Windows Installer Editor Reference
208
Organizing Your Installation Into Releases
To populate the file name or subdirectory with the value of one or more
properties, enter one or more property names surrounded by brackets.
Example: [ProductName].msi
You can use one or more specific parts of a property’s value if its segments
are period delimited. This is most useful for adding all or part of the product
version number to the file name. The syntax is:
[property_name.%segment_number%segment_number]
You can add characters between the segments, except for periods,
numerals, or the % symbol.
Examples: If the value of ProductVersion is 1.05.07.25, the following .MSI
names result.
Description
Enter information to distinguish this release from others. Examples: Evaluation,
Optimized for Internet Distribution. This description appears on the Releases
page.
Installation Theme
Select the theme for the installation dialog boxes for this release. The theme
controls the overall look of the dialog boxes by setting their top or side images
and the fonts of the dialog box text. You can use different themes for different
releases. Example: Use a different theme for an evaluation release to clearly
distinguish it from your standard release.
See
Changing the Theme of Dialogs
on page 453.
The theme of the Default release on the Releases page corresponds to the
Default Theme on the Dialogs page. Changing the theme on one page changes
it on the other. Renaming or deleting the Default release breaks this
relationship.
Compression Type
Select the amount of compression. This depends on the media you use to
distribute the release. Examples: For an Internet release, use maximum
compression for a faster download, but for a release on a CD, use no
compression. Higher compression slows the compile.
Release Type
Select Terminal Server Enabled if this release is intended to be installed in a
Microsoft Terminal Services or Citrix environment. This sets the installation to
be installed per-machine and prevents keypaths for components from being
assigned to per-user resources. This option might cause keypaths to be empty,
and might cause a one-time repair. Environment variables are duplicated,
creating a per-user set and a per-machine set, one of which is installed
depending on the value of ALLUSERS. Also see ALLUSERS Property in the
Windows Installer SDK Help.
.MSI File Name Entry
Compiled .MSI Name
Application_[ProductVersion.%4].msi
Application_25.msi
Application_[ProductVersion.%1_%2].msi
Application_1_05.msi