Namespace ReportWright.Blazor
Namespaces
Classes
- ExportedReport
An exported file.
- HttpReportViewerBackend
The WebAssembly backend: the definition comes from the server's definition endpoint, every dataset's rows from its dataset endpoint before the engine runs (the server evaluates each query from the stored definition with the values sent — a client never sends command text), and exports from its export endpoint. Fonts are the engine's bundled faces, which the server measures with too.
- LocalReportViewerBackend
The in-process backend for Blazor Server: the host hands it how to load a definition, the live data provider (the ASP.NET Core package's router, usually), the fonts and the exporter. No package dependency in either direction; the host wires one into the other.
- ParameterLayout
The
ReportParametersLayoutgrid a report states, read off the definition tree (Appendix A.10).
- ParameterLayoutCell
Where a parameter sits in the RDL 2016 parameter pane grid.
- ReportParameterBar
The parameter bar's code-behind.
- ReportViewerBackend
Where a viewer gets its definition, its rows, its fonts and its exports. The component runs the engine itself in every hosting mode; this is the only thing that differs between Blazor Server (in-process, LocalReportViewerBackend) and Blazor WebAssembly (over HTTP, HttpReportViewerBackend).
- ReportViewerStrings
Every string the viewer's chrome shows. A host localises by deriving and overriding; nothing is hard-coded in markup.