wpf-401165-dotnet-core-support.md
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) | .NET 10 |
|---|---|---|---|---|---|---|---|---|
| v25.2 (current) | ||||||||
| v24.2 - v25.1 | ||||||||
| v23.2-v24.1 | * | |||||||
| v22.2-v23.1 | ||||||||
| v21.2-v22.1 | ||||||||
| v20.1-v21.1 | ||||||||
| v19.2.5+ | ||||||||
| v19.1-v19.2.4 |
* DevExpress source code targets .NET 9.0 starting with version 24.1.8.
Prerequisites to build .NET Core applications:
The Getting Started topic explains how to start using DevExpress WPF UI controls in a .NET WPF application.
The following topic describes how to migrate an existing WPF Application to .NET: Migrate WPF Applications to .NET.
The following topic describes how to deploy your .NET WPF application: Deploy .NET Applications.
The ApplicationJumpListService is not supported.
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:
You cannot run original WPF .NET applications on macOS and Linux. WPF .NET applications are designed to run on Windows because they rely on Windows-specific APIs. Specifically, .NET only supports WPF on Windows, with packages like Microsoft WPF or DevExpress WPF restricted to the netX.0-windows target.
Note
Avalonia XPF allows WPF projects to run on macOS and Linux. The Avalonia team added support for DevExpress controls. Refer to the following GitHub example for more information: DevExpress Avalonia XPF Demo.
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:
Expand the following sections for information on popular scenarios and software requirements:
Generate and Manage Office Files (Word, Excel, PDF)
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:
You can integrate the DevExpress Office File API library in the following application types:
Read the following help topics for additional information:
Design Reports, Export Documents, and Download PDF
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:
Code Sharing, Data Access Security, and Reusable API Services
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:
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.
Please read the following topic for guidance: Migrate WPF Applications to .NET.
Please read the following topic for guidance: Deploy .NET Applications.