Report designer and viewer for .NET

SSRS reports in your app, no report server

Open the RDL files you already have, show them in a Blazor viewer, let people edit them in a Blazor designer, and export them to PDF, Excel, Word and more from ASP.NET Core or a batch job. The engine is DocWright.Reporting; ReportWright is the designer, the viewer, the data providers and the host.

Get started Guides API reference

2008–2016RDL read, edited and saved in its own version

2Blazor render modes, Server and WebAssembly

0report servers, Office installs or native dependencies

Reports.razor

@page "/reports/{*Path}"
@using ReportWright.Blazor.Viewer

<ReportViewer Path="@Path" />

@code {
    [Parameter] public string? Path { get; set; }
}

Viewer

Paging, zoom, parameters with the 2016 layout grid, toggles, interactive sort, drillthrough, bookmarks, document map, search, print and every export. One component for Blazor Server and WebAssembly; a REST API for everything else.

Designer

A design surface with rulers, snap and smart guides; tables, matrices and lists with groups and totals; charts, sparklines, data bars, gauges, indicators and barcodes; a property grid and an expression editor. Every edit is undoable and the file keeps what the designer does not understand.

Data

CSV, JSON, REST, XML, SQL Server and your own objects, resolved by the host. A connection string never reaches a client; a report's query runs only through a provider you registered.

Host

MapReportWright("/reporting") adds the API: stores, parameters, runs, sessions, toggles, search, export. Permissions per request; endpoints fuzzed with malformed input.