Pysar.Maui 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.Maui --version 0.1.63
                    


                    

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


                            Directory.Packages.props
                        

                    

                
<PackageReference Include="Pysar.Maui" />
                    


                            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.Maui --version 0.1.63
                    


                    

                
#r "nuget: Pysar.Maui, 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.Maui@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.Maui&version=0.1.63
                    


                            Install as a Cake Addin
                        

                    

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


                            Install as a Cake Tool

Pysar.Maui

.NET MAUI integration for Pysar, a cross-platform report engine for .NET: application-package asset access, font registration, PDF export, sharing and a scrollable, zoomable ReportView. It installs a DefaultReportPlatformHandler over AppPackageFileSystem for file and font access, and brings the right SkiaSharp native assets for each target platform.

Android, iOS and Mac Catalyst are the platforms the package is built for; the Windows target only appears when packing on a Windows host, and ships untested.

Setup

Declare fonts and images with ReportAsset. Pysar packages them as MauiAsset items, read straight from the application package — nothing is extracted to disk:

<ItemGroup>
  <ReportAsset Include="Fonts\**;Images\**" />
</ItemGroup>

builder
    .UseMauiApp<App>()
    .UsePysar(pysar => pysar
        .AddFont("Fonts/Ubuntu-Regular.ttf", "Ubuntu")
        .AddFont("Fonts/Ubuntu-Bold.ttf", "Ubuntu", FontStyle.Bold));

SkiaReportRenderer, IReportExportService, IReportSharer and IReportPrinter are then injectable: the export service writes a report to a stream or a byte array in a requested ExportFormat, the sharer offers those bytes to the platform share sheet, and the printer opens the platform print dialog.

byte[] pdfBytes = await exportService.ExportAsync(report, ExportFormat.Pdf);

Showing a report

<pysar:ReportView Report="{Binding Report}"
                    ZoomMode="FitWidth"
                    Zoom="{Binding Zoom}"
                    EffectiveZoom="{Binding EffectiveZoom}"
                    CurrentPage="{Binding CurrentPage}"
                    PageSpacing="24" />

Pinch zooms around the fingers and a double tap switches between fitting the width and reading close up, both anchored on the point they were made at. PageBorderColor and PageBorderThickness frame each page; PageSpacing is the gap between pages and does not scale with the zoom. Bind EffectiveZoom to show the zoom percentage — Zoom holds what was asked for, not what the view settled on.

Documentation

License

MIT — see LICENSE.

Product Compatible and additional computed target framework versions.
.NET net10.0-android36.0 is compatible.  net10.0-ios26.0 is compatible.  net10.0-maccatalyst26.0 is compatible. 
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 47 10/1/2026
0.1.56 96 9/20/2026
0.1.53 92 9/20/2026
0.1.46 99 9/18/2026
0.1.44 90 9/16/2026
0.1.41 101 9/15/2026
0.1.38 103 9/14/2026
0.1.34 108 9/13/2026
0.1.31 114 9/11/2026
0.1.24 107 9/6/2026
0.1.10 110 8/30/2026
0.1.0 105 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