QuickOPC User's Guide and Reference
Registry License Store
Application Deployment > Licensing Elements > Registry License Store
In This Topic
This functionality is not available under (or the text does not apply to) .NET Standard development platform.

Manual License Deployment

When you use the Registry License Store, proper license (for runtime usage) must be installed on the target computer (the computer where the product will be running).

The standard method for installing the QuickOPC license on runtime machines is manual: The user runs the License Manager utility (GUI or console-based), and installs the license by pointing the program to the license file stored on the disk.

If you have multiple QuickOPC versions installed on the computer, you need to deploy the license that covers them all.

The subsequent part of the documentation describes how to automate the above procedure so that the user does not have to interact with the License Manager utility.

Registry Key

The license is stored in the registry, under the following key:

HKEY_LOCAL_MACHINE\SOFTWARE\Licensing\QuickOPC\Multipurpose

In order to install the license, this key and anything that is beneath it, must be properly deployed to the target machine.

Note: On 64-bit systems, the license is stored in 32-bit registry. When the registry is accessed from 64-bit application, you must use the following key instead:

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Licensing\QuickOPC\Multipurpose

On 64-bit systems, if QuickOPC is used from both 32-bit and 64-bit processes, you have to install the license into both 32-bit and 64-bit parts of the registry.

Access to the License

The license is stored in the registry. For the license to be recognized, the process (that runs QuickOPC) must have read access to the corresponding registry keys. That is normally not a problem under "interactive" user accounts and traditional desktop applications, but it can be an issue when QuickOPC runs as Windows service, or in hosted environments (such as IIS).

Specifically, IIS has one process for each Application Pool, and the application pool runs under a configurable user account. You need to assure that this user account has read access to the registry keys where the license is stored.

 

See Also

Examples - Licensing