Table of Contents
Advertisement
UpgradeSync
Using UpgradeSync
Windows Installer Editor Reference
Using UpgradeSync is one of the steps in preparing software for updates.
See
Preparing for Software Updates
UpgradeSync compares the current package with the previous version of the package,
and does the following to prepare the current package for a patch or upgrade:
Changes the PackageCode, ProductCode, and ProductVersion properties if
necessary.
Aligns component GUIDs. If GUIDs or key paths for the same component don't
match between the new and old .MSI, the component could inadvertently get
deleted because Windows Installer does not recognize the components as being the
same. Aligning component GUIDs for matching components prevents upgrades from
deleting necessary files in the newer version.
Detects errors that could cause problems with a patch or upgrade and, if possible,
fixes them.
Note
UpgradeSync does not create an upgrade or patch; it eliminates the most commonly
encountered problems that cause patches and upgrades to work incorrectly. Use
UpgradeSync before you create a patch or an upgrade. Use Patch Creation to create a
patch and the Upgrades page to create an upgrade.
For information on the different types of updates and when to change the ProductCode
and ProductVersion, see Patching and Upgrades in the Windows Installer SDK Help.
UpgradeSync changes your current installation according to Microsoft's
recommendations, based on the type of upgrade you plan to make.
When you add new resources to an upgrade installation, you can use component rules to
ensure that the component GUIDs are aligned with those in previous installations.
See
Using Component Rules to Align GUIDs in an Upgrade
See also:
About GUIDs
on page 548
Using UpgradeSync
Using UpgradeSync
1.
Open the current version of the installation file (.WSI or .MSI).
2.
Select Tools menu > UpgradeSync. (In Visual Studio: Project menu >
UpgradeSync.)
The Welcome page appears.
3.
In Previous MSI path, specify the path of the previous .MSI.
You must specify an .MSI here, even if you deployed the installation as a single-file
.EXE. The .MSI is created in the same directory as the .EXE during compile.
4.
Click Next.
The Upgrade Type page appears.
on page 330.
on page 59.
Upgrading Applications
333
Advertisement
Table of Contents
Troubleshooting
