Which version License Key should I use in my application?
Syncfusion has introduced the licensing system from the version 16.2.0.41. So, you should register the valid license key in your application to permanently remove the license exception message if you are using Syncfusion evaluation installer or NuGet packages.
The Syncfusion license key is version-specific. So, you need to regenerate the licensing key for every new volume release.
Upgrading to Volume release | v16.2 to 20.4: If you are using the application from Syncfusion version 16.2.0.* and trying to upgrade to our next volume release version 16.3.0.*, you should generate the license key for v16.3.0.* and update the key in your application. For example, if you are using v16.2.0.41 and trying to upgrade to the next volume release, v16.3.0.21 you need to regenerate the licensing key for v16.3.0.* from our website and update the licensing key in your application. 21.*.* later: Syncfusion introduced sematic versioning from 21.*. So, if you are using the application from Syncfusion version 21.*.* and trying to upgrade to our next volume release version 22.*.*, you should generate the license key for v22.*.* and update the key in your application. For example, if you are using v21.1.35 and trying to upgrade to the next volume release v22.1.34 you need to regenerate the licensing key for v22.*.* from our website and update the licensing key in your application. |
Upgrading to Service Pack\NuGet release | v16.2 to 20.4: Our Volume release licensing key (16.2.0.*) can be applied to it’s service pack\nuget releases. If you are using the application from Syncfusion version 16.2.0.* and trying to upgrade to it’s service pack\nuget release in the same volume release, there is no need to regenerate the license key again. 21.*.* later: Syncfusion introduced sematic versioning from 21.*. and our Volume release licensing key (21.*.*) can be applied to it’s service pack\nuget releases. If you are using the application from Syncfusion version 21.*.* and trying to upgrade to it’s service pack\nuget release in the same volume release, there is no need to regenerate the license key again. For example, if you are using v21.1.35 and trying to upgrade to it’s service pack\nuget release in the same volume release v21.2.3 or v21.2.4, there is no need to regenerate and apply the license key again for service pack\nuget releases. |
Please follow the steps to generate the license key:
1. Generate the license key from License & Downloads section of the Syncfusion website. Refer to the following screenshot.
2. Choose the version for which you want to generate the license key, and then click GET LICENSE KEY.
3. Get the License key, which is shown at the bottom of the pop-up window. This is your license key.
The generated license key is just a string that should be registered before any Syncfusion control is initiated. Kindly follow the licensing help document to register the key in the application.
