.NET Core 3.1 Support for ASP.NET Core, WinForms, and WPF Controls (v19.2.5)

News
18 December 2019

DevExpress components that are compatible with .NET Core 3.1 (LTS) are ready for download from both the Download Manager and NuGet. See our .NET Core Support webpage for additional information on supported products and download sources.

General Information

  • v19.2.5 of the DevExpress assemblies has been built under .NET Core 3.0 for the best user coverage. Another reason for doing so is because the .NET Core runtime updates are compatible within a major version, for instance, netcoreapp3.0. To stress this point, our online help system shows ".NET Core 3.0+" in the version checker:

    Note that the latest Visual Studio version replaces the .NET Core 3.0 runtime with .NET Core 3.1. Microsoft ends .NET Core 3.0 support on March 3, 2020.
  • You can now download PDB files for our .NET Core 3.0+ and .NET Standard 2.0+ libraries from the Download Manager. For more information, see How can I debug DevExpress .NET source code using PDB files.
  • In the future, we are aiming to provide a built-in way to specify either .NET Core, .NET Standard, or .NET Framework when you create or filter tickets in the Support Center. We're considering the addition of an optional "Framework" field to these ticket forms. In the meantime, feel free to provide the information about the assemblies you use in the ticket subject or body. Thanks!

WPF Controls

  • We have reorganized our WPF packages in online and local NuGet feeds so that you can reference only the required controls instead of adding a package that contains the entire WPF suite (see changes to .NET Core NuGet package structure).
  • Visual Studio's New Project dialog now features WPF project templates for .NET Core.

Where to get:
DevExpress .NET Core Desktop Libraries Installer v19.2.5
DevExpress NuGet feed

Useful links:
.NET Core Support | WPF Documentation
Creating a New .NET Core 3.0 Application
Migrate WPF Applications to .NET Core 3
WPF Controls - Prerequisites 

WinForms Controls

The entire WinForms product line supports .NET Core 3.1. As we noted earlier, we had to update our code to react to breaking changes in the official Microsoft release. Our components remain in the CTP (Community Technical Preview) stage, because the new WinForms designer for .NET Core apps itself is still in preview. It is only possible to work with UI controls in code or use a workaround with linked files. You are welcome to experiment with our WinForms components in our demos or in your own projects.

Where to get:
DevExpress .NET Core Desktop Libraries Installer v19.2.5 
DevExpress NuGet feed

Useful links:
.NET Core Support | WinForms Documentation
How to: Port a Windows Forms desktop app to .NET Core
WinForms - Single-File Applications With .NET Core 3
WinForms Controls - Prerequisites

ASP.NET Core MVC Controls

Where to get:
DevExpress .NET Products Installer v19.2.5
npm and NuGet packages

Useful links:
Get started with a Visual Studio project
Get started with a non-Visual Studio project

Blazor Controls

For a limited time, you can download and use our Blazor UI component suite free-of-charge.

Where to get:
Use DevExpress NuGet feed in your .NET projects to install Blazor component
Setup Visual Studio's NuGet Package Manager

Useful links:
Introduction to Blazor
Create a New Blazor Application

Dashboard, Reporting & Office File API 

  • ASP.NET Core, WinForms, and WPF Dashboards and Reporting tools support .NET Core 3.1 (the Visual Studio designer is missing due to changes in the design-time architecture for .NET Core).
  • ASP.NET Core Reporting Project Templates now give the ability to set the Target Framework to ASP.NET Core 3:

Where to get:
ASP.NET Core and cross-platform projects: DevExpress .NET Products Installer v19.2.5+
WinForms and WPF: DevExpress .NET Core Desktop Libraries Installer v19.2.5
All platforms: DevExpress NuGet feed 

Useful links:
Reporting in .NET Core 3 (CTP) | Documentation

App Framework (XAF)

Due to significant changes in the design-time architecture of .NET Core, XAF's WinForms UI for .NET Core 3.1 remains a CTP (Community Tech Preview). Our Model Editor, Module, Application, Controller and Action designers are not yet available within Visual Studio. 

  • XAFers can use Middle Tier Security client-related classes (WcfSecuredClient, MiddleTierServerObjectSpaceProvider and MiddleTierClientSecurity) in .NET Standard 2.0/.NET Core projects. The server app still requires .NET Framework 4.5 due to .NET Core platform limitations.
  • New List View Data Access Modes (ServerView and InstantFeedbackView) are available in WinForms .NET Core 3+ and .NET Framework apps using XPO for data access - all to achieve lower memory consumption and improved load, sort, group and filter performance. For more information, see this XPO blog post.

