Trial license not detected
Problem reported by User21 - September 3 at 12:08 AM
Resolved
I can create an XSD in Liquid Studio 2020 - Developer Bundle (Trial).  And I can use Liquid XML Data Binding Wizard 2020 to create a C# solution, and build the solution in VS2019 to create the DLLs.
But when I try to use those DLLs in a C# project, I get:
and I get an exception "LiquidTechnologies.Runtime.Net45.LtException: 'Trial License Expired'".
I have restarted my computer, deleted the *.xsd.Output directory and *.xsd_NameMapping.cs.xml file, re-ran the Wizard, and rebuilt the solution.

My Enumerations.cs file has the following line:
            LiquidTechnologies.Runtime.Net45.XmlObjectBase.Register("Trial 17/09/2020", "NewFactoryConfig.xsd", "VAMFRHX3TD4RL9V1000000AA");

3 Replies

Reply to Thread
0
Liquid Support Replied
Employee Post
Hi,

What version of the product are you using?

I just tried this with the latest 18.0.12 and it worked OK using the generated SampleApp.

Also, we now recommend using Liquid XML Objects for C# code generation. You can generate the code directly from within Microsoft Visual Studio 2019 (or you can still use the Wizard).

0
User21 Replied
Thanks for the response.

I am using 18.0.11.10216.  I can try the latest version.
Also, the sample application doesn't seem to have any errors.

However after playing with this some more, I may have found where the problem is.  Our final product uses two DLLs produced from the Liquid XML Data Binding Wizard.  The first library was made by a contractor, who has a regular license.  The second library is the one I am working on using the trial version.  So I think the problem is the library the contractor delivered and/or the LiquidTechnologies.Runtime.Net45.dll that accompanies it is demanding there be a full license.  If I use the the LiquidTechnologies.Runtime.Net45.dll that was delivered alongside the first library in my final product, I get a build problem "Found conflicts between different versions of 'LiquidTechnologies.Runtime.Net45' that could not be resolved."  If I then switch to the LiquidTechnologies.Runtime.Net45.dll that is generated along side the library that I am working on, then there is just the trial license, and the first library fails when I try to use it at runtime due to an "expired trial license".


0
Liquid Support Replied
Employee Post Marked As Resolution
The runtime DLL version must exactly match the code generator version, and only one version of the runtime can be referenced by the application.

We recommend creating a 'Super Schema' which links to all of the XSDs required and then generates just 1 library as described in the documentation:

Please also see the following knowledge base article:


Reply to Thread