Hi
We are trying to upgrade a v19 Web Forms application to v20.
Can you advise how we license an application using Web Forms (EJ1) packages. Any license key we generate in our account does not seem to work. There does not seem to be an option for Web Form applications any more?
Thanks
Mike
Hi Mike,
The similar problem was reported in your account's support ticket. Please look into it further.
Regards,
Jeyaseelan M
I'm having the same problem on version 22.1.34 the last valid for a ASP.NET Web Forms project, how can I fix it?
Hi Pio,
We had an issue with the regional date and time format in v22.1.34 during the license validation process. However, we have successfully resolved this issue, and it has been included in the weekly release v22.1.36.
When you have license issues with v22.1.34 packages, please install the Syncfusion.Licensing v22.1.36 or later from nuget.org and update all dependent NuGet packages to the same version.
Please refer the following KB article for this.
Invalid license issue when using 22.1.34 syncfusion.licensing package | Syncfusion
Syncfusion license keys are version and platform-specific . Ensure that all the referenced Syncfusion assemblies\NuGet packages are all on the same version(22.*.*) as license key’s version(22.*.*) in your project.
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
Regards,
Jeyaseelan M
Even if I update the Syncfusion.licensing library to the latest version, I get the invalid license key message, because I can't update the web forms solution beyond version 22.1.34 via NuGet. In addition, in the form to generate the key, it is not possible to choose ASP.NET web form as the platform.
Pio,
Q1) I can't update the web forms solution beyond version 22.1.34 via NuGet.
A1) We have deprecated the “ASP.NET WebForms” packages in our library from 22.1.34, and they are out of service, and we do not update this package anymore.
Could you please share the list of NuGet packages that have not been updated via NuGet? We will check with the respective product team and share their response.
Q2) In addition, in the form to generate the key, it is not possible to choose ASP.NET web form as the platform.
A2) Once you have updated all the NuGet packages to version 22.1.36 or later, you can use the same license key from version 22.1.34. There is no need to generate a separate key specifically for version 22.1.36.
If you are updating to a major version (22.x, 23.x, 24.x), you need to generate and register the license key for that version.
Additionally, you can choose the ASP.NET platform when generating a license key for any version.
Let us know if you have any queries on this.
These are the libraries that have not been updated via NuGet :
Pio,
We encountered a regional issue with the Syncfusion.Licensing nuget alone. Could you please update this nuget to version 22.1.36? For other ASP.NET packages, you can use version 22.1.34 and register the license key v22.*.* in your application.
To know about registering
the license key,
https://help.syncfusion.com/common/essential-studio/licensing/how-to-register-in-an-application
Please inform us if you encounter any failures in this process.
As I indicated in previous posts, I can update the libraries up to version 22.1.34, except for the "Licensing" library which I updated to the latest available (v. 23.1.40), but the key generated for version 22.1.34 is invalid.
Pio,
As mentioned earlier, please update
only the licensing library to version 22.1.36, not the latest version
If you choose to update the licensing to the latest version (23.1.40), you will
need to update all the referred NuGet packages as well as the license key, as there
has been a major version change.
Example: Upgrading from 22.1.* to 23.1.*
you should update the license key as well.
Refer to the below KB article to know which version license
key should use in the application,
https://support.syncfusion.com/kb/article/7865/which-version-syncfusion-license-key-should-i-use-in-my-application
But in your case, you cannot upgrade to 23.1.* since we have deprecated ASP.NET packages. So kindly upgrade Syncfusion.Licensing package to 22.1.36 and other ASP.NET packages to 22.1.34.
Ok, very well !!
Thank you for supporting me.
You're welcome!! Pio
Please feel free to contact us if you need any other assistance.