Printable View
Greetings.
How do I get my setup project to automatically register a DLL into the GAC?
I've set the register property of the DLL to vsdraCOM. After running the setup project on a machine, other than my development machine, I notice that the DLL has not been registered into the GAC.
Any advice?
Thanks.
I actually tried running the Regsvr32 utility via the command prompt to register the dll in question and I get a message that says it could not find the entry point and also that the dll cannot be registered.
That being said I assume that even if I set the register property to vsdraCOM or vsdraCOMRelativePath, it still probably wouldn't successfully register the dll...?
No, that means that the dll doesn't need to be registered. How are you deploying your app? What are you using for an installer.
The installer is just your bare bones setup project that comes standard with visual studio i beleive.
I was hoping that explicitly having the setup program register certain DLL's I could avoid This Problem
How can I find out where my application is looking for a dependant DLL? Or how can I instruct the runtime where to look for certain DLL's?
If the DLL in question does not need to be registered and I properly reference it in my solution and, after an install, the DLL gets copied to the working directory of the application, why is there a problem locating it?
I don't have all the details of what you are doing and how you determined the dll's that you needed.
Was the dll part of a SP?
I'm not sure what you mean by SP. I need these DLL's so I can utilize ImageGlue services in my application for manipulating images in a variety of ways.
The DLL's in question, WebSupergoo.ImageGlue5.COM.DLL and WebSupergoo.ImageGlue5.DLL, get unpacked when I run the Image Glue Setup.exe into a folder called C:\Program Files\WebSupergoo\ImageGlue .NET\Assemblies.
I reference the DLL's from there.
Of course the Image Glue setup places those 2 DLL's into the Windows assembly as well as a ImageGlue.DLL file into System32... Not sure if there is anything else that it needs...
SP - Service Pack. It could be possible that you will need to run the setup for that package in order for it to operate properly. To find the dependencies for those files, you can use MS Depends.exe or **********.