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.

Chapter 17: Updating Applications<br />

Working with Upgrades and QuickPatch Projects<br />

<strong>Edition</strong>: <strong>InstallShield</strong> <strong>Express</strong> <strong>Edition</strong> enables you to create major upgrades as full-installation packages that remove an<br />

earlier version of the product if it is present on the target machine before installing the new version. <strong>InstallShield</strong> <strong>Express</strong><br />

<strong>Edition</strong> also enables you to create minor upgrades packaged as QuickPatch packages. If you need to create small updates<br />

or standard patches, consider upgrading to <strong>InstallShield</strong> Premier <strong>Edition</strong> or <strong>InstallShield</strong> Professional <strong>Edition</strong>.<br />

Refer to the topics in this section to learn how to create upgrades and QuickPatch projects.<br />

Understanding File Overwrite Rules<br />

The Windows Installer service uses several file overwrite rules, by default, to determine whether a file<br />

included in an upgrade should overwrite a file that already exists on the target system. The rules apply<br />

when the REINSTALLMODE property uses the o setting to install over older files on the target system.<br />

To change this behavior, you can replace the o option with one of the following values:<br />

• p—Reinstall only if there is no equivalent file on the target system.<br />

• e—Reinstall if the file is missing or if it is an earlier or equal version.<br />

• d—Reinstall if file is missing or different.<br />

• a—Reinstall all files, regardless of version.<br />

Note that the setting for REINSTALLMODE applies to all of the features being installed; it cannot be<br />

set for an individual feature. In addition, setting REINSTALLMODE to include a will likely cause<br />

prompts for the original installation source during the application of a patch.<br />

Updating the Package Code, the Product Version, and the<br />

Product Code<br />

Several Windows Installer codes help identify a product:<br />

• Package Code—Part of the Summary Information Stream, the package code identifies a particular<br />

database. The package code is not a Windows Installer property. Any two .msi databases with<br />

identical package codes must have identical contents. Therefore, you should change the package<br />

code for each build.<br />

• ProductVersion—This is a Windows Installer property that contains the product version. Note that<br />

Windows Installer uses only the first three fields of the ProductVersion property for version<br />

comparisons. For example, for a product version of 1.2.3.4, the 4 is ignored. (Note that this is true<br />

for comparisons of ProductVersion values, and not for file versions.)<br />

• ProductCode—This is a Windows Installer property that contains the GUID of a product. Windows<br />

Installer treats two products with different ProductCode GUIDs as unrelated, even if the values for<br />

the ProductName property are the same.<br />

• UpgradeCode—This is a Windows Installer property that contains a GUID representing the product<br />

family. The UpgradeCode should be consistent across different versions and languages of a family<br />

of related products for patching purposes. You can set the UpgradeCode for an upgrade in the<br />

Upgrade Paths view.<br />

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

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

Saved successfully!

Ooh no, something went wrong!