Pysar.Blazor 0.1.53

.NET 10.0 This package targets .NET 10.0. The package is compatible with this framework or higher.
There is a newer version of this package available.
See the version list below for details. 
dotnet add package Pysar.Blazor --version 0.1.53
                    


                    

                
NuGet\Install-Package Pysar.Blazor -Version 0.1.53
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.53" />
For projects that support PackageReference, copy this XML node into the project file to reference the package. 
<PackageVersion Include="Pysar.Blazor" Version="0.1.53" />
                    


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


                    

                
#r "nuget: Pysar.Blazor, 0.1.53"
#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.53
#: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.53
                    


                            Install as a Cake Addin
                        

                    

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


                            Install as a Cake Tool

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.

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.63 40 10/1/2026
0.1.56 105 9/20/2026
0.1.53 95 9/20/2026
0.1.46 110 9/18/2026
0.1.44 95 9/16/2026
0.1.41 95 9/15/2026
0.1.38 98 9/14/2026
0.1.34 98 9/13/2026
0.1.31 100 9/11/2026
0.1.24 115 9/6/2026
0.1.10 111 8/30/2026
0.1.0 103 8/30/2026

## Highlights

### `ReportAsset` — a single way to ship report assets
Fonts, images and other report resources can now be declared once as a
`ReportAsset` MSBuild item. The build translates it into each host framework's
own item type (`MauiAsset`, `AvaloniaResource`, `EmbeddedResource`, …), and a new
`EmbeddedAssetFileSystem` reads assets straight from the manifest resources of
assemblies marked with `[PysarAssetSource]`. This means a shared report library
can carry its own fonts and images, and every host can see them.

A new `FallbackFileSystem` chains the platform's own asset source ahead of the
embedded one. All five UI platforms (MAUI, WPF, Avalonia, Uno, Blazor) and both
disk-backed `DefaultReportPlatformHandler` constructors install this chain, so
console apps, workers, server-side rendering and the design-time preview resolve
embedded assets too.

> An `IFileSystem` you pass explicitly is **not** widened — it stays the caller's
> whole answer.

### Trimming support
`Pysar.dll` now embeds an `ILLink.Descriptors.xml`, and `Pysar.Xaml` ships a
`build/Pysar.Xaml.targets` that auto-generates an embedded trimmer descriptor for
any project containing `.rxaml` reports (opt out with `PysarDisableTrimmerRoots`).
See `docs/trimming.md` for WebAssembly trimming behaviour.

### Avalonia: shared renderer and export
New `PysarAvalonia` entry point with a shared renderer/export service and proper
reset logic behind `AppBuilderExtensions`, plus headless Avalonia tests.

### Platform layer refactor
Platform-specific handlers are replaced by `DefaultReportPlatformHandler` backed
by per-platform `IFileSystem` implementations. Desktop/macOS printing and the
macOS pinch monitor moved into `Pysar.Viewer.Platform`, and desktop print logic is
centralised in `DesktopPdfPrint`. Obsolete platform shims were removed.

## Performance

- **`ImageRenderCache`** — a session-scoped cache for image bytes, bitmaps and
 SVGs, wired into both the prefetch and draw paths, with failure tracking and
 deterministic disposal.
- **Faster layout** — `GridLayoutMeasurer`, `StackLayoutMeasurer`, `TextMeasurer`
 and `LayoutEngine` were reworked; `BindingEngine` and `PropertyPathResolver`
 were optimised.
- Removed the `#if DEBUG` `[Pysar.Perf]` zoom instrumentation that logged to the
 console in every consumer's Debug build.

## Fixes

- **Stale pinch-zoom tiles** — rapid pinch commits could leave superseded zoom
 generations in the tile cache, keeping cells from older scales on screen. Only
 the active generation and one bridge generation are kept now.
- **Touch axis lock** — `ReportView` locks a swipe to its dominant axis, so
 scrolling no longer drifts sideways.
- **WPF printing** — the printer now imports the viewer platform namespace it
 needs for the print flow.

## Authoring and tooling

- XAML source generation: richer binding validation with namespace/name
 collection and real diagnostics.
- New API surface: `StyleExtensions.WithStyle`, `AddElements` overloads on
 `ReportContainer`, `PysarBuilder.AddFonts`, and a default `Band` height.
- Quick start and the MAUI/Uno/Avalonia READMEs now document `ReportAsset`
 instead of hand-declared asset items.

## Breaking changes

- **`MeasureAsync` / `ProbeAsync` are now synchronous `Measure` / `Probe`**
 throughout the layout and rendering pipeline. Custom element measurers and any
 code calling the measure API must drop `await` and the `Task` return type.
- **Platform handler types removed** — `MauiReportPlatformHandler`,
 `WpfReportPlatformHandler` and `AvaloniaReportPlatformHandler` are gone; use
 `DefaultReportPlatformHandler` (installed for you by `UsePysar` /
 `AddPysar` / `UsePysar()` on the app builder).
- `IImageCache` / `LocalImageCache` lost members superseded by `ImageRenderCache`.
- `PysarWpf` and `Pysar.Avalonia.ReportView` helper shims were removed.

## Tests

~2,000 lines of new test coverage: embedded-asset and fallback file systems,
per-platform asset chains, pinch-commit placement, image-render caching, PDF
print on desktop, trimmer roots and package layout, and binding validation.