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. COM
  4. Registry

Registry

Scheduled Pinned Locked Moved COM
c++comwindows-adminquestion
5 Posts 5 Posters 12 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.
  • D Offline
    D Offline
    Dimitri
    wrote on last edited by
    #1

    Can't initialise a COM with regsvr32 on the machine without VC++ 6.0 installed ! But with V-studio there is no problems. Anyone knows why ?

    A 1 Reply Last reply
    0
    • D Dimitri

      Can't initialise a COM with regsvr32 on the machine without VC++ 6.0 installed ! But with V-studio there is no problems. Anyone knows why ?

      A Offline
      A Offline
      Alex Gorev
      wrote on last edited by
      #2

      Hi, Probably your control links dynamically to one of the DLLs from VC++ (like MFC libraries)... You have to distribute all the DLLs you are using in your control or use static linking. Regards, Alex Gorev, Dundas Software.

      D 1 Reply Last reply
      0
      • A Alex Gorev

        Hi, Probably your control links dynamically to one of the DLLs from VC++ (like MFC libraries)... You have to distribute all the DLLs you are using in your control or use static linking. Regards, Alex Gorev, Dundas Software.

        D Offline
        D Offline
        ddd_lll_ddd
        wrote on last edited by
        #3

        Thanks, I think I've found a problem. It's quite tricky if you don't know indeed. The standard Windows NT configuration doesn't include an Atl.dll in system32 dir. Neither you can see it in "Dependency walker" when checking your COM deps., so to enable registration of ATL COM on the fresh installed NT, you must copy that dll and register it as well as it needs to have an Ole32aut.dll but proper version (NT, or 95). Unfortunately this small tip is not noticed anywhere you can see straight away and for new COM developers can be a time consuming. Thanks again, Dimitri.

        M E 2 Replies Last reply
        0
        • D ddd_lll_ddd

          Thanks, I think I've found a problem. It's quite tricky if you don't know indeed. The standard Windows NT configuration doesn't include an Atl.dll in system32 dir. Neither you can see it in "Dependency walker" when checking your COM deps., so to enable registration of ATL COM on the fresh installed NT, you must copy that dll and register it as well as it needs to have an Ole32aut.dll but proper version (NT, or 95). Unfortunately this small tip is not noticed anywhere you can see straight away and for new COM developers can be a time consuming. Thanks again, Dimitri.

          M Offline
          M Offline
          Michael Dunn
          wrote on last edited by
          #4

          Moral: Always build with the MinDependency configuration. :) That way you never have to worry about ATL.DLL. --Mike-- http://home.inreach.com/mdunn/

          1 Reply Last reply
          0
          • D ddd_lll_ddd

            Thanks, I think I've found a problem. It's quite tricky if you don't know indeed. The standard Windows NT configuration doesn't include an Atl.dll in system32 dir. Neither you can see it in "Dependency walker" when checking your COM deps., so to enable registration of ATL COM on the fresh installed NT, you must copy that dll and register it as well as it needs to have an Ole32aut.dll but proper version (NT, or 95). Unfortunately this small tip is not noticed anywhere you can see straight away and for new COM developers can be a time consuming. Thanks again, Dimitri.

            E Offline
            E Offline
            Edward
            wrote on last edited by
            #5

            If you build your project with /D "_ATL_STATIC_REGISTRY" compiler option you do not need atl.dll to register/unregister you component.

            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