By following the best practices outlined in this guide, you will avoid the common pitfalls of double installations, failed patches, and irremovable software entries. Treat your Product Code with the same rigor as your source code—store it in version control, document its changes, and audit it before every build.
To understand the Product Code, it must be differentiated from other standard identifiers used in InstallShield projects Identifier Frequency of Change Product Code Identifies a specific version/flavor of a product. Change for major upgrades. Package Code Identifies a specific file/build. Change for every single build Upgrade Code Identifies the general "product family." Keep the same across all versions to allow upgrades. When to Change the Product Code installshield product code
: In some licensing scenarios, the product code can be used to identify the software for which a license is required. By following the best practices outlined in this
Now go forth and build flawless InstallShield setups. Change for major upgrades
