Creating and activating a license using an ASP.NET script on product purchase?

Comments

5 comments

  • Official comment
    Avatar
    John Michel

    Hi Luke

    AddUser, AddUserEx and AddUserEx2 are evaluations of our APIS throughout the years. To retain backward compatibility, we always introduce new methods and leave the old ones untouched. You can use any of the 3 methods but I would recommend the latest, i.e. AddUserEx2.

     

    Note that you can pass an empty email address and the license will not be associated to a user but it's obviously better to call AddUserEx2 first and then call CreateActivationKey...

     

    Yes, you can call these methods from the server.

     

    Regards

    John

  • Avatar
    John Michel (Edited )

    Hi Luke

     

    I would suggest that you call QlmLicense.CreateActivationKeyWithExpiryDateEx7 to create the Activation Key. The license key creation should ideally be done from your server rather than from the application.

    To activate the key, you would call QlmLicense.ActivateLicense from your application.

     

    Regards

    John

  • Avatar
    Luke D

    Hi John,

    Thank you for the reply! Based on what I can see, it looks like a user is required to exist before the activation key can be created, as it (obviously) needs to be tied to a user. I see there is QlmLicense.AddUser, AddUserEx, & AddUserEx2. What is the difference between these three methods? 

    Also, these are listed under the License Server Application API. I presume I can call them from our server however? 

    Regards,

    Luke.

  • Avatar
    Luke D

    Thanks for your help so far John.

     

    We're developing this serverside application in ASP.NET Core 2.1, and just running it now, we see that QlmLicenseLib seems to need .NET 4, specifically it's targeting System.Web.Services 4. Is there anyway to make QlmLicenseLib work under an ASP.NET Core environment? It's rather critical we get this running.

    Regards,

    Luke.

  • Avatar
    John Michel

    Unfortunately not. We do not support ASP.NET Core.

Please sign in to leave a comment.

Powered by Zendesk