If your application uses DevExpress Reporting and targets .NET Core 3, you can run it on all supported platforms - WinForms, WPF, and ASP.NET Core.
ASP.NET Core 3 reports maintain feature parity with previous .NET Core versions and use the same Report Designer mechanism. A Visual Studio extension associated with XML report definition files launches the Report Designer and saves your edits to XML. Refer to the ASP.NET Core Reporting documentation section for more information.
Due to limitations in .NET Core 3.0, we are currently unable to integrate the Report Designer into Visual Studio's design time for WinForms or WPF projects. This topic explains how you can work around this limitation and create reports at design time. This method requires that you create an auxiliary .NET project that links reports available in your .NET Core 3.0 project.
Refer to the Limitations section in this topic for information on the report features that you should avoid when you use the suggested workaround to create reports in desktop applications.
Right-click the Dependencies node in the Solution Explorer and select Manage NuGet Packages in the invoked context menu.
Select DevExpress 19.2 Local in the Package source drop-down list and go to the Browse page. Find the DevExpress.WindowsDesktop.Win.Reporting/ DevExpress.WindowsDesktop.Wpf.Reporting package and install it.
The installed libraries are added to the project after the installation is completed.
Add an Auxiliary Desktop .NET Project
The .NET Core 3 project's infrastructure does not currently support design-time report creation. Add an auxiliary .NET Framework project to the solution and use the Report Designer to create new reports or edit existing reports.
In Visual Studio, add the Windows Forms App / WPF App (.NET Framework) or Class Library ( .Net Framework) project to your solution.
Add the Reporting libraries to the project, for example, add an empty report to the .NET project, and then remove the empty report.
Add the reports from you .NET Core 3 project to the auxiliary .NET project as links.
In the auxiliary project, double-click the report link's .cs file. This invokes the Report Designer where you can edit the report.
The following limitations apply when you design reports in an auxiliary .NET project for a .NET Core 3 project:
Synchronize connections between projects. All new connections are saved to the auxiliary .NET project's configuration file. Move this file to the .NET Core 3 project and use a link to it in the auxiliary .NET project.
Do not use the Object/EF/XPO Data Sources. Objects from .Net Core 3 projects can not be used in the auxiliary .NET project at design time.
Was this page helpful?
Thanks for your feedback! Any other suggestions? Tell us here.