Currently, Syncfusion provides Visual Studio Extension as Syncfusion Web Conversion and Migration to upgrade/downgrade the Syncfusion release versions in web applications. Please refer to the following user guide links to know more about Syncfusion Project Migration Visual Studio Extension:
In some specific projects (like 3rd party project templates, different web.config structure, modified project structure), migration process may fail by Project Migration extension. So, please follow the given steps to upgrade/downgrade Syncfusion version in Syncfusion Web applications manually:
For ASP.NET/ASP.NET MVC Platform
From your Syncfusion Web application, get the referred Syncfusion assemblies list, and remove the existing Syncfusion references. Then, add the corresponding Syncfusion assemblies with the required Syncfusion version. You can get the required Syncfusion assemblies from the following Syncfusion Essential Studio setup installed location:
For E.g: C:\Program Files (x86) \Syncfusion\Essential Studio\18.104.22.168\Assemblies (or) C:\Program Files (x86) \Syncfusion\Essential Studio\22.214.171.124\precompiledassemblies\126.96.36.199
The ASP.NET Core platform projects have direct NuGet references, by default. So, you can update the Syncfusion related NuGet references by following the steps mentioned in the link:
You can get and update the required Syncfusion Scripts and CSS files in your application in the following ways.
You can get the required Syncfusion Scripts and CSS files in your application from the following Syncfusion setup installed location. Once you navigate to this location, you can get the corresponding version scripts and CSS, and replace it in your required project location:
No need to make any master/view file reference changes for Syncfusion Scripts and CSS files references path, if you have updated the modified Script/CSS in the same location of existing Syncfusion assets in your application.
Syncfusion CDN Updates
ASP.NET Core application is referred Bower packages, by default. So, if you are using Syncfusion Bower packages in your web application, you can get the more details about upgrading packages to latest or specific version in the following user guide link:
Once you updated the assemblies to required Syncfusion version, you should update the same version of the assembly in the Web.Confg file of your application. ASP.NET WebForms and ASP.NET MVC applications have web.config, by default.
If you referred the Syncfusion WCF/WEBAPI files in our web application, you should update the same to corresponding Syncfusion version. You can get the required Syncfusion WCF/WEBAPI files in our application from the following Syncfusion Essential Studio setup installed location. Refer to the following locations to navigate the WCF and WEBAPI files for required version:
This page will automatically be redirected to the sign-in page in 10 seconds.