Deployment Automation

This functionality is only available on (or the text applies to) Windows (it is not available on Linux or macOS).

In order to automate the installation of the license, you first need to obtain the proper registry content that corresponds to it.

Use the License Manager utility on the development computer, and install the license you intend to distribute. Then, start the REGEDIT utility, navigate to the registry key for the license, select it, and perform File -> Export command. You will obtain a registration file (with .REG extension) that contains the license information.

Your installation program can then use this information in various ways. For example, it can invoke the REGEDIT utility, and pass it the name of the generated .REG file on the command line. Alternatively, you can use other methods that your installation program provides for manipulating the registry, and simply have it replicate the information contained in the .REG file to the target system.

The license must not be modified in any way. Changing any of its fields (such as the Subject name) will render the license invalid.

Note: Take care on 64-bit systems, as both 32-bit and 64-bit REGEDIT applications exist, and each has a different view of the registry.

Some customers have notified us that when using Visual Studio to create an .MSI Installer, exporting the license from the registry and importing it into the Visual Studio project has modified the license fields and caused the license to be not recognized by the component. When in doubt, compare the registry content created by the License Manager against the one created by your installer. They must be precisely equal.

When a license in the registry is damaged, the License Manager may still display it as valid; but the component will not recognize it in runtime.