Pysar.Blazor 0.1.63

.NET 10.0 This package targets .NET 10.0. The package is compatible with this framework or higher. 
dotnet add package Pysar.Blazor --version 0.1.63
                    


                    

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


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


                    

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


                            Install as a Cake Addin
                        

                    

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


                            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

## Avalonia fonts

**Report fonts can come from Avalonia `FontManager`.**
`UsePysar` installs a typeface fallback before your configuration. The family string in the report must be the Avalonia `FontFamily` string — `fonts:Inter#Inter` after `WithInterFont`, or `avares://MyApp/Fonts#Ubuntu` for a resource folder — not a file path. A bare name is a system-font lookup; if `TryGetGlyphTypeface` substitutes Helvetica, Pysar treats that as a miss.

`AddFont` still wins. A library `ReportAsset` still needs one `AddFont`: the file is not copied into the head, and `FontManager` does not see it. A XAML `FontFamily` resource is not a registration. Styles stay `Normal`, `Bold`, `Italic` and `BoldItalic`. This bridge is Avalonia only. Console, the design-time preview, MAUI, WPF and Uno keep `AddFont`.

## PDF export

**PDF/A-2b is an option of PDF, not another format.**
Pass `new PdfExportOptions { PdfA = true }` to `SavePdfAsync`, `RenderToPdfAsync`, `RenderToPdfBytesAsync`, or `IReportExportService.ExportAsync`. Skia writes the archival document setup: XMP `pdfaid` identification, a document UUID, and an sRGB output intent. It does not validate the file. A font Skia cannot embed still fails a checker, and the UUID makes those bytes non-reproducible. Existing overloads are unchanged.

## Images

**SVG is drawn from the bytes, not only from a `.svg` path.**
A stream or embedded source whose bytes start with `<svg` (optional XML declaration) is rendered as SVG. A decode or parse failure is recorded on the image cache, so the same bad bytes are not decoded again. Fixes #23.

## Rendering

**A built report may be rendered more than once, only sequentially.**
PDF and then page bitmaps, or a retry of the same export, is supported. Do not render one instance concurrently. `PageNumber` and `PageCount` are scratch written during the pass, and `OnPageChanged` runs again on every render.

## Uno

**Android report pages no longer depend on OpenGL ES.**
`UsePysar` sets `UseOpenGLOnSkiaAndroid` to false before the window is created. OpenGL ES draws image textures as opaque black, which hid every report page.

## Internal

- Host startup (Avalonia, MAUI, WPF, Uno) shares one installation sequence, `PysarInstallation`.
- `InternalsVisibleTo` for `Pysar.Avalonia` and `Pysar.Avalonia.Tests`.

**Full changelog:** v0.1.56...HEAD