Professional OPC
Development Tools

logos

Online Forums

Technical support is provided through Support Forums below. Anybody can view them; you need to Register/Login to our site (see links in upper right corner) in order to Post questions. You do not have to be a licensed user of our product.

Please read Rules for forum posts before reporting your issue or asking a question. OPC Labs team is actively monitoring the forums, and replies as soon as possible. Various technical information can also be found in our Knowledge Base. For your convenience, we have also assembled a Frequently Asked Questions page.

Do not use the Contact page for technical issues.

DUE TO ADMINISTRATIVE REASONS, WE MAY NOT BE ABLE TO RESPOND (OR TO RESPOND AS QUICKLY AS USUAL) BETWEEN July 31 - August 11, 2021. WE APOLOGIZE FOR INCONVENIENCE.

Single Developer license as embedded resource

More
26 Aug 2020 15:46 #8794 by support
Hello,
if this is done the usual way (which is the way described in the documentation and the one you have also summarized in your post), then the answer is simple: Yes.

In this case, the license key is originally stored alongside any other source files in your source control system.
And the instructions/configuration (as to the fact that the license key is a resource to embed into the binary) are part of normal Visual Studio solution file. As such, VS will build it locally, but also the compilation process will follow the VS solution and do the same.

Best regards
The following user(s) said Thank You: Cavallari

Please Log in or Create an account to join the conversation.

More
26 Aug 2020 10:57 #8793 by Cavallari
We have one question about QuickOPC license management: we would like to purchase a "Single Developer + Runtime Free License" for using the QuickOPC Standard in a .NET application that we are developing. The goal is to be able to deploy a fully licensed executable that does not need any runtime license installed on the target machine (i.e. without any additional installation step related to QuickOPC license distribution).

From the description of the Managed Resource License Store found here:

Managed Resource License Store

I understand that the .BIN license file (received after the QuickOPC purchase) must be simply embedded inside the solution of our application, then a small piece of code must be arranged in order to activate the license at runtime.

The matter is that we are using a continuous integration system on which application is automatically built after it is committed from the developer machine. I wonder if placing the license binary inside the application solution does guarantee that also the binary generated by the compilation process from the integration system will be fully licensed as if it was compiled on the development machine.

Thank you for support.

Jacopo

Please Log in or Create an account to join the conversation.

Moderators: support
Time to create page: 0.156 seconds