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 17: Updating Applications<br />

Working with Upgrades and QuickPatch Projects<br />

Small-update patches also enable Windows Installer 3.0 and later to maintain a valid product state as<br />

other patches are applied and removed individually from the product. In addition, patch sequencing lets<br />

you generate upgrade packages from a smaller set of earlier product states without requiring you to<br />

consider every possible combination of patches that could exist on the target machine. The sample<br />

application lifecycle presented in the following table illustrates this advantage.<br />

Table 17-6: Sample Application Lifecycle for Patches Applied with Windows Installer 3.0<br />

Application Package<br />

All of the small updates in the table above belong to the same patch family. Windows Installer 3.0 and<br />

later uses the patch family to compare a small-update patch with all of the other patches within the same<br />

family and determine the order in which each of the patches should be applied to the target machine.<br />

Patch sequences are added to the MsiPatchSequence table of the patch package database. This table<br />

defines the relationships between patches that target the same family of patches.<br />

Patch Uninstallation<br />

Patch Sequence<br />

Number<br />

Product<br />

Version<br />

1. Base installation — 1.0 —<br />

2. Small update 1 1.0 1.0<br />

3. Small update 2 1.0 1.0<br />

4. Small update 3 1.0 1.0<br />

5. Small update 4 1.0 1.0<br />

6. Minor upgrade — 1.1 1.0<br />

Project: This information applies to QuickPatch projects.<br />

Previous Setups Targeted by<br />

Package<br />

Windows Installer 3.0 or later supports the uninstallation of patches for small updates and minor<br />

upgrades; the patches to be uninstalled must have been installed with Windows Installer 3.0 or later.<br />

When a patch is uninstalled, the product is returned to the state it was in before the patch was<br />

uninstalled. With earlier versions of Windows Installer, an end user who wants to remove a patch needs<br />

to uninstall the patched product and then reinstall the product without applying the patch. In this case,<br />

any patches that should not be removed must be reapplied.<br />

End users can uninstall patches through Add or Remove Programs on systems running Windows XP<br />

SP2 and later. For systems running Windows Installer 3.0 or later with earlier versions of Windows,<br />

patches must be uninstalled from the command line. For more information, see Uninstalling Patches in<br />

the Windows Installer Help Library.<br />

The uninstallation of patches is not enabled by default because not all patches can be uninstalled. For<br />

example, a major upgrade packaged as a patch cannot be uninstalled. It is recommended that you<br />

thoroughly test the uninstallation of your patch before deploying it to your end users. To learn more<br />

about patches that are not uninstallable, see Uninstallable Patches in the Windows Installer Help<br />

Library.<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 333

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

Saved successfully!

Ooh no, something went wrong!