Skip to main content
BuyLog In
.NET Reporting Tools
Search in…
Docs > .NET Support > .NET Reporting Limitations
All docs
V25.2
    • DevExpress Reports
    Product Information
    What's New
    .NET Support
    CLI Project Templates
    Template Kit
    Linux and macOS Support
    .NET Reporting Limitations
    Migration Guides
    Getting Started
    Create Reports in Designer
    Feature Guide
    AI-powered Extensions
    Report Designer for Visual Studio
    Report Designer for VS Code
    Report Designer for JetBrains Rider
    Reporting for Desktop
    Reporting for .NET MAUI
    Reporting for Web
    Localize Reporting Applications
    Security Considerations
    Memory Usage in Reporting - Best Practices
    Cloud Integration
    .NET Aspire Integration
    Cross-Platform .NET App UI
    Backend Web API Service / REST API for Reporting
    WCF Report Service
    End-User Documentation
    API Reference
    ASP.NET Core API Reference
    Blazor API Reference
    Client API Reference
    Client API Reference (Web Forms & MVC)
    Download CHM

    Reporting - .NET Limitations

    • 3 minutes to read

    This help topic lists known limitations of DevExpress Reports in .NET applications.

    Platform-Specific Limitations

    General

    Linux

    • Export to WMF image format is not supported.

    macOS

    • Exported PDF files cannot embed fonts.

    Design-Time Limitations

    When you use the Visual Studio Report Designer in .NET projects, it runs out of process. This behavior differs from the in-process designer used in .NET Framework applications and introduces several design-time limitations:

    Global Project Resources

    In .NET projects, the Visual Studio Report Designer cannot reliably access global project resources defined in Properties.Resources.

    Issues:

    • Exceptions occur when a report references images or other resources from Properties.Resources.
    • The Image Picker dialog is not available for resource-based images.
    • Resource images may not appear in the designer.

    Solutions:

    • Use file-based images instead of project resources.
    • Assign images in code at runtime.
    • Store images in a location accessible to the designer process.

    ObjectDataSource and Project-Relative Files

    In .NET projects, the Visual Studio Report Designer executes from a temporary folder. As a result, it does not have direct access to files located in the original project directory.

    Issues:

    • ObjectDataSource fails to load content files located in the project directory if you reference them in code.
    • Relative paths such as Data\sample.json do not resolve correctly at design time.

    Solutions:

    • Use absolute paths for design-time testing.
    • Embed data into the assembly.
    • Supply design-time data in code.
    • Ensure required files are copied to the output directory and accessed using a resolved base path.

    XRPictureBox.ImageSource Behavior Differences

    The behavior of the XRPictureBox.ImageSource property differs between designers.

    .NET Framework Report Designer:

    • Displays an Image Picker dialog.

    • Allows users to select images from project resources.

    .NET Report Designer:

    • Opens a standard file dialog.

    • Does not have access to project resources.

    • Does not display resource-based images in the Image Picker.

    Recommendation:

    • Select file-based images for design-time configuration in .NET projects.

    • Assign resource images programmatically at runtime if required.

    Troubleshooting

    Referenced Assemblies Are Not Discovered (XRSubreport)

    In .NET projects, referenced assemblies are not included in type discovery for the XRSubreport control.

    Solution
    Move your reports to the main project, or specify the ReportSourceUrl property in code.

    .xsd Files Not Available In Report Designer’s Toolbox

    In .NET projects, typed DataSet components generated from .xsd files are not displayed in the Report Designer’s Toolbox.

    Need Help?

    If you encounter any other limitations or issues related to the transition to .NET that are not listed in this help topic, please submit a ticket in our Support Center.