Native queues and dialogs
Platform Print Adapters
Keep one print API while honoring each desktop printing system.
Explore source ↗Capability
Windows Win32/XPS, macOS AppKit/Quartz, and Linux CUPS/GTK adapters discover queues, inspect capabilities, coordinate native dialogs, and respect sandbox or portal constraints.
- 01
Win32 spooler and XPS flows
- 02
AppKit and Quartz integration
- 03
CUPS, GTK, Flatpak, and Snap portals
- 04
Runtime adapter selection
How it composes
From intent
to working system.
Select
The Avalonia bootstrap chooses the platform adapter at startup.
Discover
Native services report queues, capabilities, defaults, and constraints.
Dialog
Platform UI gathers user ticket and destination choices.
Submit
The adapter renders and monitors the native print job.
Quick start
Adopt this
capability.
Start with the primary module, then add the related packages only when the application needs those layers. Replace VERSION with the current NuGet version.
dotnet add package PrintingTools.Windows<PackageReference Include="PrintingTools.Windows" Version="VERSION" /><PackageVersion Include="PrintingTools.Windows" Version="VERSION" />AppBuilder.Configure<App>() .UsePlatformDetect() .UsePrintingTools(options => { options.EnablePreview = true; options.DiagnosticSink = Console.WriteLine; });Modules in this capability
Use one layer.
Compose the rest.
Source of truth
Read the module beside the complete system.
The implementation, samples, issues, and release notes stay in the parent repository so module details remain connected to the product architecture.