Pysar.Blazor 0.1.34

.NET 10.0

dotnet add package Pysar.Blazor --version 0.1.34

NuGet\Install-Package Pysar.Blazor -Version 0.1.34

This command is intended to be used within the Package Manager Console in Visual Studio, as it uses the NuGet module's version of Install-Package.

<PackageReference Include="Pysar.Blazor" Version="0.1.34" />

For projects that support PackageReference, copy this XML node into the project file to reference the package.

<PackageVersion Include="Pysar.Blazor" Version="0.1.34" />
                    

                            Directory.Packages.props

<PackageReference Include="Pysar.Blazor" />
                    

                            Project file

For projects that support Central Package Management (CPM), copy this XML node into the solution Directory.Packages.props file to version the package.

paket add Pysar.Blazor --version 0.1.34

The NuGet Team does not provide support for this client. Please contact its maintainers for support.

#r "nuget: Pysar.Blazor, 0.1.34"

#r directive can be used in F# Interactive and Polyglot Notebooks. Copy this into the interactive tool or source code of the script to reference the package.

#:package Pysar.Blazor@0.1.34

#:package directive can be used in C# file-based apps starting in .NET 10 preview 4. Copy this into a .cs file before any lines of code to reference the package.

#addin nuget:?package=Pysar.Blazor&version=0.1.34
                    

                            Install as a Cake Addin

#tool nuget:?package=Pysar.Blazor&version=0.1.34
                    

                            Install as a Cake Tool

The NuGet Team does not provide support for this client. Please contact its maintainers for support.

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	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.

Compatible target framework(s)

Included target framework(s) (in package)

Learn more about Target Frameworks and .NET Standard.

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.34)
- 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.

Version	Downloads	Last Updated
0.1.34	38	9/13/2026
0.1.31	45	9/11/2026
0.1.24	99	9/6/2026
0.1.10	100	8/30/2026
0.1.0	94	8/30/2026

### Added
- `DefaultReportPlatformHandler` (`Pysar.Skia`): a ready-made `IReportPlatformHandler` for hosts without a UI framework - console and worker applications, server-side rendering, and the design-time preview. Pass a directory to its constructor when assets do not sit next to the binaries.
- `LocalFileSystem` (`Pysar.Skia`): an `IFileSystem`/`ISyncFileSystem` that reads report assets from disk. Relative paths resolve against the application's deployment directory, rooted paths are read as given, and a missing asset reads as `null` instead of throwing.

### Fixed
- Asset paths now resolve against `AppContext.BaseDirectory` rather than the executing binary, so images and fonts are found when the assembly is loaded by a host such as `dotnet app.dll` or the design-time preview.

### Changed
- Rounded-border rendering builds its ring path with `SKPathBuilder`, matching the current SkiaSharp path API.
- Docs: quick start and README now describe `DefaultReportPlatformHandler` as the default, with the UI-framework handlers (`AvaloniaReportPlatformHandler`, `WpfReportPlatformHandler`, `MauiReportPlatformHandler`, `WasmPlatformHandler`) registered by `UsePysar`/`AddPysar`.