Article ID: 278686
This article was previously published under Q278686
This article describes how to correctly create a Visual Studio Installer (VSI) package to perform a small update or minor upgrade.
There are several codes to be aware of when upgrading a Windows Installer Package:
Package code: The package code is a GUID that associates an .msi file with a particular Microsoft® Windows® Installer package. This code must be changed in each package that you create no matter what kind of upgrade you are performing. This code is not made visible within the VSI interface. To modify this code you must use a tool such as ORCA, which enables you to directly modify the .msi database and change the Package Code property. For additional information on how to obtain and use ORCA, click the article number below to view the article in the Microsoft Knowledge Base:
255905Product code: The Product Code property is a String GUID that uniquely identifies a particular product release. This code only needs to be changed in a major upgrade package.
(https://support.microsoft.com/kb/255905/EN-US/ )How To Use the Orca Database Editor to Edit Windows Installer Files
If any of the rules for upgrading an .msi package are not followed correctly as stated in this article or in the Windows Installer Platform SDK, your package will not upgrade correctly. This may also produce multiple application entries in the Add/Remove Programs (ARP) utility in Control Panel. For additional information on the causes of duplicate ARP entries , click the article number below to view the article in the Microsoft Knowledge Base:
(https://support.microsoft.com/kb/300540/EN-US/ )PRB: Multiple Entries in the Add/Remove Programs Utility After a Windows Installer Update
Steps to Create an Update Package in VSIThe following steps will guide you through the process of creating a Visual Studio Installer package, followed by creation of an update/upgrade package.
Small Update/Minor Upgrade PackageA small update is an update to one or two files that is too small to warrant changing the product version number. A minor upgrade includes changes large enough to warrant changing the ProductVersion property.
NOTE: Once you modify the package in ORCA the changes won't be reflected when you edit your package in VSI. This is because ORCA edits the .msi directly, whereas VSI saves changes to a .wip project file and then builds the .msi from that.
Article ID: 278686 - Last Review: October 9, 2012 - Revision: 3.0
Retired KB Content Disclaimer
This article was written about products for which Microsoft no longer offers support. Therefore, this article is offered "as is" and will no longer be updated.