User Guide

303
Patches
Note
This feature was developed and tested with the RC1 build of Windows Installer 3.0;
unexpected results may occur with the final version of the runtime. As of this release of Wise
for Windows Installer, Microsoft had not released the final version of Windows Installer 3.0,
therefore, it is not included in this product. To use this feature, obtain an RC or production
build of Windows Installer 3.0 from Microsoft and install it on your computer.
Also see:
About Patch Sequencing on page 303
Creating a Patch File on page 304
For additional topics, see Upgrading Applications on page 296.
About Patch Sequencing
" Windows Installer 3.0 or later.
Patch sequencing ensures that patches are applied in the correct order, regardless of the
order in which they are actually provided to the destination computer.
Sequencing is supported for small update patches only. Sequenced patches can be
installed by Windows Installer 2.0, but the sequencing is ignored.
You add sequencing information to a patch during Patch Creation. You can add
sequencing to a patch you created previously. Step through Patch Creation, open an
existing patch file, enter sequencing information, and complete the wizard to recompile
the patch.
Order in Which Patches Are Applied
1. Patches without sequence information are applied in the order they are provided to
the destination computer. Example: If Patch2 is provided before Patch1, they will be
applied in that order.
2. Sequenced patches are applied in sequence order.
Patch Families
A patch family is a group of patches that update the same, similar, or related
functionality of the application and should be applied in a specific order relative to other
patches in the same family. Most patches will belong to a single family, and most
applications will be updated by a single family. However, a patch can belong to multiple
families if it applies to more than one application or includes multiple fixes.
Example: Suppose you have 2 applications that are sold separately, but are also sold
together as a suite. Patches A and C only update Application1 and belong to family 100.
Patch B only updates Application2 and belongs to family 200. Patch D updates both
applications and belongs to family 100 and family 200.
You might sequence these patches as follows:
Patch Updates Family Sequence
A Application1 100 1
B Application2 200 1
C Application1 100 2