Install package and deployment wizard vb6

You run Package and Deployment Wizard after you have finished your application and are ready to create a distribution vehicle for the application. Such a distribution vehicle might be either distribution disks or a special directory on a network.

The distribution vehicle would contain compressed versions of all files necessary to install and run the application. During the import Visual Installer will make an analysis of the VB6 project file and find out which files to include in the installation project.

Runtimes files and ActiveX components if used are included automatically. How to create an installation for a VB6 application:. Related tips Visual Installer can also import a VB.

NET project from Visual Studio This tip shows how: How to create an installation for a VB. NET application As mentioned above, an installation can be code signed.

Yes, that's the problem with the Package and Deployment Wizard. It's fine if your target is a pre-Windows OS, but it becomes a catch once you start removing dependent files in order to support newer OS versions. I don't think msvcrt. Inno Setup is good alternative. It's free and allows much more control over your application setup package. It's not as easy to use as the Package and Deployment Wizard but if you're supporting several versions of the OS then it's an invaluable utility.

I've used the Microsoft Visual Installer in the past. It's configurability was better than the PDW but it isn't as easy to use and I found the user interface to be rather non-intuitive. My favorite used to be the Wise Installation System back to the shareware and first few versions.

But as they added new features the price escalated well beyond what I could justify paying for the product. They no longer have a version for the "little guy". I have had the same problem. It can be frustrating, but you can modify your setup. Check out this link.

It should be helpful.