Inconsistent registration
-
Howdy. I have a large, multiserver project that has been developed in VC++ on WinNT 4.0 SP6a. It makes use of ATL for most of the COM-related things. My trouble is that it works fine on the machine on which it was developed. I have tried it on other machines and sometimes it works fine - sometimes it doesn't. The current issue is that when I regsvr32 my servers, I get the standard message that says that registration was successful. Trouble is, nothing shows up in the registry! Do ATL-based servers require some fancy libraries for registration? Do they require any libraries that get loaded with MSDEV or a certain service pack? I'm trying to make do without loading the development environment on the machine (it will be a production machine eventually). Any help would be GREATLY appreciated. J
-
Howdy. I have a large, multiserver project that has been developed in VC++ on WinNT 4.0 SP6a. It makes use of ATL for most of the COM-related things. My trouble is that it works fine on the machine on which it was developed. I have tried it on other machines and sometimes it works fine - sometimes it doesn't. The current issue is that when I regsvr32 my servers, I get the standard message that says that registration was successful. Trouble is, nothing shows up in the registry! Do ATL-based servers require some fancy libraries for registration? Do they require any libraries that get loaded with MSDEV or a certain service pack? I'm trying to make do without loading the development environment on the machine (it will be a production machine eventually). Any help would be GREATLY appreciated. J
Follow-up... The problem persists. I searched the MSDN library and found a reference to some run-time issues. They suggest you do a release min dependency build and remove the _ATL_MIN_CRT define. I did it, registered the server, it said that it worked, but didn't touch the registry. I'll add that I'm working as an administrator, so registry security should not be an issue. Also, my .exe servers added their CLSIDs and APPIDs, but little else. So something's working - just not enough to actually be useful. Puh-leeeeeze hep me! Hep me! J
-
Follow-up... The problem persists. I searched the MSDN library and found a reference to some run-time issues. They suggest you do a release min dependency build and remove the _ATL_MIN_CRT define. I did it, registered the server, it said that it worked, but didn't touch the registry. I'll add that I'm working as an administrator, so registry security should not be an issue. Also, my .exe servers added their CLSIDs and APPIDs, but little else. So something's working - just not enough to actually be useful. Puh-leeeeeze hep me! Hep me! J
Sometimes, a proxy/stub Dll needs to be registered. Does your application make use of an external proxy/stub dll? I vote pro drink :beer:
-
Sometimes, a proxy/stub Dll needs to be registered. Does your application make use of an external proxy/stub dll? I vote pro drink :beer:
It does, and the same problem occurs. I believe the PS dll loads stuff under the AppID key under HKCR? Either way, when I regsvr32 either one of them, they both "succeed" but neither actually touches the registry. J
-
It does, and the same problem occurs. I believe the PS dll loads stuff under the AppID key under HKCR? Either way, when I regsvr32 either one of them, they both "succeed" but neither actually touches the registry. J
Oops. The PS does NOT put entries in AppID. My mistake. The problem remains. :( J
-
Oops. The PS does NOT put entries in AppID. My mistake. The problem remains. :( J
Try to move the ATL.DLL with you. Shadi Al-Kahwaji