InstallShield 2012 Spring Express Edition User Guide

• Express Settings
• Media Types
• Build Tab
• Setup.exe Tab
• Signing Tab
• .NET/J# Tab
• Internet Tab
• Events Tab
Chapter 24: View Reference
Prepare for Release View
When you build a release, InstallShield takes all of the information from your project and compiles it
into a package that is capable of installing your product onto any supported Windows platform.
Express Settings
The Express item in the center pane of the Releases view has the following settings that apply to all of
your projects releases.
Table 24-60: Express Settings
Setting Description
Package Code To override the default package code that is entered in the General Information view, enter a
new GUID. To have InstallShield generate a different GUID for you, click the Generate a new
GUID button ({...}) in this setting.
Generate Package
Code
MSI Package File
Name
Note: This package code is ignored if Yes is selected for the Generate Package Code
setting.
Specify whether you want InstallShield to generate a new package code every time that a
release is built:
• Yes—InstallShield generates a new package code at build time and includes it in the
.msi package.
• No—InstallShield does not generate a new package code at build time. If you enter a
package code in the Package Code setting, that package code is used. If you do not
specify a package code for your releases, InstallShield uses the package code that it
generated when you first created the project.
The package code—which is part of the Summary Information Stream—identifies a
particular database. Any two .msi databases with identical package codes must have
identical contents. Therefore, the package code should be changed for each build.
Specify the file name—without the period or the file extension—that InstallShield should use
for the .msi file that it generates at build time. If this setting is blank, the product name is
used.
InstallShield 2012 Spring Express Edition User Guide ISE-1900-UG00 579