expressappframework-401253-migration-to-net.md
XAF v25.2 introduces many changes. Before upgrading, you need to make specific changes to your application in v25.1. The migration process has several steps: you can use the XafApiConverter tool to automate some tasks and simplify the update, but manual code review and adjustments are still required.
Ensure that the following components are installed on your machine:
The major changes are listed below. For the complete list of removed APIs, refer to the following knowledge base article: XAF - Legacy .NET Framework (WinForms and ASP.NET WebForms) APIs, .NET-based API/Modules, and Security System have been removed from distribution.
End of .NET Framework support
End of Entity Framework 6 (EF6) support
The following modules have been removed from XAF:
Security System, which includes built-in user and role types other than PermissionPolicyUser and PermissionPolicyRole or the legacy SHA-512 password hashing algorithm has been deprecated
Built-in business classes have been removed
The legacy Solution Wizard no longer allows you to create new XAF project and item templates. Instead, use the new DevExpress Template Kit that is now automatically added as a Visual Studio extension by our Unified Component Installer.
For additional information, refer to the following help topic: Template Kit.
Note
The new Template Kit also supports Rider and VS Code.
We developed a tool designed for those migrating an XAF application to v25.2+. It automates the following routine migration tasks:
You can find the tool source code in the following GitHub repository: XafApiConverter. Refer to the repository description for additional information about the XafApiConverter tool.
See the following help topics for information on the corresponding upgrade scenarios:
See Also
Modernize .NET apps effortlessly with GitHub Copilot
Start Your Cloud Journey with Azure App Service
Migrating from ASP.NET to ASP.NET Core tutorial playlist on YouTube