Windows Installer Editor Reference
220
Organizing Your Installation Into Releases
Installs any other prerequisites that are specified on the Prerequisites page.
These prerequisites are not installed into an SVS layer.
Determines whether a compatible version of the SVS Driver (Software
Virtualization Agent) is installed.
If a compatible version of the SVS Driver is not found and if the SVS Driver
runtime is not a prerequisite of the installation, one of the following happens:
If you selected the option to install the .MSI normally on the Build Options
page, the .EXE wrapper installs the .MSI normally and not into an SVS layer.
If you did not select the option to install the .MSI normally, the installation
ends.
If a compatible version of the SVS Driver is not found and the SVS Driver is a
prerequisite of the installation, the .EXE wrapper does one of the following to
install the SVS Driver:
If a full version of the SVS Driver is installed, a compatible full version is
downloaded and installed.
If the Download Driver option on the Prerequisites page is selected for the
SVS Driver runtime, the SVS Driver runtime is downloaded and installed.
If the Include Driver option on the Prerequisites page is selected for the
SVS Driver runtime, the SVS Driver runtime is installed.
Prompts the end user to restart the computer if the SVS Driver was installed.
The computer must be restarted to complete the installation of the SVS Driver.
Creates an SVS layer for the .MSI and installs the .MSI into the layer.
The .MSI installation runs normally. This includes the installation dialog boxes
that appear to the end user. The product code of the .MSI is used for the layer
ID.
Activates the virtual software layer.
The virtualized application then looks and behaves like any other application to
the end user.
See also:
About Virtual Software Packages in the Virtual Package Editor Help
About the Exclusion of Files on the Build Options Page
On the Build Options page, if you select Install the .MSI into an SVS layer, options to
exclude file extensions or directories become enabled. Use these options to exclude end
user data files from the SVS layer. You exclude files so that end users data files are not
saved in the SVS layer but are saved to the base file system. End user data files that are
excluded from the layer are not lost when the application is reset from Add/Remove
Programs.
See
About Maintenance of an .MSI Installed into an SVS Layer
on page 221.
Warning
If an .MSI is installed into an SVS layer, any files that are generated by the application
and saved locally are lost when the layer is reset unless those files were excluded on the
Build Options page.