Open topic with navigation
InstallShield 2012 Spring
Project: This information applies to Basic MSI projects.
For information on multiple-instance support for InstallScript projects, see Running an InstallScript Installation Multiple Times.
Configuring the Release
To include multiple-instance support in a release, you must configure your release to include a Setup.exe setup launcher, since it displays the instance selection dialog when appropriate. To learn how to include the Setup.exe setup launcher, see Creating a Setup Launcher.
Building the Release
Building a release that includes multiple-instance support is slightly different than building a release that does not include this support. For multiple-instance support, InstallShield builds some additional files: instance transforms and instance packages.
At build time, InstallShield generates instance transforms for each instance. InstallShield streams the instance transforms into the .msi file that it creates in the Disk1 folder. Depending on how you have configured the release, the .msi file may be compressed into the Setup.exe file, or it may be left uncompressed.
At build time, InstallShield generates an .msi file for each instance. The name of each file is InstanceIdN.msi, where N represents the value of the InstanceId property for that instance. The .msi files are stored in a folder called Instances under the release location.
Working with Releases
Creating Patches for Multiple Instances of a Product
Special Considerations for Multiple-Instance Support
Run-Time Behavior for Installing Multiple Instances of a Product
Installing Multiple Instances of Products and Patches (Windows Installer Help Library)
InstallShield 2012 Spring Help Library
|Copyright Information | Contact Us|