The following is a general example of authoring an InstallScript wrapper for your installation.

Depending on the installation requirements, there are occasions where checks or modifications to the target machine are needed before the main installation is run. What follows is a simplified version of an InstallScript wrapper where one of two possible installations can be run depending on the OS. Additional changes will be needed depending on the setup?s requirement and more complex changes falls outside of the scope of this article. For installations that need to be run before the main installation, use a setup prerequisite instead.

1. Create a new InstallScript setup. MSI based installations can run while the InstallScript installation process is running- allowing it to act as a wrapper.

2. In the Installation Designer tab, go to ?General Information? -> Maintenance Experience table entry select ?No uninstall or maintenance?. This helps ensure no uninstall key is created. The wrapper will run as a first time install regardless the number of times it is run on the target machine.

3. Go to ?Behavior and Logic? and select ?Support Files/Billboards?. In Support Files -> Place the main installation(s) in the Language Independent section.

4. Now select the InstallScript view above ?Support Files/Billboards?. Select the ?Setup.Rul?.

In the first drop down menu, select ?Before Move Data?. In the second drop down menu, select the ?OnFirstUIBefore? option. Remove all the code between the ?begin? and ?end;? from the default function. Select ?Move Data? in the first drop down menu. Select ?OnMoveData?. Remove all the code between the ?begin? and ?end;? from the default function. Finally, select ?After Move Data? in the first drop down menu and select ?OnFirstUIAfter? in the second drop down menu. Remove all the code between the ?begin? and ?end;? from the default function.

Add custom code in the OnFirstUIBefore event with the custom code to launch the wrapped installations. In this case, after a OS comparison appropriate calls to LaunchApplication are run. Note that if you are using LaunchApplication to launch an .msi instead of an .exe within an InstallScript wrapper, the InstallScript wrapper process should continue running while the .msi is running so that the cached .msi can be accessed. You can do this by passing in the LAAW_OPTION_WAIT with INFINITE as the nTimeOut parameter in LaunchApplication. Alternatively, you can use LaunchAppAndWait with WAIT for the nOptions parameter.

5. Build and test the release.

For more information on the LaunchApplication() function, please see the following Helpnet article: LaunchApplication
For information on accessing the 64-bit version of cmd.exe see the following Helpnet article: Targeting 64-Bit Operating Systems with InstallScript Installations