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.