Skip to main content
BuyLog In
.NET Reporting Tools
Search in…
Docs > Reporting .NET Migration Guides > Migrate DevExpress Reports to .NET Applications
All docs
V24.2
Reporting
Product Information
What's New
.NET Support
Get Started with DevExpress Reporting
Create Different Report Types (Walkthroughs)
Detailed Guide to DevExpress Reporting
Memory Usage in Reporting - Best Practices
Localize Reporting Applications
Security Considerations
AI-powered Extensions
Visual Studio Report Designer
VS Code Report Designer
Reporting for Desktop
Reporting for .NET MAUI
Reporting for Web
Reporting .NET Migration Guides
Migrate DevExpress Reporting Web Apps to .NET
Migrate DevExpress Reporting WinForms/WPF .NET Framework Apps to .NET
Migrate DevExpress Reports to .NET Applications
Cloud Integration
.NET Aspire Integration
Cross-Platform .NET App UI
Backend Web API Service / REST API for Reporting
WCF Report Service
End-User Documentation
Redistribution and Deployment
API Reference
ASP.NET Core API Reference
Blazor API Reference
Client API Reference
Client API Reference (Web Forms & MVC)
Download CHM

Migrate DevExpress Reports to .NET Applications

  • 2 minutes to read

The following help topic explains how to migrate reports created in .NET Framework applications to .NET Projects. You can reuse both a report definition stored as a .REPX extension and a report created in Visual Studio ( a .cs extension) in a report project on any available platform.

Note

You do not need to update report definitions each time you upgrade DevExpress Reporting. New versions of DevExpress Reporting Components will process existing reports correctly. However, a report created with a newer DevExpress version may not be rendered correctly in applications that use older versions of DevExpress Reporting Components.

Reports Designed in Visual Studio (.cs)

  1. Upgrade your existing .NET Framework application to the latest version of DevExpress components. Use the Project Converter tool for this purpose. Refer to the following help topic for additional information: Upgrade Your Application to a New DevExpress Version.

  2. Add required dependences to the .NET Project. You can do it in one of the following ways:

    • Add an empty report to your new .NET application. This action adds required dependencies automatically.

    • Add DevExpress Reporting NuGet packages or assemblies manually. Refer to the application deployment help topic for more information about required packages: Redistribution and Deployment.

  3. Copy source code files of your reports (.cs, .designer.cs, .resx) directly into your new application. You may also need to move dependent classes and components from the existing project to the new one. Adjust the copied report code to fix compilation issues or resolve breaking changes.

You can now use migrated reports in your new .NET application. The following help topic outlines minor limitations compared to .NET Framework projects: Limitations of .NET Core Apps.

You may require additional packages to run our Reporting components on Linux or iOS: Use Reporting on Linux.

Reports Stored in REPX format

.NET applications only support reports saved to REPX format by using XML serialization. If you generate REPX reports with the latest version of DevExpress components or with the XtraReport.SaveLayoutToXml method overloads, no further actions are required to use such reports in .NET applications.

However, if you were using REPX files created with legacy CodeDOM Serialization format or with the XtraReport.SaveLayout method overloads, convert these report to XML format before migration. For this conversion, use any application that targets .NET Framework. Load such reports in code (Load a Report in Code) and then save them in XML format as instructed in Save Reports in Code.