Hello,
thanks for update. I am glad that it works now.

I currently have no explanation why the exact resource name was necessary.

Best regards
 

Support

Thanks so much for the feedback. I finally got it to load the license correctly. 

I did have the file marked Build Action: Embedded Resource. I did find it in the Manifest file via ILDASM, was checking wrong resource file version. 

The issue was the code was not loading it for some reason. It was then defaulting to the registry entry of the old license. 

I finally got it to load in the published runtime application by hardcoding the exact entry from the Manifest. The wildcards weren't finding it, possibly because it was in a folder - ?

thank you for your help. 

 

Hello, thanks for additional info. 

(First, a clarification: We use the term "trial license" for the license with 30-minute runtime limit - this one is built-in, normally there is no separate license key file for it. We use the term "evaluation license" for a license key that has no such limit, but instead is limited by an absolute date in the future - typically 30 days - this is the one we have sent you). 

The word "WebForm" in the license key file refers to how it was generated internally. It has no relation to whether your program uses Web Forms. 

If you are getting wrong links for documentation pages, it is because documentation for some old QuickOPC versions has been removed. Use the current documentation instead ( www.doc-that.com/files/onlinedocs/OPCLabs-ConnectivityStudio...html#Licensing%20Elements.html ), the parts that you need are largely the same. 

If you do not see the license key resource in the ILDASM output, then it is understandable that we don’t' find it: it is  simply not there. You wrote that you have set the build action to Embedded Resource (on the license key file I suppose), and that should be enough. But frankly, I believe you have done something wrong there. Please double-check this. In any way, the license key must appear in the ILDASM output as a resource. It is done completely using VB.NET / C# build tools, and is thus outside of our control. If you do not find a reason, I suggest that you send me you project file privately. 

If the embedded license (resource) is not found, the next where we look is the License Manager (registry), so if you have your old license there, that's what we end up using. Best regards

More info: 

1. I have an ASPX application using VB.NET. I am not using webforms. I noticed my trial key has "webforms" in it : "Key-Evaluation-WebForm-xxxxxxxxxx-xxxx.bin"
Does that matter? Is this causing an issue? 

2. I tried to embed the trial key file into my project by adding the key file as an existing file (after copying it to the project directory) in a folder named "opclabs_license" . I then set the property build action to embedded resource. I then added the registration code to my application start method as per the advice of a web search:

  ' Register the license using a wildcard pattern
        ' Parameters: Product Name, License ID, Assembly, Resource Name Pattern
        LicensingManagement.Instance.RegisterManagedResource("QuickOPC", "Multipurpose", [Assembly].GetExecutingAssembly(), "*.Key-*.*")

  ' Optional: Verify it worked by checking the serial number
            Dim client As New OpcLabs.EasyOpc.UA.EasyUAClient()
            Dim sn As Long = CLng(client.LicenseInfo("Multipurpose.SerialNumber"))
            'If sn = xxxxxx871, the key is active
            MessageBox.Show("License SN: " & sn)

In VS2017 I can run the project and will get the correct serial number on the MsgBox IF I load the trial license into license manager. So it seems that registration code isn't working and it's looking at the license manager. When I clean and recompile, I don't see the resource registered in the project DLL that is compiled using ILDASM. 

When I publish, I STILL get the error code ABOUT dropping my old license (xxx924) and doesn't mention the new one. Not allowed to run by the license "Multipurpose". You might be running a trial license, and the version of the software you are using is obsolete. To resolve this problem, a) obtain a recent version, or b) ask for an evaluation license key, or c) install a license valid for the current version.
Product information follows. Component name: "QuickOPC", license IDs: "Multipurpose", version number: 562, release date: 11/13/2021, trial validity: 397 days, option expression: "EasyUAClient".
Context: 1 dropped license(s); S/N xxxxxxx924 (release date covered 2/8/2020).
+ The client method called (or event/callback invoked) was 'BrowseMultiple[1]'.


what is the accepted method of registering the license in the code for the version I have?

Is the old license in my code causing interference with the new trial license? I cannot find in the code where the old license was embedded.

ANY HELP would be appreciated!!

Thanks for your reply!

I'm sure that is my problem, however I cannot find in my original code (from 2019) where theEasyOPC license is embedded. 

Based on some google searches, I searched for and did not find the following search terms. How do I find where the original license code was embedded? OR, Were the older versions of EasyOPC registered differently?? (these search items referred to Quick OPC rather than EasyOPC... I did search for EasyOPC. 

• Code:

  LicensingManagement
  : This is the primary class used for license registration.
• Code:

  RegisterManagedResource
  : This method embeds the license as a managed resource within your assembly.
• Code:

  RegisterManagedResourceWithExistenceCheck
  : A safer version of the above that verifies the resource exists.
• Code:

  Multipurpose DO I just need to embed the new trial license ? Thanks for your help!

Hello,

it looks like that QuickOPC does not "see" the evaluation license key installed through License Manager.

Are you embedding your original license key inside your project? If so, the embedded key takes precedence. You need to embed the evaluation license key instead in such case.

Best regards

Hi, I am new to the forum. I have a license for EasyOPC back in 2019. I have upgraded to v 5.62 for compatibility with Server 2022.

I received a 30 day trial license for version 5.62 (an all versions). I can run the app in Visual Studios. But when I publish the app, I have issues. I have loaded the new trial license in License manager, and it shows in the license manager app. but the app throws an error. is this because I cannot use a trial license in a published app???
Is there something in the code I need to do in order for this to work? very link I visit about this seems to be broken. Not allowed to run by the license "Multipurpose". You might be running a trial license, and the version of the software you are using is obsolete. To resolve this problem, a) obtain a recent version, or b) ask for an evaluation license key, or c) install a license valid for the current version.
Product information follows. Component name: "QuickOPC", license IDs: "Multipurpose", version number: 562, release date: 11/13/2021, trial validity: 397 days, option expression: "EasyUAClient".
Context: 1 dropped license(s); S/N 1999223924 (release date covered 2/8/2020).
+ The client method called (or event/callback invoked) was 'BrowseMultiple[1]'.

I would like to be able to send my app to my customer to have them verify that it works with Server 2022 before I buy the license.

Any help would be appreciated!