Pysar 0.1.65
dotnet add package Pysar --version 0.1.65
NuGet\Install-Package Pysar -Version 0.1.65
<PackageReference Include="Pysar" Version="0.1.65" />
<PackageVersion Include="Pysar" Version="0.1.65" />
<PackageReference Include="Pysar" />
paket add Pysar --version 0.1.65
#r "nuget: Pysar, 0.1.65"
#:package Pysar@0.1.65
#addin nuget:?package=Pysar&version=0.1.65
#tool nuget:?package=Pysar&version=0.1.65
Pysar
Pysar is a report engine for .NET: you describe a paginated document once — in XAML markup or with a fluent C# builder — hand it your data, and get back a vector PDF, a set of bitmap pages, or a scrollable, zoomable view inside your application.
This package is the core: the report element tree, data binding, and the SkiaSharp measurement,
pagination, rendering and PDF engine. Add Pysar.Xaml for declarative .rxaml markup and one
Pysar.<Platform> package for an in-app report view.
var report = ReportBuilder.Create("Hello report")
.WithPageFormat(new PageFormat { Margin = new Thickness(30) })
.WithDetail(detail => detail.AddElement(new Text { Content = "Hello from Pysar" }))
.Build();
await new SkiaReportRenderer().SavePdfAsync(report, "hello.pdf");
What you get
A report is a vertical stack of bands — report header, page header, detail, page footer, report
footer — and the detail band is the one that repeats over your data. Inside a band you compose the
usual layout primitives: Grid, StackPanel, Frame, Text, Image, plus Repeater for nested
master-detail groups.
- Two authoring styles, one object model.
.rxamlmarkup (packagePysar.Xaml) for reports with a fixed shape, the fluent builder for reports whose structure is computed at runtime. They produce the same tree and can be mixed. - Data binding with
{Binding}, string formats, value converters and data triggers for conditional formatting. Bindings resolve once, at build time — a report is a document, not a UI. - Real pagination. Detail rows are sliced across pages, detail headers can repeat on every page,
page bands are re-resolved per page, and
PageNumber/PageCountare available to bindings and to anOnPageChangedAsynchook. - Vector PDF output — text stays selectable and sharp at any zoom — plus bitmap page rendering at an arbitrary scale.
Everything is measured in points (1/72"). A4 portrait is 595.5 × 842 pt.
Exporting to PDF
SkiaReportRenderer writes the built report as a vector PDF. Build() must run first; a report can
only be built once, so build right before you export:
using Pysar.Export;
using Pysar.Skia;
report.Build();
// straight to a file
await new SkiaReportRenderer().SavePdfAsync(report, "invoice.pdf");
// or onto any stream, e.g. an HTTP response body
await new SkiaReportRenderer().RenderToPdfAsync(report, httpContext.Response.Body);
// or as an in-memory byte array, e.g. to attach to an email
byte[] pdfBytes = await new SkiaReportRenderer().RenderToPdfBytesAsync(report);
// PDF/A-2b document setup. Skia does not validate the file.
await new SkiaReportRenderer().RenderToPdfAsync(
report, httpContext.Response.Body, new PdfExportOptions { PdfA = true });
Requirements
- .NET 10 SDK
- SkiaSharp native assets for the target platform (the platform packages bring the right ones)
- A platform implementation of
IReportPlatformHandlerfor file and font access —DefaultReportPlatformHandlerreads assets from the application directory, and the platform packages install one for their own asset source
Related packages
A consumer names at most three packages: Pysar always, Pysar.Xaml for reports written in
.rxaml markup, and one platform package for the target UI framework.
| Package | Responsibility |
|---|---|
Pysar.Xaml |
Declarative report markup: the runtime loader and the code-behind source generator |
Pysar.Maui |
.NET MAUI integration: app-package assets, font registration, PDF export and sharing |
Pysar.Avalonia |
Avalonia integration: avares:// assets, font registration and the report view |
Pysar.Blazor |
Blazor integration: the report viewer component, printing through the browser |
Pysar.Wpf |
WPF integration (Windows only): pack/manifest assets, font registration and the report view |
Pysar.Viewer — the framework-neutral viewer logic — is not referenced directly; it arrives
transitively with a platform package.
One rule worth knowing up front
Report.Build() mutates the report tree: it resolves bindings, expands repeaters and applies
triggers. A Report instance can therefore be built once. Create or load a new instance for each
document — building the same one twice throws.
Rendering that built instance more than once is supported, but only sequentially (PDF and then page
bitmaps, or a retry of the same export). Do not render one instance concurrently. PageNumber and
PageCount are scratch written during the pass, and OnPageChanged runs again on every render.
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.1.1)
- HarfBuzzSharp.NativeAssets.Linux (>= 14.2.1.1)
- HarfBuzzSharp.NativeAssets.macOS (>= 14.2.1.1)
- HarfBuzzSharp.NativeAssets.Win32 (>= 14.2.1.1)
- Microsoft.Extensions.DependencyInjection.Abstractions (>= 10.0.11)
- 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 (4)
Showing the top 4 NuGet packages that depend on Pysar:
| Package | Downloads |
|---|---|
|
Pysar.Viewer
Framework-neutral logic for a paginated report viewer: page geometry, zoom, tile planning and the tile cache. |
|
|
Pysar.Xaml
Runtime XAML loader for Pysar: parses and constructs report objects from declarative markup. |
|
|
Pysar.Maui
.NET MAUI integration for Pysar: application-package asset access, font registration, PDF export and sharing. |
|
|
Pysar.Uno
Uno Platform integration for Pysar: application asset access, font registration, a scrollable, zoomable report view, PDF printing and sharing. |
GitHub repositories
This package is not used by any popular GitHub repositories.
| Version | Downloads | Last Updated |
|---|---|---|
| 0.1.65 | 156 | 11/2/2026 |
| 0.1.63 | 174 | 10/1/2026 |
| 0.1.56 | 279 | 9/20/2026 |
| 0.1.53 | 160 | 9/20/2026 |
| 0.1.46 | 165 | 9/18/2026 |
| 0.1.44 | 165 | 9/16/2026 |
| 0.1.41 | 166 | 9/15/2026 |
| 0.1.38 | 158 | 9/14/2026 |
| 0.1.34 | 156 | 9/13/2026 |
| 0.1.31 | 163 | 9/11/2026 |
| 0.1.24 | 175 | 9/6/2026 |
| 0.1.10 | 160 | 8/30/2026 |
| 0.1.0 | 164 | 8/30/2026 |
Added automatic font resolution from platform registrations:
- MAUI: reports can use fonts registered with ConfigureFonts by alias.
- Uno: fonts declared with UnoFont are available by family name and matching style.
- Explicit AddFont registrations retain priority.
Fixed cross-assembly font cache leakage and duplicate embedded font resources in Uno. Updated documentation and added MAUI and Uno examples.