For a , such as a critical hotfix that replaces a single file, the Product Code should remain unchanged . For a minor upgrade , like moving from version 1.1.0 to 1.2.0, the Product Code should remain stable . The existing Product Code will be used to find the already-installed product on the system and apply the changes.
Navigate to the following key for 64-bit systems or 32-bit applications on 32-bit systems: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Uninstall
If you've ever wondered how Windows knows an app is already installed, or how to properly upgrade an old version without breaking everything, the answer lies in mastering the product code. This article will serve as your complete guide to the InstallShield product code, explaining what it is, why it's so important, and how to manage it correctly in your own projects.
Uniquely identifies the product itself. A different Product Code indicates a completely different product. installshield product code
Go to Project > InstallShield MSI Project > General Information > Product Code and click "New GUID." Then navigate to Media > Releases > Upgrades and create a new upgrade item. Set "Detected product code" to the old version's Product Code.
When you create an , the Product Code is a property stored in the MSI database. Windows Installer uses this code to recognize the product. According to Microsoft's standards:
Developers often confuse the three core GUIDs used in Windows Installer packages. Each serves a distinct purpose in the application lifecycle: Scope of Uniqueness When to Change It Unique to every single .msi file built. Change automatically with every compilation. Product Code Unique to a specific version of a product. For a , such as a critical hotfix
Change the Product Code if it is a major upgrade, or increment the Product Version if it is a minor upgrade. Uninstallation Leaves Leftovers
Changing a Product Code after a product has shipped is a serious decision that effectively signals the birth of a new product, breaking the chain of upgrades for the previous version. By following the guidelines and best practices outlined in this guide, you can leverage the full power of the Product Code to build a robust, reliable, and professional installation experience for your users.
A represents a significant change to your product, for example, from version 2.0.0 to 3.0.0. In this scenario, you must generate a new Product Code . The Windows Installer treats two products with different Product Codes as entirely separate, unrelated products. For a major upgrade, you change the Product Code because you want the new version to install "alongside" the old one, and then a special upgrade table uninstalls the old version. You will also need to set up the Upgrade Paths in your project to tell the new installer which old Product Codes (or Upgrade Code version ranges) it should remove. Navigate to the following key for 64-bit systems
Do not copy an existing InstallShield project file to start a new application without explicitly clicking the "Generate New GUID" button next to the Product Code property. Troubleshooting Common Product Code Issues
Understanding the InstallShield Product Code: A Complete Guide for Developers