devexpress-reports-blazor
starsforks
How to install devexpress-reports-blazor?
devexpress/agent-skills/devexpress-reports-blazor
$npx -y skills add DevExpress/agent-skills --skill devexpress-reports-blazorIntegrate DevExpress Report Viewer and Report Designer into Blazor Server, Blazor WebAssembly, and Blazor Web App. Register AddDevExpressServerSideBlazorReportViewer, AddDevExpressBlazorReporting in Program.cs. Configure DxResourceManager.RegisterScripts in App.razor. Components:
SKILL.md
| 1 | # DevExpress Blazor Reporting — Viewer & Designer Integration |
| 2 | |
| 3 | Integrates DevExpress report viewing and designing into Blazor applications. Five components across three families cover every Blazor hosting model. |
| 4 | |
| 5 | This skill covers **Blazor UI component integration only**. For creating reports programmatically (bands, controls, data binding, export), use the `devexpress-reports-core` skill. |
| 6 | |
| 7 | > **Skill boundary — hard stop**: This skill does NOT generate `XtraReport` subclasses, band declarations (`DetailBand`, `GroupHeaderBand`), or control code (`XRLabel`, `XRTable`, etc.). If a report class is needed, switch to `devexpress-reports-core` for that part, get the class name or instance, then return here to wire it into the viewer. |
| 8 | |
| 9 | --- |
| 10 | |
| 11 | ## Agent Workflow — Three Required Phases |
| 12 | |
| 13 | **Do not write any code until all three phases are complete.** This ensures you load the correct reference files and generate a single coherent step-by-step plan. |
| 14 | |
| 15 | - **Phase 1** — Search the project and ask clarifying questions for any unknowns |
| 16 | - **Phase 2** — Apply the decision gates to select the exact component and architecture |
| 17 | - **Phase 3** — Load the matching reference files, merge their steps, present the plan, then execute |
| 18 | |
| 19 | --- |
| 20 | |
| 21 | ## Phase 1 — Preflight: Gather Context |
| 22 | |
| 23 | ### Step 1 — Automated Discovery (Do Before Asking Anything) |
| 24 | |
| 25 | Run these searches in the project before asking the developer: |
| 26 | |
| 27 | 1. **Installed packages**: `dotnet list package` → look for `DevExpress.Blazor.Reporting.*` and their versions |
| 28 | 2. **Blazor configuration classification** — follow this 4-step algorithm and record the result before selecting any component: |
| 29 | |
| 30 | **Step A — Solution structure**: Find all `.csproj` files. Is there a `.Client` project (name suffix or a `<ProjectReference>` from a server project pointing to a client project)? |
| 31 | |
| 32 | **Step B — Server `Program.cs`** (look for `AddRazorComponents` call chain): |
| 33 | |
| 34 | | What is found | Preliminary result | |
| 35 | |---|---| |
| 36 | | `AddRazorComponents()` with no `AddInteractiveServerComponents()` or `AddInteractiveWebAssemblyComponents()` | → **Static** | |
| 37 | | `AddInteractiveServerComponents()` only | → **Interactive Server** | |
| 38 | | `AddInteractiveWebAssemblyComponents()` only | → **Interactive WebAssembly (Client + Server)** | |
| 39 | | Both `AddInteractiveServerComponents()` + `AddInteractiveWebAssemblyComponents()` | → Auto candidate; confirm in Step D | |
| 40 | |
| 41 | **Step C — Client `Program.cs`**: presence of `WebAssemblyHostBuilder.CreateDefault(args)` confirms a WASM client project. If this file exists without a server `Program.cs` that calls `MapRazorComponents` → **Interactive WebAssembly Standalone**. |
| 42 | |
| 43 | **Step D — `@rendermode` in `.razor` files** (search `App.razor`, `Routes.razor`, all `@page` components): |
| 44 | |
| 45 | | Directive / parameter | Indicates | |
| 46 | |---|---| |
| 47 | | `@rendermode InteractiveServer` | Interactive Server | |
| 48 | | `@rendermode InteractiveWebAssembly` | Interactive WebAssembly | |
| 49 | | `@rendermode InteractiveAuto` or `new InteractiveAutoRenderMode(...)` | **Interactive Auto** | |
| 50 | | No directives and no `AddInteractive*` in `Program.cs` | Static | |
| 51 | |
| 52 | > **Key rule**: Both `AddInteractiveServerComponents()` + `AddInteractiveWebAssemblyComponents()` in `Program.cs` does **not** alone mean Auto mode. Final classification uses the `@rendermode` directives actually present in components. |
| 53 | |
| 54 | **Final result** — record one of: **Static** | **Interactive Server** | **Interactive WebAssembly Standalone** | **Interactive WebAssembly (Client + Server)** | **Interactive Auto**. If ambiguous, ask the user for the Visual Studio template name or the `dotnet new` command used to create the project. |
| 55 | |
| 56 | 3. **Existing viewer/designer components**: search all `.razor` files for `<DxReportViewer`, `<DxDocumentViewer`, `<DxReportDesigner`, `<DxWasmDocumentViewer`, `<DxWasmReportDesigner` — note component names and file locations |
| 57 | 4. **Report |
People who liked this also viewed
6 picksType
- grill-with-docsA relentless interview to sharpen a plan or design, which also creates docs (ADR's and glossary) as we go.SkillsJul 2026
- lark-minutes飞书妙记：搜索妙记、查看妙记基础信息、下载/上传音视频、读取或编辑妙记的产物内容、改标题、替换说话人/关键词、申请妙记查看/编辑权限。当给出minute_token、本地音视频文件，要查/改/转妙记产物，或用户明确要主动申请妙记权限时使用；本地音视频转纪要/逐字稿优先走本 skill，不要用 ffmpeg/whisper 本地转写。不负责：获取会议关联妙记，或仅按自然语言标题定位纪要SkillsJul 2026
- lark-markdown飞书 Markdown：查看、创建、上传、编辑和比较 Markdown 文件。当用户需要创建或编辑 Markdown 文件、读取、修改、局部 patch 或比较差异时使用。不负责将 Markdown 导入为飞书在线文档，也不负责文件搜索、权限、评论、移动、删除等云空间管理操作。SkillsJul 2026
- docxUse this skill whenever the user wants to create, read, edit, or manipulate Word documents (.docx files) or Word templates (.dotx files). Triggers include: any mention of 'Word doc', 'word document', SkillsJul 2026
- edit-articleSkills for Real Engineers. Straight from my .agents directory.SkillsJul 2026
- lark-note飞书会议纪要（Note）直查：已知 note_id 时查询纪要详情、展示类型、关联文档 token，并读取 unified 原始逐字记录。当用户已持有 note_id，或从文档显式 vc-node-id 获得 note_id 时使用。不负责会议/日程/妙记定位、文档标题搜索或 Docx 正文读取。SkillsJul 2026
