Patching and Upgrades
Because an installation package can contain the files that make up an application as well the information needed for their installation, Windows Installer can be used to update the application. The installer can update information in the following parts of the installation package:
- The .msi file.
- The files of the application.
- The Windows Installer registration information.
The type of update can be characterized by the changes the update makes to the application's product code, product version, and package code. The application's product version is stored in the ProductVersion property. The application's product code is stored in the ProductCode property. The application's package code is stored in the Revision Number Summary Property.
An update that changes the application into another product is required to change the ProductCode of the application. For more information about which updates require changing the ProductCode see Changing the Product Code. The update can change the ProductVersion and leave the ProductCode unchanged if future versions of the application will need to differentiate between the updated and nonupdated versions of the current product. The Package Code uniquely identifies the installation package and should always be changed whenever update or upgrade changes any information in the installation package.
When deciding whether to change the product version, you should consider If future versions of the application will need to differentiate between the updated and nonupdated versions of the current product. To ensure differentiation in the future, a minor upgrade should be used instead of a small update.
- If an update changes the .msi file and application files, but does not change the ProductCode property or ProductVersion property, it is termed a small update.
- If the update changes the ProductVersion, but does not change the ProductCode, it is termed a minor upgrade.
- If the update changes the installation into an entirely different product, the ProductCode must change and the update is termed a major upgrade.
The following table summarizes the different types of updates.
|Type of update||Productcode||ProductVersion||Description|
|Small Update||No change||No change||An update to one or two files that is too small to warrant changing the ProductVersion. The package code in the Revision Number Summary Property does change. Can be shipped as a full installation package or as a patch package.|
|Minor Upgrade||No change||Changed||A small update making changes significant enough to warrant changing the ProductVersion property. Can be shipped as a full installation package or as a patch package.|
|Major Upgrades||Changed||Changed||A comprehensive update of the product warranting a change in the ProductCode property. Shipped as a patch package or as a full product installation package.|
Users can update to an application by reinstalling a Windows Installer package for the application. Note that Minor Upgrades can be applied in the same way as Small Updates. For more information about updating an application by reinstalling the application, see these sections:
- Applying Small Updates by Reinstalling the Product
- Applying Major Upgrades by Installing the Product
An update to an application can be provided to users as a Windows Installer patch package. A patch can contain an entire file or only the file bits necessary to update part of a file. This means that the user can download an upgrade patch that is much smaller than the entire product and that preserves user customizations through the upgrade. Note that Minor Upgrades can be applied in the same way as Small Updates. For more information about updating an application using a patch, see these sections:
- Creating a Small Update Patch
- Applying Small Updates by Patching the Local Installation of the Product
- Applying Small Updates by Patching an Administrative Image
- Applying Major Upgrades by Patching the Local Installation of the Product