Adding a custom dll to Project Deployment
by Tatjana · in Torque Game Engine · 11/20/2006 (11:40 pm) · 3 replies
Always have used nullsoft to deploy my Torque project. But now I have created a new dll that must be packaged using the Setup Wizard in the Microsoft Visual Studio .NET 2003. I use the ide to rebuild for a new desktop icon. Tried to use NullSoft again for the new package using the new dll, but I was unsuccessful.
When the entire project is added into the installer, my dll is clearly scene in the Application Folder in the File System and in the Solution Explorer. But when I try to launch the new package after rendering the new installer, once I get to the form page that calls for the dll, I get an error exception that the dll cannot be located. (The dll works beautifully in the original application, just the deployment is the issue)
I've done some research about this. I keep reading about a dll linker. I don't know if this is what I need. And if it is, I don't know how get to the dll linker to use it.
My basic question- How do I get the installed application to locate the dll assembly using the Microsoft Visual Studio .NET 2003 Setup Wizard?
Thank you in advance.
Deeply Grateful,
~Tatjana
When the entire project is added into the installer, my dll is clearly scene in the Application Folder in the File System and in the Solution Explorer. But when I try to launch the new package after rendering the new installer, once I get to the form page that calls for the dll, I get an error exception that the dll cannot be located. (The dll works beautifully in the original application, just the deployment is the issue)
I've done some research about this. I keep reading about a dll linker. I don't know if this is what I need. And if it is, I don't know how get to the dll linker to use it.
My basic question- How do I get the installed application to locate the dll assembly using the Microsoft Visual Studio .NET 2003 Setup Wizard?
Thank you in advance.
Deeply Grateful,
~Tatjana
About the author
#2
Myself, I am not sure what you were trying to do. In any case, glad you got it working! (:
11/27/2006 (4:55 am)
Could be that no one knew the answer or just did not notice your thread.Myself, I am not sure what you were trying to do. In any case, glad you got it working! (:
#3
http://forums.winamp.com/forumdisplay.php?s=&forumid=65
Some other ramblings on DLLS...
-You usually have them placed in the same folder as your main app executable for them to be detected automatically.
-You can place them in your Windows system32 folder to be detected automatically although I'm not sure that's not the correct thing to do in many cases
-I THINK you can place them in a folder which is in your PATH environment variable to be detected automatically. Maybe someone else can confirm this?
Hope this helps.
11/28/2006 (9:58 pm)
Tatiana while I'm not completely clear on what you are trying to do exactly I have used NSIS for creating many installer packages in the past 3 years which I gather is what you are using? This sounds like it may be a question more appropriate for those forums. You may already be aware the forums are located here....http://forums.winamp.com/forumdisplay.php?s=&forumid=65
Some other ramblings on DLLS...
-You usually have them placed in the same folder as your main app executable for them to be detected automatically.
-You can place them in your Windows system32 folder to be detected automatically although I'm not sure that's not the correct thing to do in many cases
-I THINK you can place them in a folder which is in your PATH environment variable to be detected automatically. Maybe someone else can confirm this?
Hope this helps.
Torque Owner Tatjana
Found what may be a solution. The same way that I had added the exe assembly to the user's desktop folder is the same way that I added the custom dll. The custom dll will show on the user's desktop, but the program will run. At least it did for me.
If anyone else is dealing with this same issue, please try this idea. If it doesn't work, I'll keep on researching.
~Tatjana