Quote:
Originally posted by Ed Lampman
Your package will undoubtedly contain .dll files and .ocx files. These will have to be registered on the target machine in order for your program to use them. It's easier to let the P&D do all this as part of the install.
I really, really hate the P&D wizard. I usually just use the P&D wizard to create a dependency file to see what dll's are used. I then either use .bat files or VB4(which doesn't need run-times) to install my vb6 runtimes and register my dll's.