Pysar.Blazor
0.1.31
See the version list below for details.
dotnet add package Pysar.Blazor --version 0.1.31
NuGet\Install-Package Pysar.Blazor -Version 0.1.31
<PackageReference Include="Pysar.Blazor" Version="0.1.31" />
<PackageVersion Include="Pysar.Blazor" Version="0.1.31" />
<PackageReference Include="Pysar.Blazor" />
paket add Pysar.Blazor --version 0.1.31
#r "nuget: Pysar.Blazor, 0.1.31"
#:package Pysar.Blazor@0.1.31
#addin nuget:?package=Pysar.Blazor&version=0.1.31
#tool nuget:?package=Pysar.Blazor&version=0.1.31
Pysar.Blazor
Blazor WebAssembly integration for Pysar, a cross-platform
report engine for .NET: the <ReportView> component, printing through the browser, and a
WasmPlatformHandler for file and font access.
Setup
Registration is a service-collection call, and the same renderer serves both the viewer and the exporters — so a custom drawer registered here reaches the screen as well as the PDF:
builder.Services.AddPysar(renderer => renderer.WithDrawer<QRCode>(new QRCodeDrawer()));
The browser has no file system, so assets are fetched up front and held in memory. This is not a preference: fonts are loaded synchronously, and a blocking read on the browser's single thread is a deadlock rather than a stall.
var files = await PreloadedFileSystem.FetchAsync(http, [
"Fonts/Ubuntu-Regular.ttf",
"Images/logo.svg"
]);
WasmPlatformHandler.Install(files);
Showing a report
<ReportView Report="@_report" ZoomMode="@ReportZoomMode.FitWidth" PageSpacing="24" />
The view renders a built report as scrollable, zoomable pages, rasterised one visible tile at a time, so memory follows the size of the viewport rather than the zoom level.
Printing
IReportPrinter resolves to BlazorReportPrinter, which renders the report to PDF off the UI thread
and hands it to the browser's own print dialog. It is registered scoped, because it holds a JS module
reference belonging to one browser context. The report must already have Build() called.
Documentation
License
MIT — see LICENSE.
| Product | Versions Compatible and additional computed target framework versions. |
|---|---|
| .NET | net10.0 is compatible. net10.0-android was computed. net10.0-browser was computed. net10.0-ios was computed. net10.0-maccatalyst was computed. net10.0-macos was computed. net10.0-tvos was computed. net10.0-windows was computed. |
-
net10.0
- HarfBuzzSharp (>= 14.2.0)
- HarfBuzzSharp.NativeAssets.Linux (>= 14.2.0)
- HarfBuzzSharp.NativeAssets.macOS (>= 14.2.0)
- HarfBuzzSharp.NativeAssets.Win32 (>= 14.2.0)
- Microsoft.AspNetCore.Components.Web (>= 10.0.11)
- Microsoft.Extensions.DependencyInjection (>= 10.0.11)
- Microsoft.Extensions.DependencyInjection.Abstractions (>= 10.0.11)
- Pysar.Viewer (>= 0.1.31)
- SkiaSharp (>= 4.151.2)
- SkiaSharp.NativeAssets.Linux (>= 4.151.2)
- SkiaSharp.NativeAssets.macOS (>= 4.151.2)
- SkiaSharp.NativeAssets.Win32 (>= 4.151.2)
- Svg.Skia (>= 5.2.3)
NuGet packages
This package is not used by any NuGet packages.
GitHub repositories
This package is not used by any popular GitHub repositories.
### Added
- Report watermarks: `Report.Watermark` / `ReportBuilder.WithWatermark`, XAML child, repeats on every page, full physical page, `Layer` (behind or in front of content), `IsVisible`.
- `Opacity` (0..1) and visual `Rotation` (around bounds center) on report elements.
- Rounded frames: `CornerRadius` (1 or 4 values). Borders wrap the inner content radius; children clip to the inner arc.
- XAML file overlay for unsaved editor buffers during preview/resource load (overlay wins over disk).
### Fixed
- MAUI pinch/zoom after Shell flyout navigation (stale recognizers on the old scroll view).
- ReportView gesture lifecycle: detach/reattach on handler changes and `Loaded`, so gestures survive navigation.
### Changed
- Native libraries: SkiaSharp 4.151.2, Svg.Skia 5.2.3, HarfBuzzSharp + native assets, MAUI / Microsoft.Extensions 10.x.