Library tutorials & articles
Visual Studio Installer
Wrapping Up
And that's it! All you need to do now is click Build|Build... then after the setup has been compiled successfully, you can test it by clicking Project|Launch Installer. The msi file that you need to distribute will be in a folder named Output in the directory you created the installation project.
You might want to specify some cabinet sizes, if your program is distributed on floppy disk, and set the compression rate to what you want. You can set all of this under Project|Properties.
After using the Visual Studio Installer, you might be interested in some of our reviews for other Windows Installer products. (Take a look at Related Pages on the right).
James first started this website when learning Visual Basic back in 1999 whilst studying his GCSEs. The site grew steadily over the years while being run as a hobby - to a regular monthly audience ...
Related articles
Related discussion
-
Run-time error '91'
by converter2009 (1 replies)
-
VB6 Runtime error 381 subsript out of range Error
by Uncle (2 replies)
-
passing and reading parameters from using Shell
by jigartoliya (0 replies)
-
Convert C++ code to VB6
by mawcot (4 replies)
-
listbox scrollbar
by Dennijr (10 replies)
Related podcasts
-
Christian Beauclair
14 mai 2008 (�mission #0074) ::.Christian Beauclair: Stratégies de migration VB6 vers .NET Nous discutons avec Christian Beauclair des stratégies de migration VB6 vers .NET. Entre autres, nous discutons comment utiliser le "VB 6 Code Advisor" et le "Interop Forms Toolkit" pour ajouter la puiss...
Can anybody plz tell how to map the check boxes or radio buttons present in the user interface editor of setup wizard with some link so that only the desired features gets installed .....
How do I get the setup to check to see if MDAC, JET and DCOM are available on the target machine, install if required and then install the actual application?
I have found that the Installer has a setting to check for the INSTMSIA.exe file so it must be able to do other checks...
I am calling the function MsiInstallMissingComponent from a wrapper to the msi to fix a missing components and I noticed that all the custom actions that are in the UI sequence table are called during the call of this function.
If I have a custom action that I don't want to be called during the call of the function, is there a flag\property that I can use?
Thanks
-- Dafna
This article does not contain much information about how to handle registry.
There is no information whether we can access some runtime informations like the application folder path or not .This might be required for saving the path of the application in registry.
This thread is for discussions of Visual Studio Installer.