.NET Support and Migration from .NET Framework
- 2 minutes to read
Prerequisites
Ensure that the following components are installed on your machine:
DevExpress Unified Component Installer v24.2+ or DevExpress NuGet feed.
.NET Core/.NET projects rely on NuGet package references instead of assembly references in the .NET Framework. The installer’s DevExpress 24.2 Local package source (offline) or your personal DevExpress NuGet package source (online) includes XAF-specific packages: https://nuget.devexpress.com/packages?q=xaf.
XAF applications created using the Solution Wizard already contain required NuGet package references based on the selected UI platforms, modules, and other wizard settings. You can also include additional DevExpress and third-party package references manually.
- .NET SDK and runtime
- Visual Studio 2022 v17.0+
Tip
Are you currently using the .NET Framework, and are you ready to transition to .NET or move your solutions to the Cloud?
We recognize that migrating/rewriting legacy applications can be a significant undertaking. If you are ready to transition to newer versions of .NET or move your solution to the cloud, be sure to review the following highly rated help topics:
- .NET Upgrade Assistant Tool
- Start your cloud journey with Azure App Service
- ASP.NET to ASP.NET Core tutorial playlist on YouTube
- Reliable Web App pattern (RWA) on GitHub (a guidance for building around existing apps without the need for a complete rewrite)
This section includes the following topics:
- Port an Existing XAF Application to .NET 6
- Reuse an XAF Shared Module between .NET Framework and .NET Applications
- Add a New .NET XAF Module to an XAF Application
- Create a Combined .NET WinForms and Blazor Solution
Important Notes
The following design-time functionality is not available because of the changes to Visual Studio’s designer architecture in .NET: Module and Application designers, Controller and Action designers, and EasyTest debugging commands. You can perform related tasks in code: