Express Settings

InstallShield 2020 Express Edition

The Express item in the center pane of the Releases view has the following settings that apply to all of your projects releases.

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.

Note:This package code is ignored if Yes is selected for the Generate Package Code setting.

Generate Package Code

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.

MSI Package File Name

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.

You can also include the value of a property from the Property Table in this field, as described in Setup File Name.

Setup File Name

Specify the file name—without the .exe file extension—that InstallShield should use for the setup launcher file that it generates at build time. If this setting is blank, InstallShield uses the default value of Setup, and the setup launcher file is called Setup.exe.

You can also include the value of a property from the Property Table in this field. For example, you could enter any of the following properties:

setup[ProductVersion]

setup[CustomVersion]

setup[ProductCode]

setup[ProductCode][ProductVersion]

If you entered setup[ProductVersion], it would result in a setup named setup14.10.1234.exe, for example.

64-Bit Setup Launcher

Specify whether you want to build a 64-Bit Setup Launcher or a 32-Bit Setup Launcher.

Select Yes to build the 64-Bit setup launcher.

Select No to build the 32-Bit setup launcher. For more detail, see Building 64-Bit Setup Launcher.

See Also

Building a Release

General Information Settings