Dlls distribution and API improvements

Hi! We use Cryptlex for our C# project. Currently we handle our 3rd party dependencies using internal Nuget server, so I have to pack the dlls manually each time a new version is released.

I want to simplify this and have a few proposals/questions:

Q1: Do you plan to start distributing Cryptlex dlls via Nuget?
Q2: Do you plan to create a native C# wrapper for your API so I don’t have to copy/paste interop code into my projects from demos and deal with it’s lower level API?
P1: For float client - please add corresponding methods to query server’s stat. Now I have to do separate web request to get license expiration time - this is very annoying.
P2: For float client - I don’t like the overhead of making a server query per each custom field to obtain a value. Can this be optimized? Ideally, all the fields should be transferred at the time of license lease.
P3: Can you embed a product version into dlls? This will help me in build automation.
P4: Can you post release notes somewhere on the site (not only in emails you send).

Thank you!

Best regards, Alex.

Hi Alex,

Q1: Do you plan to start distributing Cryptlex dlls via Nuget?

Actually, creating a LA_ANY based package is bit tricky for C dlls in nuget, so it may not be a planned, but will give it a try.

Q2: Do you plan to create a native C# wrapper for your API so I don’t have to copy/paste interop code into my projects from demos and deal with it’s lower level API?

We are not planning to create any native wrapper.

P1: For float client - please add corresponding methods to query server’s stat. Now I have to do separate web request to get license expiration time - this is very annoying.

Server stats api is meant for server administration, something which is not supposed to be done from float client

P2: For float client - I don’t like the overhead of making a server query per each custom field to obtain a value. Can this be optimized? Ideally, all the fields should be transferred at the time of license lease.

This would be breaking change, can’t be added.

P3: Can you embed a product version into dlls? This will help me in build automation.

Product version is different across each version of product. How can it be embedded?

P4: Can you post release notes somewhere on the site (not only in emails you send).

Will create a changelog text file and add it to the sdk.

P3: Well, the question here is that given a particular dll how could I obtain its version?

Please have a look at this msdn arcticle: https://msdn.microsoft.com/en-us/library/aa381058(VS.85).aspx

Misinterpreted your proposition. We will add the version to the dll’s starting from next release.

Thank you!

Next release has come, but there is still no product version embedded and no changelog file.

Hope you didn’t forget about this.

Fixed, please download the latest build

I just downloaded Cryptlex and signed up, and I’m putting license management on a VSTO add in for Microsoft Office. I’ve never done this before, and saw this thread about embedding the product version. Does this mean I can embed the product.dat information into my build? I’m not sure where this file goes and how to include it in my release package. Thank you.

Hi,

Product.dat can’t be embedded as of now.