Skip to main content
All docs

Add an End-User Report Designer to a DevExtreme ASP.NET Core Application

  • 6 minutes to read

This tutorial describes how to add the Report Designer control to a DevExtreme ASP.NET Core Application.



In .NET 6, the System.Drawing.Common library is compatible with Windows only. An exception is thrown on other platforms. See the following topic for more information: Reporting .NET/.NET Core Limitations.

Create a DevExtreme ASP.NET Core Application

Create a new DevExtreme ASP.NET Core Application from a template as described in the following help topic: Configure a Visual Studio Project for the DevExtreme Application:

Create New DevExtreme Project

Configure New DevExtreme Project

Select Project Settings

Install NuGet Packages

Follow the steps below to install NuGet packages:

  1. Right-click Dependencies in the Solution Explorer and select Manage NuGet Packages from the context menu.


  2. Install the following packages:

    For more information on how to install NuGet packages for DevExpress components, review the following help topic: Install DevExpress Controls Using NuGet Packages.

Configure npm

  1. Install Node.js (LTS version) from the Node.js website if you do not have Node.js installed.

  2. Right-click the project in the Solution Explorer and select Add | New Item from the context menu. Select npm Configuration File in the invoked Add New Item dialog.

    Add npm Configuration File to the Project

    Open the newly created package.json file, replace its content with the following code, and save the file:

    "version": "1.0.0",
    "name": "",
    "private": true,
    "dependencies": {
        "@devexpress/analytics-core": "23.1-stable",
        "bootstrap": "^4.3.1",
        "devexpress-reporting": "23.1-stable",
        "devextreme": "23.1-stable"
  3. Right-click package.json in the Solution Explorer and select Restore Packages. Alternatively, you can execute the following command in the folder that contains the package.json file:

    npm install

Manage Libraries

You must register JS and CSS resources once and in the correct order. Otherwise, client-side errors may occur, as described in the following help topic: Reporting Application Diagnostics.

To create resource bundles, modify the bundleconfig.json file as follows:

    "outputFileName": "wwwroot/css/vendor.css",
    "inputFiles": [
      // Adds the UTF-8 charset to display icons correctly  


      // Predefined themes:
    "minify": {
      "enabled": false
    "outputFileName": "wwwroot/js/vendor.js",
    "inputFiles": [
    "minify": {
      "enabled": false
    "outputFileName": "wwwroot/css/reporting.designer.part.bundle.css",
    "inputFiles": [
    "minify": {
      "enabled": false,
      "adjustRelativePaths": false
    "outputFileName": "wwwroot/js/reporting.designer.part.bundle.js",
    "inputFiles": [
    "minify": {
      "enabled": false
    "sourceMap": false

Note that third-party bundles are merged into vendor bundles. Libraries specific to the Report Designer are included in the related bundles.

Configure Application and Services

  1. Open the Program.cs_ file and modify the code as shown in the following code snippet:

    using DevExpress.AspNetCore;
    using DevExpress.AspNetCore.Reporting;
    var builder = WebApplication.CreateBuilder(args);
    var app = builder.Build();
  2. Implement controllers to process the Report Designer requests. In the Controllers folder, create the ReportingControllers.cs file with the following content:

    using DevExpress.AspNetCore.Reporting.QueryBuilder;
    using DevExpress.AspNetCore.Reporting.QueryBuilder.Native.Services;
    using DevExpress.AspNetCore.Reporting.ReportDesigner;
    using DevExpress.AspNetCore.Reporting.ReportDesigner.Native.Services;
    using DevExpress.AspNetCore.Reporting.WebDocumentViewer;
    using DevExpress.AspNetCore.Reporting.WebDocumentViewer.Native.Services;
    public class CustomWebDocumentViewerController : WebDocumentViewerController {
        public CustomWebDocumentViewerController(IWebDocumentViewerMvcControllerService controllerService)
            : base(controllerService) {    }
    public class CustomReportDesignerController : ReportDesignerController {
        public CustomReportDesignerController(IReportDesignerMvcControllerService controllerService)
            : base(controllerService) { }
    public class CustomQueryBuilderController : QueryBuilderController {
        public CustomQueryBuilderController(IQueryBuilderMvcControllerService controllerService)
            : base(controllerService) {    }

An application with End-User Report Designer requires all three controllers for proper operation.

Add a Sample Report

  1. Right-click the project in the Solution Explorer and select Add | New Folder from the context menu. Rename the newly created folder to Data.

  2. Right-click the project in the Solution Explorer and select Add | Existing Item from the context menu. Open the following path and copy the nwind.xml file to the project’s Data folder: C:\Users\Public\Documents\DevExpress Demos 23.1\Components\Data\nwind.xml

  3. Right-click the project in the Solution Explorer and select Add | New Folder from the context menu. Rename the newly created folder to Reports.

  4. Right-click the Reports folder and select Add | New Item from the context menu. In the invoked Add New Item dialog, click the Reporting tree node and select DevExpress v23.1 Report.

    Add New Report

    Rename the new report to TestReport and click Add.

  5. In the invoked Report Wizard, select the Table report type:

    Select Table Report

    Click Next.

  6. Select the Database data source type:

    Select Database Source Type

    Click Next.

  7. Do not use an existing data connection:

    Do not Use an Existing Data Connection

    Click Next.

  8. Select XML file as the data provider:

    Select XML Data Provider

    Specify the nwind.xml file in the Data folder. Click Next.

  9. Save the connection string:

    Save Connection String

    Click Next.

  10. Select the Categories table:

    Select Categories Table

    Click Next.

  11. Select data fields:

    Select Data Fields

    Click Finish.

Add the End-User Report Designer Component

  1. Add the DevExpress.AspNetCore namespace directive to the _ViewImports.cshtml file. As an alternative, you can add this namespace to the view that contains the Report Designer control.

    @using DevExpress.AspNetCore
  2. Add a new page (Designer.cshtml) with the following code, which displays the Report Designer and loads the TestReport:


    If you implement a custom report that inherits from XtraReport and want to open it in the End-User Report Designer, add a constructor without parameters to this report.

    <link rel="stylesheet" href="~/css/reporting.designer.part.bundle.css" />
    <script src="~/js/reporting.designer.part.bundle.js"></script>
            .Bind(new Reports.TestReport()))

    The page includes script and style bundles related to the Report Designer. The bundles are defined in the bundleconfig.json file.

  3. Open the Layout.cshtml file (Views|Shared folder) and add a link to the Designer.cshtml page:

        <div id="navbar" class="collapse navbar-collapse">
            <ul class="navbar-nav mr-auto">
                <li class="active nav-item"><a href="#" class="nav-link">Home</a></li>
                <li class="nav-item"><a href="#about" class="nav-link">About</a></li>
                <li class="nav-item"><a href="#contact" class="nav-link">Contact</a></li>
                <li class="nav-item"><a href="/Designer" class="nav-link">Report Designer</a></li>

Run the Application

When you run the application, the page contains the End-User Report Designer with the TestReport. You can design a report, preview it, print and export, but you cannot save it or load another report.

To enable users to save and load reports, create and register a report storage. See the following topic for instructions: Add a Report Storage (ASP.NET Core).


If the page does not display the Report Designer component, or it is displayed incorrectly, check the following:

  • The script files should be registered in the correct order, as demonstrated in the bundleconfig.json code above. For more information, review the following help topic: Script Registration Order.
  • There should be no duplicate registrations. Report Designer component bundles should be included in the pages that contain the component.
  • The version of the DevExpress scripts (npm packages) should match the version of the server-side libraries (NuGet packages). You can enable Development Mode to check for library version mismatch on every request to the server. For more information, review the following help topic: Server-Side Libraries Version.

Review the following help topic for more information: Troubleshooting.


Review the following help topic for details: Reporting .NET/.NET Core Limitations.

See Also