09.12.2012 Views

InstallShield 2012 Spring Express Edition User Guide

InstallShield 2012 Spring Express Edition User Guide

InstallShield 2012 Spring Express Edition User Guide

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Chapter 18: Additional Installation Options<br />

Working with Windows Installer Properties<br />

Public Properties<br />

Public properties have names that contain only uppercase letters. For example, INSTALLDIR is a<br />

public property. Public properties can be specified at the command line used to launch the installation<br />

or chosen by using an authored user interface.<br />

Note: Only public properties have their values preserved from an installation’s user interface to the point where the<br />

installation is changing the target system. If you set the value of a property in a dialog displayed to the end user, use a<br />

public property (for example, MY_PUBLIC_PROPERTY) if you want its value written to a file or to the registry.<br />

Private Properties<br />

Private properties have at least one lowercase letter in their name and cannot be changed from the user<br />

interface. For example, ProgramFilesFolder is a private property. End users have no control over the<br />

values of private properties, since they cannot be set from the command line.<br />

Restricted Public Properties<br />

Restricted public properties allow network administrators to define public properties that can be<br />

changed only by a system administrator. This way, the administrator can change settings quickly<br />

without having to worry that other users on the network may tamper with the setup. For more<br />

information, see Specifying that a Public Property Should Be a Restricted Public Property.<br />

Required Properties<br />

The Windows Installer service relies on five properties that are required in every Windows Installer<br />

installation. By default, these properties are included in every installation that you create using<br />

<strong>InstallShield</strong>.<br />

• ProductCode<br />

• ProductLanguage<br />

• Manufacturer<br />

• ProductVersion<br />

• ProductName<br />

Conditions<br />

Many properties are not set until the installation is launched. These properties are populated with<br />

information from the target system. For example, the VersionNT property is not set until the<br />

installation is launched. This property is set to the version of Windows that the target machine is<br />

running if the operating system is Windows 2000 or later.<br />

Properties that are set at run time can be used to create launch conditions for the installation. If you<br />

want your product to be installed only on Windows XP, you can use conditional logic to check the end<br />

user’s system, and install the product if all conditions are met.<br />

<strong>InstallShield</strong> <strong>2012</strong> <strong>Spring</strong> <strong>Express</strong> <strong>Edition</strong> <strong>User</strong> <strong>Guide</strong> ISE-1900-UG00 349

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!