MSI Builder adds Product ID options for 2023

The information in this article applies to SAPIEN Script Packager in the 2023 versions of PowerShell Studio (5.8.214), PrimalScript (8.1.174), and later builds.

In a previous article, we introduced the new User Interface options in the 2023 SAPIEN Script Packager Installer. An additional change in the 2023 SAPIEN Script Packager is not related to user interfaces.

The Product Details page now enables you to change the Product IDs used by the generated MSI:


Review the information below before changing these values!

You should only change these values when you are absolutely sure that it is necessary. Otherwise, modifying them may break your installer or the ability to update older versions of your software.

A detailed discussion of Product Codes and Upgrade Codes can be found here:

In a nutshell, the Upgrade Code identifies the family of versions of your application, whereas the Product Code identifies the specific version. So, for example, MyTool 1.1.5 and MyTool 2.5.6 have the same Upgrade Code but different Product Codes.

Applications with the same Upgrade Code can only be installed ONCE on any given computer. If you properly changed the version number of your installer for a new build, a new Product Code will automatically be generated—you do not need to generate a new one yourself.

So, when do you need to change this?

  1. If you copied a project, including its .psbuild file, to create something new, you must regenerate the Upgrade Code—otherwise, the two product installers will interfere.
  2. If you want the previous version of your application to remain rather than be updated by a new version, you must regenerate the Upgrade Code.
  3. If you do not want to update the version number for some reason but want to trigger an update with a new installer, you need to regenerate the Product Code.


Do you have any suggestions or comments? Please use the Comment section below, or post in our support forums.