devexpress-reporting-aspnetcore

Integrates DevExpress Document Viewer and Report Designer into ASP.NET Core MVC and Razor Pages applications.

Updated Dec 11, 2025
One-click install
npx skills add https://github.com/AleksaRistic216/dotnet-playground --skill devexpress-reporting-aspnetcore-aleksaristic216
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: devexpress-reporting-aspnetcore
Source: https://github.com/AleksaRistic216/dotnet-playground/tree/main/.github/skills/reporting/devexpress-reporting-aspnetcore
Command: npx skills add https://github.com/AleksaRistic216/dotnet-playground --skill devexpress-reporting-aspnetcore-aleksaristic216

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Integrating DevExpress reporting components into ASP.NET Core involves a strict multi-step setup (NuGet packages, npm bundling, Program.cs middleware order, controllers, Razor views) where any misconfiguration causes silent failures, blank viewers, or cryptic HTTP errors. This Skill guides the full integration and provides a symptom-to-fix troubleshooting reference. ## Core Features & Use Cases - Viewer & Designer Integration: Step-by-step setup for the Web Document Viewer and End-User Report Designer in both MVC and Razor Pages projects, including bundleconfig.json, libman.json, and Program.cs configuration. - Report Storage & Customization: Implement ReportStorageWebExtension or IReportProvider for name-based report loading, and customize toolbars, tab panels, export options, and parameter editors via client-side events. - Security & Troubleshooting: Configure authorization, CSRF exemptions, CSP nonces, and diagnose common failures like blank viewers, 400/404/500 errors, and script load-order issues. - Use Case: A developer needs to add an end-user report designer to an existing ASP.NET Core MVC app on Linux. The Skill walks them through package installation, Skia setup, storage implementation, and verifies the result in the browser. ## Quick Start Ask the assistant to add a DevExpress Document Viewer to your ASP.NET Core MVC project and have it generate the Program.cs, controllers, bundleconfig.json, and view code for you.

Frequently Asked Questions about devexpress-reporting-aspnetcore

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I add a DevExpress Document Viewer to an ASP.NET Core MVC app?

Install DevExpress.AspNetCore.Reporting, run npm install with the reporting packages, add bundleconfig.json and libman.json, then register AddDevExpressControls and ConfigureReportingServices in Program.cs. Add a WebDocumentViewerController and call Html.DevExpress().WebDocumentViewer in your view.

How do I enable save and load in the DevExpress End-User Report Designer?

Implement a ReportStorageWebExtension subclass with GetData, SetData, SetNewData, GetUrls, IsValidUrl, and CanSetData methods. Register it with AddScoped after AddDevExpressControls in Program.cs, then bind reports by name string.

Why is my DevExpress report viewer blank with no errors?

A blank viewer usually means app.UseDevExpressControls() is missing or placed after app.UseStaticFiles() in Program.cs. Move it before UseStaticFiles and verify thirdparty.bundle.js loads in the layout head, not in a Scripts section.

Does DevExpress ASP.NET Core reporting work on Linux or macOS?

Yes, but you must install the DevExpress.Drawing.Skia NuGet package for non-Windows hosting, including Docker and Azure App Service on Linux. Without it you get a DllNotFoundException for Skia at runtime.

Why do I get HTTP 400 errors on DXXRDV reporting endpoints?

HTTP 400 on reporting endpoints is caused by anti-forgery token validation rejecting the requests. Add the [IgnoreAntiforgeryToken] attribute to your viewer, designer, and query builder controllers.

What causes 'Component dx-filtereditor-plain is already registered' in the report designer?

This error occurs when both viewer.part.bundle.js and designer.part.bundle.js load on the same MVC designer page. The designer bundle is self-contained and already includes the viewer scripts, so remove the viewer bundle from that page.