How to migrate from ASP.NET (Classic) to ASP.NET?
Steps for migrating the existing project in ASP.NET (Classic) to ASP.NET.
Currently, there is no easy migration path available for Essential Studio 12.2. The controls do not share the same API. So, you have to manually map the equivalent functionality in the new controls. However, when you share your application code (samples that use your controls), you may be provided with the equivalent code using the new controls.
In ASP.NET (latest), you don’t have separate DLLs for every controls such as, Syncfusion.Grid.Grouping.Web.dll and Syncfusion.Tools.Web.dll rather, you can use Syncfusion.EJ.Web.dll and Syncfusion.EJ.dll to hold all the controls in common.
Therefore remove the Syncfusion.Grid.Grouping.Web.dll, Syncfusion.Shared.Web.dll and other DLLs used by ASP.NET (classic) and also remove the namespaces from the web.config. Refer to the Syncfusion.EJ.Web.dll and Syncfusion.EJ.dll in the project.
The following table lists the required Namespaces, DLLs, script and CSS files to work with the ASP.Net control.
Syncfusion script files:
External Script files:
You can find the scripts and css files in the following locations:
DLL Location: C:\Program Files (x86)\Syncfusion\Essential Studio\22.214.171.124\Assemblies
In order to create an application in ASP.NET (latest) and configure the settings manually, refer to the following link:
For more information about the features available in ASP.NET (latest), refer to the following online sample link.