Printable View
If I include a dll as an additional file with the Package & Deployment wizard and then distribute the resulting setup file to an end user, why do they have to register that dll? Shouldn't Visual Basic take care of that or is there some security issues involved here? I'd like to have this dll included with my program but it's just not possible if all of my end users need to register it before using the program. I appreciate any thoughts and/or replies.
umm, i think the p&d wizard should register the files:confused: I had a tonne of problems with it though, so i started using Inno Setup. Try it, its performed pretty damn sweet for me so far:)
Funny you should mention that. I've got Inno Setup just not a clue how to use it. I've created an .iss script or something I think. I'm just not sure where to go after that.
The Inno Setup has a complete help file with all the commands. If you created a setup iss file with the wizard then you should have a skeleton of what is needed.
There are forums or something simuliar for the Inno Setup program. Just do a search on the Internet. Search the Forum also, it is discussed quite frequently.
There is also a utility that takes the Setup.lst file that the PDW creates and create a partial Inno Setup Script that is OK to get you started. I am going to extend it functionalities in my version.
Check download.com for Inno Script
I just finished creating a utility to help one move from PDW to Inno Setup.
Take a look:
http://www.vbforums.com/showthread.p...&highlight=pdw