.NET/.NET Core Support
- 6 minutes to read
Prerequisites
The table below shows the versions of DevExpress WPF Controls that support .NET/.NET Core.
| DevExpress Version | .NET Core 3.0 | .NET Core 3.1 (LTS) | .NET 5.0 | .NET 6.0 (LTS) | .NET 7.0 | .NET 8.0 (LTS) | .NET 9.0 (current) |
|---|---|---|---|---|---|---|---|
| v24.2 (current) |  |
|
|
|
|
 |
|
| v24.1.8+ | |
|
|
|
|
|
|
| v23.2-v24.1.7 | |
|
|
|
|
|
|
| v22.2-v23.1 | |
|
|
|
|
|
|
| v21.2-v22.1 | |
|
|
|
|
|
|
| v20.1-v21.1 | |
|
|
|
|
|
|
| v19.2.5+ | |
|
|
|
|
|
|
| v19.1-v19.2.4 | |
|
|
|
|
|
|
Prerequisites to build .NET Core applications:
- .NET/.NET Core
- Visual Studio 2022 v17.0+ (includes support for .NET 6.0)
- Visual Studio 2022 v17.4+ (includes support for .NET 7.0)
- Visual Studio 2022 v17.8+ (includes support for .NET 8.0)
Getting Started
The Getting Started topic explains how to start using DevExpress WPF UI controls in a .NET WPF application.
Migrate an Existing Application to .NET
The following topic describes how to migrate an existing WPF Application to .NET: Migrate WPF Applications to .NET.
Deployment
The following topic describes how to deploy your .NET WPF application: Deploy .NET Applications.
Limitations
The ApplicationJumpListService is not supported.
Create Custom Themes for .NET Applications with the Theme Designer
- Install DevExpress WPF Controls for the .NET Framework.
- Build and publish your custom theme that targets the .NET Framework in the Theme Designer.
- Reference the resulting assembly in .NET projects.
Theme projects contain XAML resources and no C# or VB code, and there are no conflicts between the .NET Framework and .NET.
Tip
Are you currently using .NET Framework and ready to transition to .NET 6+ 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)
FAQ
Can WPF .NET applications run on macOS and Linux?
No, WPF .NET applications cannot run on macOS and Linux. WPF .NET applications are designed to run on Windows because they rely on Windows-specific APIs. Specifically, .NET supports WPF only on Windows, with packages like Microsoft WPF or DevExpress WPF being restricted to the netX.0-windows target.
I want to maintain WinForms/WPF apps and create companion apps for non-Windows platforms (Web, Mobile, macOS/Linux). What features are available in the DevExpress ecosystem and how can I reuse my code?
DevExpress offers a variety of feature-rich visual UI controls and non-visual components/libraries for developing desktop, web, and mobile apps including APIs/services (based on modern versions of .NET and JavaScript).
UI Controls for Building Traditional Line-of-Business, CRUD, Office-Inspired Apps
If cross-platform compatibility is a requirement, you can choose a framework that supports multiple operating systems from the ground up. With DevExpress UI libraries, you can build web, hybrid, or cross-platform software with or without JavaScript, ASP.NET Core, or Blazor. You can also use tools like Electron or BlazorWebView/HybridWebView from .NET MAUI to pack your web applications inside a native container application. You can also build native mobile apps using .NET MAUI framework.
DevExpress UI libraries include:
- UI Controls for ASP.NET Core (MVC, Razor Pages)
- UI Controls for Blazor (Server, WebAssembly, Hybrid)
- UI Controls for JS / TS (Angular, React, Vue, jQuery)
- UI Components for .NET MAUI (Android, iOS)
- Business Intelligence Dashboard (ASP.NET Core, Blazor, Angular, React, and Vue)
- XAF (Cross-Platform .NET App UI for Blazor, WinForms & WPF)
Expand the following sections for information on popular scenarios and software requirements:
The DevExpress cross-platform Office File API allows you to create, load, edit, convert, sign, and print rich text documents, Excel spreadsheets/workbooks, and PDF files across all platforms and operating systems that support recent .NET versions:
- Windows, Linux, macOS
- Non-Windows environments (Azure, AWS, Docker, etc.)
You can integrate the DevExpress Office File API library in the following application types:
- Desktop (WPF, WinForms)
- Web (ASP.NET Core MVC, Razor Pages, Blazor Server/WebAssembly, Blazor Hybrid, Web API)
- Mobile (.NET MAUI)
- Console and API service applications
- Cross-platform .NET UI frameworks (for example, Avalonia)
Read the following help topics for additional information:
- Integrate Excel Spreadsheet API into Blazor Server App
- Integrate Word Document API into Blazor Server App
- Integrate Office File API into .NET MAUI App (macOS, iOS, Android)
- ASP.NET Core Backend Web/REST API for Office File API with Access Control Rights)
- Azure App Service Container (Linux) for Office File API App
- Amazon ECS (Linux Container) Using AWS Fargate for Office File API App
- Dockerize an Office File API Application
DevExpress Reports is our feature-complete reporting platform and component library for the .NET ecosystem that targets Web, Mobile, and Desktop platforms. You can incorporate a Report Viewer or End-User Report Designer directly within your application, generate PDF files from predefined templates, export reports to a variety of file formats. With DevExpress Reports, you can address requirements across multiple operating systems and hosting environments (Windows, Linux or macOS, Azure or AWS).
Read the following help topics for additional information:
- Reporting for ASP.NET Core
- Embedded JS Reports (Angular, React, Vue, jQuery)
- Reporting for Blazor
- Integrate DevExpress Blazor Report Viewer into .NET MAUI Blazor Hybrid App
- Integrate Reporting Tools into .NET MAUI Apps (macOS, iOS, Android)
- ASP.NET Core Backend Web/REST API for Reporting with Access Control Rights
- DevExpress Reporting for Avalonia
The amount of code you can reuse from existing applications depends on the architecture of your application. However, upgrading to modern versions of .NET and refactoring your code can greatly increase the likelihood of code reuse so that different UI clients can use the same business logic or API services.
You can share your existing database, data model, business logic, authentication/authorization settings, and cross-platform C# code between multiple UI clients (desktop, web, mobile) that target different platforms. API services are a natural choice or solution for security (UI clients cannot access database connection information or directly read/modify database tables), usability, and maintenance. For example, if your WPF application utilizes Entity Framework Core or XPO ORM, you can build a data service that can be used by your DevExpress WPF, Blazor, JavaScript, or mobile applications that target .NET.
Read the following help topics and blog posts for additional information:
Is there design-time support for WPF projects in JetBrains Rider and VS Code?
Design-time support for DevExpress-powered WPF projects is limited when using JetBrains Rider and Visual Studio Code. JetBrains Rider and VS Code do not have built-in design-time support for WPF projects. This means you won’t have access to the visual designer that you would typically use in Visual Studio.
How to convert/migrate a WPF application for .NET Framework to .NET?
Please read the following topic for guidance: Migrate WPF Applications to .NET.
How to deploy a WPF .NET application?
Please read the following topic for guidance: Deploy .NET Applications.