devexpress-reports-aspnetcore

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

39|7|Updated Jun 2, 2026
One-click install
npx skills add https://github.com/DevExpress/agent-skills --skill devexpress-reports-aspnetcore
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: devexpress-reports-aspnetcore
Source: https://github.com/DevExpress/agent-skills/tree/main/plugins/dx-reporting/skills/devexpress-reports-aspnetcore
Command: npx skills add https://github.com/DevExpress/agent-skills --skill devexpress-reports-aspnetcore

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill eliminates the complex, error-prone manual process of integrating DevExpress Web Document Viewer and End-User Report Designer into ASP.NET Core MVC and Razor Pages applications, handling correct NuGet/npm package version alignment, service and middleware registration, client-side asset bundling, cross-platform deployment configuration, and resolution of common runtime errors like blank viewers, HTTP 400/404/500 responses, and script loading failures that occur from incorrect setup order.

Core Features & Use Cases

  • Dual Component Support: Integrates both read-only Web Document Viewer for report preview and full End-User Report Designer for no-code report customization by non-technical users.
  • Multi-Framework & Cross-Platform Compatibility: Includes setup guides for both ASP.NET Core MVC and Razor Pages, with support for Linux and macOS deployment via the DevExpress.Drawing.Skia renderer.
  • Comprehensive Guardrails & Troubleshooting: Provides mandatory setup step ordering, version consistency checks, security configuration guidance (authorization, CSRF, CSP), and a detailed symptom-to-fix table for common integration errors.
  • Use Case: A developer building an internal business dashboard can use this Skill to add a report viewer for sales summaries and an end-user report designer, allowing team members to modify report layouts and parameters without requiring developer involvement for every change.

Quick Start

Use this Skill to integrate a DevExpress End-User Report Designer into your existing ASP.NET Core MVC application, configure all required NuGet and npm packages, set up the necessary reporting controllers and client-side asset bundles, and implement report storage to enable user-driven save and load operations for custom reports.

Frequently Asked Questions about devexpress-reports-aspnetcore

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

FAQPage Schema
How do I integrate the DevExpress Report Viewer into an ASP.NET Core MVC application?▼

To integrate the DevExpress Report Viewer into ASP.NET Core MVC, register the required reporting services and middleware, align NuGet and npm package versions, and configure client-side asset bundles to render reports without blank screens or script loading failures.

Can I deploy DevExpress reporting applications on Linux or macOS?▼

Yes, DevExpress reporting supports Linux and macOS cross-platform deployment by configuring the DevExpress.Drawing.Skia renderer, enabling web farm document storage and ensuring correct service pipeline registration for non-Windows environments.

What's the best way to add an End-User Report Designer to Razor Pages?▼

Adding an End-User Report Designer to Razor Pages requires setting up reporting controllers, configuring NuGet and npm packages, implementing report storage, and bundling client-side assets to allow non-technical users to customize report layouts without code.

Why does my DevExpress Web Document Viewer display a blank screen or return HTTP 500 errors?▼

A blank Web Document Viewer or HTTP 500 response usually stems from incorrect setup ordering, mismatched NuGet and npm package versions, or missing client-side asset bundles, requiring strict adherence to mandatory setup steps and version consistency checks.

Do I need to configure security and authorization for reporting endpoints in ASP.NET Core?▼

Yes, configuring security for reporting endpoints in ASP.NET Core requires setting up authorization rules, CSRF tokens, and Content Security Policy (CSP) headers to protect both the Web Document Viewer and End-User Report Designer from unauthorized access.

How do I implement report storage for saving and loading custom reports in ASP.NET Core?▼

Implementing report storage in ASP.NET Core requires creating a custom storage provider that handles report serialization and deserialization, enabling users to save modified layouts from the End-User Report Designer and load them dynamically during preview sessions.