This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallShield
- :
- InstallShield Forum
- :
- Register dll not working
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Jul 02, 2008
02:31 AM
Register dll not working
I've got an installshield package that is installing a c++ dll. It used to be set to selfregister but for various reasons we now need to register this file at the end of the install.
If i call
i get a loadlibrary failed error. While the error is on screen i open a command window and run "regsvr32 mydll.dll" and the registration succeeds.
So i thought maybe the path i'm giving it is wrong although the line above it registers a component in the samefolder and i've used the same format of command. So i run this:
This code still fails with the LoadError Message and registration from the command line still succeeds at this point.
Any Ideas?
Russell
If i call
LaunchAppAndWait(SUPPORTDIR ^ "regsvr32", WINSYSDIR ^ "mydll.dll", WAIT);
i get a loadlibrary failed error. While the error is on screen i open a command window and run "regsvr32 mydll.dll" and the registration succeeds.
So i thought maybe the path i'm giving it is wrong although the line above it registers a component in the samefolder and i've used the same format of command. So i run this:
if(FindFile(WINSYSDIR , "mydll.dll",szSDKFileName)=0) then
LaunchAppAndWait(SUPPORTDIR ^ "regsvr32", WINSYSDIR ^ szSDKFileName, WAIT);
else
MessageBox("Not found",SEVERE);
endif;
This code still fails with the LoadError Message and registration from the command line still succeeds at this point.
Any Ideas?
Russell
(1) Reply
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Jul 02, 2008
10:49 AM
Have you tried dependency walker on your DLL on the target machine? One other thing you could try would be making sure the current directory is set to WINSYSDIR as well.
I'm also a little unnerved by your use of a regsvr32 in SUPPORTDIR; it would probably be much better to use the one on the target machine.
I'm also a little unnerved by your use of a regsvr32 in SUPPORTDIR; it would probably be much better to use the one on the target machine.