The second install will fail with a message that the product is already installed, or it will trigger a self-repair. Fix: If you need multiple builds (e.g., Developer vs. Production), you must either use different Product Codes or use instance transforms (MSI).
To manage installations effectively, you must understand how the Product Code differs from other crucial deployment identifiers:
: For products offered in multiple configurations, separate product codes may be required for each configuration.
The Product Code should be treated with care. , as it breaks the link between the installer and the already-installed product. Once you change a project's GUID, its previous GUID cannot be recovered. If you change the Product Code without proper upgrade logic, Windows Installer treats the new version as an unrelated product, potentially leading to multiple entries in the "Add or Remove Programs" list and causing installation conflicts.
When in doubt, let InstallShield guide you: If you check "Major Upgrade" in the Release Wizard, it will automatically generate a new Product Code for you.