Windows Installer Editor Reference
195
Organizing Your Installation Into Releases
z
Exclude all file extensions from the Extension table
Mark this to exclude user data files from the SVS layer for all file extensions that
appear in the Extension table. You add file extensions to the Extension table on the
File Associations page.
See
Adding File Associations
on page 154 and
About the Exclusion of Files on the
Build Options Page
on page 196.
z
Exclude the following extensions
Specify file extensions for user data files that you want to exclude from the SVS
layer. Separate extensions with a comma. You can enter extensions with or without
the preceding period.
z
Exclude all files in the following directories
Use this option to exclude specific directories from an SVS layer. Any user data file
that is saved in these directories is excluded from the SVS layer. When you specify
a directory, you can also exclude its subdirectories. To exclude a directory, click
Add and select the directory from the Directory drop-down list. The Directory
drop-down list displays all built-in Windows Installer directories and any directories
that you added on the Files page. To exclude subdirectories, mark Exclude all
subdirectories under this directory. Directories that you exclude appear in the
list pane on the Build Options page.
See also:
Adding Prerequisites to a Release
on page 198
Creating a WebDeploy Installation
on page 207
About the Installation of an .MSI into an SVS Layer
You can create an .MSI installation that is installed into an SVS layer. You can then take
advantage of the benefits of both an .MSI and an SVS layer. When you install an .MSI
into an SVS layer, you eliminate the possibility of conflicts with other applications,
including another version of the same application, and avoid changes to the base
Windows installation. You also make it possible for an end user to quickly restore the
application to its original state by resetting the layer from Add/Remove Programs.
Before you create an installation that installs an .MSI into an SVS layer, you should be
familiar with the following:
z
.EXE wrapper
To create an installation that installs an .MSI into an SVS layer, you must first select
an option to create an .EXE on the Build Options page. After you select an .EXE
option, the Install the .MSI into an SVS layer option becomes enabled on this
page. After you select the option to install the .MSI into an SVS layer and compile
the .MSI, an .EXE file is created that has the same name as the .MSI file. This .EXE
file contains the logic that is needed to install the .MSI into an SVS layer.
See
Setting Build Options for a Release
on page 193
z
WiseScript project file (.WSE)
When you select the option on the Build Options page to install the .MSI into an SVS
layer, a WiseScript project file (.WSE) is created, which when compiled creates the
.EXE wrapper. You can edit this .WSE file from the Prerequisites page.
See
Editing the WiseScript That Creates the Installation .EXE
on page 202.
In addition to the logic needed to install the .MSI into an SVS layer, the WiseScript
file contains installation error messages and the installation’s maintenance mode
