Windows Installer Editor Reference
60
Setting Up
previous .MSI is matched and the component key is set to match the previous version.
All new resources you add to the upgrade installation will be checked against the
previous installations.
To ensure that all resources you add to an upgrade installation are aligned with previous
versions, specify the previous installation versions before adding any resources to the
installation. If you have already added resources to the installation, as is the case when
you use a copy of a previous .WSI as a starting point for creating an upgrade
installation, you must run UpgradeSync to align GUIDs for existing components.
To use component rules to align GUIDs in an upgrade
1. Create or open the upgrade installation.
2. If you have already added resources to the upgrade installation, run UpgradeSync
to align GUIDs for existing components.
See
UpgradeSync
on page 333.
3. Select a rule set to use for this upgrade.
See
Selecting a Component Rule Set
on page 58.
Make sure the rule set you select contains a rule for aligning component GUIDs with
previous versions; this should be the first rule in the rule set.
For best results, use the same rule set, if any, that was used in the previous
versions. That way, component creation in the upgrade will be consistent with the
previous versions.
4. Select Component Rules menu > Previous Versions.
In Visual Studio: Project menu > Component Rules > Previous Versions.
The Previous Installation Versions dialog box appears.
5. On the Previous Installation Versions dialog box, specify the previous versions of
this installation.
To add a previous version .MSI to the list, click Add, click
to browse to the
.MSI, and click Open. The .MSI is added to the list.
The previous versions will be checked in the order they appear in this list.
6. Click OK on the Previous Installation Versions dialog box.
All new resources you add to the upgrade installation will be checked against and
aligned with the previous installations you specified.
See also:
Component Rules
on page 57
Customizing Component Rules
If the predefined component rule sets do not reflect your organization’s standards, you
can create a new rule set. The predefined rule sets, Microsoft Best Practices and One file
per component, are read-only and cannot be modified. However, you can copy a
predefined rule set and modify the copy.
When creating new rules, refer to Microsoft’s rules for creating components.