Where to get:
DevExpress .NET Core Desktop Libraries Installer v19.2.5
DevExpress NuGet feed

Useful links:
.NET Core 3.0 and .NET Standard 2.0 Support
Port an Existing XAF Application to .NET Core 3.0

ORM Library (XPO)

  • XPO Profiler now supports WinForms & WPF .NET Core 3+ apps. It can also profile ASP.NET Core apps regardless of whether System.Text.Json or Newtonsoft.Json are used for serialization.
  • XPO now supports Microsoft.Data.SqlClient v1.1.0 for .NET Standard that can be used in .NET Core apps. This feature is available in .NET Framework 4.5 apps as well.
  • We published an ASP.NET Core version of the XPO + OData V4 example on GitHub. The example currently uses .NET Core 2.2, but we will add a newer version once Microsoft supports .NET Core 3 for Microsoft.AspNetCore.OData. For more information, track this GitHub issue.

Where to get:
DevExpress .NET Core Desktop Libraries Installer v19.2.5
DevExpress.Xpo on NuGet
DevExpress NuGet feed

Useful links:
.NET Core 3.0 and .NET Standard 2.0 Support
Getting Started with .NET Core

Your Feedback Matters

We know you are busy this time of the year, but please let us know what you think about our .NET Core 3.1 support in general. What can we improve?

We would also value your thoughts about rebuilding the DevExpress source code for this new platform. How is this scenario important for you and why? 

Currently, we do not provide tools to rebuild the DevExpress source code for .NET Core 3.0+ and .NET Standard 2.0+ assemblies automatically. First, because of minimal interest from our customers (popular debugging scenarios are solved with PDB files or third-party decompilers). Second, recompiled assemblies alone do not make much sense in .NET Core apps without NuGet packages and it is difficult to create them automatically.

Showcase Your Apps on DevExpress.com

Highlight your business app and share your development experiences with the DevExpress community. To include your app in our upcoming App Showcase, please forward an application screenshot to clientservices@devexpress.com and tell us which DevExpress products you currently use within your organization.
5 comment(s)
Bassam Abdelaal
Bassam Abdelaal

Hello,

just to be sure , we are using .Net Framework 4.6 , will upgrading from 19.1.6 to 19.2.5 work smoothly or this addition of .Net Core support will cause problems to us in XAF and Winforms apps ?


Kindly advice

Thanks


19 December 2019
Chris Dickerson
Chris Dickerson
Assemblies have been built under .NET Core 3.0? Way to be ahead of the game.
19 December 2019
Ngabo Adrian
Ngabo Adrian

I've a Fluent Form with An Accordion Control containing several Navigation pages. This Fluent Form is Name "MainForm". I've designed a Customers Interface with several controls on an XtraUserControl which I later add to the Navigation Page on the MainForm as per the code below. It was working fine in earlier versions but it seems it doen't work in the current versions anymore!!! What could be the problem in these new versions including version 19.2.3?

Dim CustomerInterface As New CustomerXtraUserControl() With {.Dock = DockStyle.Fill}
MainForm.NavigationPage30.Controls.Add(CustomerInterface)
MainForm.NavigationFrame1.SelectedPage = MainForm.NavigationPage30
19 December 2019
Dmitry (DevExpress)
Dmitry (DevExpress)
@Bassam Abdelaal
No, .NET Core support won't affect your .NET Framework apps.

A library cannot target both frameworks simultaneously, and for that reason, we ship libraries built under different frameworks as parts of different installers ("DevExpress Component Installer" for .NET Framework libraries, and "Desktop Product Installer" for .NET Core libraries). If you plan to upgrade from v19.1 to v19.2 and keep .NET Framework 4.6 as the target framework, download "DevExpress Component Installer" and it will simply replace older libraries built under .NET Framework with newer libraries build under the same framework.

However, even though .NET Core libraries will have no impact whatsoever on your application, any major DevExpress components update may have breaking changes when compared to older versions. To be aware of all potential issues and ways to resolve them, check the Version History page prior to upgrading.

@Ngabo Adrian
Unfortunately, the information you provided is not enough to identify what causes the issue. Would you please create a new ticket in our Support Center and describe your scenario in greater detail? Our support engineers will be happy to help you.
19 December 2019
MiguelLarios
MiguelLarios
In a DevExtreme Razor Page Aplication i cant create a report in design time?
20 November 2020

Please login or register to post comments.