How can I create a vb6 install package, Package and deployment wizard not working???

How do I create a install package for a vb6 application? Hello experts I have a vb6 app that I need to create a install back for.  I tried using the add in package and deployement wizard that comes with vb6 and it doesn't seem to work when I run the setup.exe file.  I always get an error saying some ocx file is being used, and it wont let me continue with installation.  The vb6 application itself has 3 part tools with in it.  I am not sure I am doing it correctly.   What button do I click on the first screen of the wizard?  Package, Deploy, Manage Scripts.  I tried both Package and Deploy,   then I am prompted to Select a Deployement Script.  Is there a good walk through, or another tool I can use to create the install package?
Who is Participating?
tonym001Connect With a Mentor Commented:
I still have to use VB6 for some applications and use the Microsoft Visual Studio Installer (I avoid the package and deployment wizard like the plague).  It's free and fairly easy to use and there are lots of tutorials on how to use it if you google it.
It's avaiable here
kevinfiggConnect With a Mentor Commented:

You could you the P & D W but there are better free products out there. Advanced Installer ( allows the creation of simple setup installers based on the MSI format - which is great as this is the standard at the moment.

To use this, you need to know exactly what files are needed on the target system. So work out what files you expect to be available in terms of text files, graphics ect. Then, you need to consider the system files needed.

Firstly, you'll need to add MSVBVM60.DLL - this is a definate.

Then, if you know what OCX and DLL files you need - then great. But if you don't then open your .VBP file in notepad and see what DLL and OCX files are referenced. Ignore the STOLE.DLL (or something similar) - this should never be installed by an installer.

You have the choice of where to install these files, and I would recommend installing them all - including the DLL and OCX files to you application directory - this avoids other applications ruining your app and vice versa. It's a against the way shared libraries were designed to work - but thats the flaw in the design of shared libraries..

There are tutorials on Adv. Installer's website eg, 
so it might be worth starting there.

Good luck and were here if you need us.
Éric MoreauConnect With a Mentor Senior .Net ConsultantCommented:
when I was using VB6, I was using
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.