Registration: upgrade to new major version

[Matthias Wagner]

Hi.

I took a project from my co-worker who is no longer in the company.
The project is with ASP.NET Core and Angular and i wonder how the registration works in this project. When i run the application, there are no hints to a trialversion, so the components seems to be registered.

But there is nothing like  

• "registerLicense('LicenseKey')" in the startup or somewhere else in the code 
• there is no environment variable set
• there is no license.txt in the folders
• nothing in the main.ts

In the near future we will eventually upgrade to a new major version and then at the latest i have to change registration.

Do you have any hints for me in which different ways the product could have been registered?

Regards

Matthias

[Nivetha Anandan]

Hi Matthias,

Find below response for your queries.

Q1) I took a project from my co-worker who is no longer in the company.
The project is with ASP.NET Core and Angular and i wonder how the registration works in this project. When i run the application, there are no hints to a trialversion, so the components seems to be registered.

But there is nothing like  

• "registerLicense('LicenseKey')" in the startup or somewhere else in the code 
• there is no environment variable set
• there is no license.txt in the folders
• nothing in the main.ts

A1) It seems that you are using Syncfusion package and script files from Syncfusion Essential Studio licensed installer. When we are using Syncfusion packages or script file from the licensed installer, there is no need to register the license key in the any of the above mentioned locations.

Also, by default, “SyncfusionLicense.txt“ file will be shipped in samples location with license key in it.

Q2) In the near future we will eventually upgrade to a new major version and then at the latest i have to change registration.

Do you have any hints for me in which different ways the product could have been registered?

A2) If you are upgrading the Syncfusion packages/script files from Syncfusion Essential Studio licensed installer, license key registration is not necessary. In this case trial license warning will not be displayed.

If you are using Syncfusion assemblies\NuGet packages from trial installer or from nuget.org , you should generate and register the corresponding version and platforms license key in your application to avoid trial license warning. 

Refer to this link for generating license key,

https://ej2.syncfusion.com/aspnetcore/documentation/licensing/how-to-generate

https://ej2.syncfusion.com/angular/documentation/licensing/license-key-generation

Refer to this link for registering license key,

https://ej2.syncfusion.com/aspnetcore/documentation/licensing/how-to-register-in-an-application

https://ej2.syncfusion.com/angular/documentation/licensing/license-key-registration

We have introduced license key validation for Essential JS2 platforms from the 2022 Volume 1 release. This licensing key validation will enforce the developer to register the valid licensing key in an application if you upgrade the Syncfusion any of the latest packages, either from npm or CDN.

Refer to the following blog for more information,

https://www.syncfusion.com/blogs/post/introducing-license-key-validation-for-the-essential-js-2-platforms.aspx

If the license key is not properly registered, the below license errors will be displayed.
https://ej2.syncfusion.com/aspnetcore/documentation/licensing/licensing-errors

If you are facing any licensing warning even after registering the proper license key, refer to the below links.

Find below the knowledge base article to know about which version license key should use in application,
https://www.syncfusion.com/kb/8951/which-version-syncfusion-license-key-should-i-use-in-my-application

Follow the below knowledge base article to resolve the license warning message.

https://www.syncfusion.com/kb/12756/how-to-resolve-syncfusion-license-popup-message-or-trial-message-warning

Let us know if you need further assistance.

Regards,

Kalap Johnson Peter P.