Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
  1. Home
  2. General Programming
  3. C / C++ / MFC
  4. COMCTRL32 Manifest

COMCTRL32 Manifest

Scheduled Pinned Locked Moved C / C++ / MFC
performancetutorialquestionannouncement
3 Posts 2 Posters 0 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • A Offline
    A Offline
    Alex_Y
    wrote on last edited by
    #1

    If my project includes 85 dlls how to enable manifest on for some of them. If you have manifest it always using COMCTRL32 vesion 6 for all projects. I tried to unload version 6 and load version 5 but it didn't work Microsoft keeps always 6 in the memory if you have manifest. Is the any way to customize usage of manifest per project? :)

    G 1 Reply Last reply
    0
    • A Alex_Y

      If my project includes 85 dlls how to enable manifest on for some of them. If you have manifest it always using COMCTRL32 vesion 6 for all projects. I tried to unload version 6 and load version 5 but it didn't work Microsoft keeps always 6 in the memory if you have manifest. Is the any way to customize usage of manifest per project? :)

      G Offline
      G Offline
      georgeraafat
      wrote on last edited by
      #2

      The wizard generated code for MFC apps adds code to stdafx.h to tell the linker to add the 6.0 manifest specific information. You can make sure you don't have this code for the dlls where you want to load the pre-6.0 dll. I would think that you need to load the pre-6.0 before loading the 6.0 one. gmileka

      A 1 Reply Last reply
      0
      • G georgeraafat

        The wizard generated code for MFC apps adds code to stdafx.h to tell the linker to add the 6.0 manifest specific information. You can make sure you don't have this code for the dlls where you want to load the pre-6.0 dll. I would think that you need to load the pre-6.0 before loading the 6.0 one. gmileka

        A Offline
        A Offline
        Alex_Y
        wrote on last edited by
        #3

        Is it only for VS2005 MANIFESTDEPENDENCY :)

        1 Reply Last reply
        0
        Reply
        • Reply as topic
        Log in to reply
        • Oldest to Newest
        • Newest to Oldest
        • Most Votes


        • Login

        • Don't have an account? Register

        • Login or register to search.
        • First post
          Last post
        0
        • Categories
        • Recent
        • Tags
        • Popular
        • World
        • Users
        • Groups