Library tutorials & articles
Visual Studio Installer
- Introduction
- Visual Studio Installer
- Getting Started
- Installation Files
- Customizing the Setup
- Wrapping Up
- Install on Demand
Visual Studio Installer
A free program from Microsoft, the Visual Studio Installer allows you to take advantage of this new technology for applications developed using Visual Studio. This program integrates with Visual InterDev,and is ideal for creating simple installations, with out costing the developer anything. It also provides a useful utility for importing Visual Basic projects, effectively making it possible to create a professional installation within a few minutes. We'll show you how here.
The Visual Studio Installer is available on the Windows 2000 Readiness Kit, which you can order for free from here.
Once you have installed the Visual Studio Installer (from here on referred to as VSI), run the program. You will then be greeted with the standard Visual InterDev New Project dialog. Click the Visual Studio Installer Projects under the Visual Studio folder, and create a new Visual Basic Installer Project. You will notice there is also an Empty Installer Project, which you could use, but it is usually far quicker to let VSI to select the correct components your application needs for you.
For this we obviously need a VB project. I recommend you just create a quick VB application that does absolutely nothing for the moment! Don't forget to compile the project to an EXE file. When the wizard starts, select a Visual Basic project you want to create a setup program for.
Below this path, you then have the choice whether to create an Installer or a Merge Module. An Installer is a stand-alone installation for an application, where as a Merge Module is an installation for a shared component. This can then be used in another Installer project that requires the component. In this case, leave the Create Installer option selected, and click Finish.
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.