Wise Package Studio Reference
129
Wise Package Studio Tools
If you compiled the installation as an .EXE, you need the .MSI for the installation
because Patch Creation does not operate on .EXE files. The .MSI is created in the
same directory as the .EXE during compile.
Patching assemblies in the Global Assembly Cache
¾
Windows Installer 3.0 or later.
Prior to Windows Installer 3.0, it was difficult to patch assemblies that were installed in
the Global Assembly Cache (GAC), because the files could not be found.
When you patch an assembly that is installed in the GAC, Windows Installer 3.0
identifies and finds the original file and applies a binary patch. This eliminates the need
for Windows Installer to access the original installation source in order to patch an
assembly installed in the GAC. See MsiPatchOldAssemblyName Table and
MsiPatchOldAssemblyFile Table in the Windows Installer SDK Help.
For additional topics, see About Upgrading Applications in the Windows Installer Editor
Help.
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 two 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:
Содержание SOFTWARE MANAGER 8.0 - REFERENCE FOR WISE PACKAGE STUDIO V1.0
Страница 1: ...Wise Package Studio Reference ...
