09.12.2012 Views

InstallShield 2012 Express Edition User Guide - Knowledge Base ...

InstallShield 2012 Express Edition User Guide - Knowledge Base ...

InstallShield 2012 Express Edition User Guide - Knowledge Base ...

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Upgrade Path Settings<br />

Chapter 24: View Reference<br />

Organize Your Setup View<br />

By specifying upgrade path settings, you indicate how you want to affect an end user’s system if a<br />

previously released version of your product that uses Windows Installer is installed—and that installed<br />

version has a different product code and a different version number than your current release. Each<br />

upgrade entry setting is described below:<br />

Table 24-10: Upgrade Path Settings<br />

Setting Description<br />

Upgrade Code This setting contains as its value the upgrade code GUID of the product version that you<br />

want this version of your application to replace. When the installation of your current<br />

version begins, the Windows Installer engine searches the target system for the upgrade<br />

code specified. Upon finding a matching upgrade code—along with other matching<br />

upgrade properties—the Windows Installer upgrades the target system by installing the<br />

new version.<br />

If you added an upgrade entry to the Upgrade Paths tree by browsing for and selecting<br />

an .msi file on your system, the upgrade code of that .msi file automatically populates<br />

the Upgrade Code setting. If the .msi file for the product version that you want to<br />

upgrade is not on your system, you can type the upgrade code in this setting.<br />

You can also use the ellipsis (...) button to navigate to an .msi file (or a Setup.exe file<br />

that contains an .msi file) on your system and populate the Upgrade Code setting.<br />

Caution: The upgrade code must be the same as that of the previous version of your<br />

product that was installed using Windows Installer technology.<br />

Min Version The Min Version setting further defines the Windows Installer’s search for installed<br />

versions to upgrade. The previously installed version’s upgrade code must first match<br />

the value specified in the Upgrade Code setting. Once a matching upgrade code match<br />

is detected, the search can be narrowed by the minimum and/or maximum version<br />

specified and whether the versions are included or excluded (indicated in the Include Min<br />

Version and Include Max Version settings).<br />

This setting contains the minimum version number of the product that you want your<br />

current version to update. The setting can be populated in one of the following ways:<br />

• If you added an upgrade entry to the Upgrade Paths tree by browsing for and<br />

selecting an .msi file or a Setup.exe file on your system, <strong>InstallShield</strong> uses the<br />

version of the .msi file in the Min Version setting.<br />

• You can also type the minimum version in this setting in the format 0.00.0000 or<br />

00.00.0000 (where the zeros represent the version number).<br />

Caution: You must specify a value for at least one of the version settings: Min Version,<br />

Max Version, or both.<br />

Include Min Version Specify whether you want to include the minimum version—specified in the Min Version<br />

setting—in the upgrade.<br />

If you want the Windows Installer to include the minimum version in the search for<br />

previously installed versions of your product on the target system, select Yes.<br />

<strong>InstallShield</strong> <strong>2012</strong> <strong>Express</strong> <strong>Edition</strong> <strong>User</strong> <strong>Guide</strong> ISE-1800-UG01 521

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

Saved successfully!

Ooh no, something went wrong!