FullBleed.DotNet 0.2.0: C# document components

Build PDF documents with ordinary C# methods, typed records, LINQ children and reusable styles. FullBleed.DotNet.UI adds immutable Element, Document, Style and StyleSheet values over the existing native renderer; no HTML strings or application framework are needed.

• Named text, structure, layout and table components; escaped text and attributes; conditional and captured sequence children.
• Explicit WithClass, inline WithStyle and outer Document.Styles, with worked examples explaining selectors, composition and style precedence.
• Direct PDF/PNG, compiled bindings and batch adapters; a complete invoice sample with registered fonts, paid/empty/credit states and multi-page rows.

Install FullBleed.DotNet 0.2.0 from NuGet. Start with the component guide or runnable source sample.

The engine remains pinned to Fullbleed 2.5.22, native ABI 1 and four platforms. Existing HTML/CSS APIs remain available; no managed runtime dependency is added. New applications can target .NET 10; the managed library also supports .NET 8 and 9.

Verification: 44 managed tests; one assembled package exercised by twelve consumers (.NET 8/9/10 on Windows x64, Linux x64, Intel macOS and Apple Silicon). Independent PDF readers check 14 component cases / 21 pages per consumer, including removed-class and removed-inline controls, 40 ordered rows, literal escaped text, compiled output and batches. Their PDFs, native previews, source inputs, extracted text and glyph observations match across these consumers. The exact README and all six guide C# blocks compile and render from the package. Existing font/layout/tagged-structure regression gates also pass.

The signed public NuGet payload matches every entry of the release-qualified package. Attached evidence retains the package identity, checksums, cross-platform reports, guide outputs and representative component PDFs/previews. These checks cover the retained fixtures; they do not claim complete language parity or new PDF conformance.

FullBleed.DotNet 0.1.8

FullBleed.DotNet 0.1.8 includes Fullbleed 2.5.22 with fixes for counter scopes, filtered clipping, border-image tiling and floated first letters. The managed API, native ABI and supported .NET/platform matrix are unchanged. Review saved PDFs when upgrading templates that use these layouts.

Install with dotnet add package FullBleed.DotNet --version 0.1.8.

The release gate checks thirteen layouts through direct and compiled rendering on .NET 8, 9 and 10 across Windows x64, Linux x64, Intel macOS and Apple Silicon macOS. All 312 resulting PDFs and both native preview sets match across those twelve consumers. Independent readers check counter labels, interior colors, text and retained Chrome character geometry. The public 0.1.7 package fails 24 of the 26 layout cases; the two already-correct controls retain identical PDFs, previews and text.

Existing font-family, inline-layout, standard-font, tagged-PDF and older-package checks remain in the gate. The retained tagged specimen passes veraPDF 1.30.2 checks for PDF/UA-1 and PDF/UA-2. These are checks of specific retained specimens, not general CSS parity or blanket PDF conformance.

The attached evidence includes the final package manifest, native-library provenance, all twelve consumer outputs, independent comparisons, the older-package controls and verification of the signed public NuGet package. External PDFium readers on Windows and Linux substitute standard Helvetica differently in the counter specimens; the PDFs, extracted text and Fullbleed native previews are byte-identical, and the reader difference is recorded explicitly.

Try the C# quickstart, ASP.NET PDF download starter or editable C# tagged notice.

FullBleed.DotNet 0.1.7

FullBleed.DotNet 0.1.7 includes Fullbleed 2.5.13 and fixes tagged HTML document structure around decorative paint, lists, figures and captions. The managed API and native ABI are unchanged.

The retained rich document specimen has zero machine-check failures in veraPDF 1.30.2 for PDF/UA-1 and PDF/UA-2. Rendering that same specimen with public 0.1.6 produces 3 and 10 failed checks respectively. Its ordinary PDF bytes, extracted text and native previews remain unchanged.

The release gate consumes the assembled package on .NET 8, 9 and 10 across Windows x64, Linux x64, Intel macOS and Apple Silicon macOS. All 12 consumers produce identical PDFs and previews for the tagged specimen. Existing font, inline-layout, standard-font and document checks remain in the gate.

Install with dotnet add package FullBleed.DotNet --version 0.1.7.

The attached evidence retains package provenance, four native-library checksums, the consumer matrix, old-package comparisons, independent validator reports and verification of the signed public NuGet package. These checks cover the retained specimens; review the final content, reading order, descriptions and assistive-technology behavior of your own documents before delivery.

Try the C# tagged PDF starter for an editable library notice, both sample PDFs and retained validation reports.

FullBleed.DotNet 0.1.6: portable standard-font previews

FullBleed.DotNet 0.1.6 pins Fullbleed 2.5.11. PNG previews of unembedded standard PDF fonts now use bundled outline substitutes, so they work without installed system fonts. The package retains the fonts' OFL and Adobe notices and their modification/provenance records.

The qualified NuGet package is consumed on Windows x64, Linux x64, Intel macOS and Apple Silicon, each under .NET 8, 9 and 10. The release checks 52 standard-font cases, 54 inline-layout cases, 22 font-family cases and six base document fixtures per consumer. Tested PDF bytes and native preview PNGs agree across those consumers.

The same isolated consumers run with system fonts hidden in a private Linux mount namespace. Public 0.1.5 produces 48 blank saved-PDF previews and twelve blank direct HTML previews; 0.1.6 renders visible text and matches the normal host. All 52 PDF byte sequences and the four embedded-font controls are unchanged. The earlier layout and family-selection negative controls remain in the gate.

Install with dotnet add package FullBleed.DotNet --version 0.1.6.

The attached evidence includes package checksums and native provenance, independent PDF/font inspections, cross-platform comparisons, old-package negative controls, and public NuGet verification. Standard-font substitutes can differ from the original designs; register explicit fonts when that appearance matters. These retained fixtures do not establish universal rendering parity or PDF standards conformance.

FullBleed.DotNet 0.1.5: inline wrapping and label widths

FullBleed.DotNet 0.1.5 brings engine 2.5.10's inline-layout fixes to C#. Text following styled inline content now wraps in the correct position, and tracked labels use corrected intrinsic widths in flex and inline-block layouts. The managed API and native ABI are unchanged.

dotnet add package FullBleed.DotNet --version 0.1.5

Affected templates can change line breaks and page layout. Review saved outputs when upgrading. The invoice and a few spacing-sensitive controls intentionally change and are checked against visually reviewed, versioned baselines.

The release workflow validates the assembled NuGet package on .NET 8, 9, and 10 across Windows x64, Linux x64, Intel macOS, and Apple Silicon macOS:

• 54 inline-layout cases exercise ordinary PDFs, fixed bindings, throughput reflow, compact reflow, and intrinsic label sizing. Independent readers check text and physical word positions. All fixture PDFs and independent PDFium pixels match across the 12 consumers.
• All 46 embedded-font native previews match across platforms. Eight unembedded Helvetica/Times previews use existing host font fallbacks and are checked across .NET versions within each platform. Register explicit font files for portable native previews; missing host fallbacks can omit glyphs.
• The pinned public 0.1.4 package fails the 44 expected layout cases. Eight unaffected wrapping controls retain identical bytes and pixels; all ten healthy controls retain their text.
• The 22 font-family cases and six document/font fixtures pass independent checks. The older 0.1.3 family-selection negative control still fails as expected. Fixed, reflow, and Unicode fixtures retain their previous bytes and pixels.
• Native architectures, retained licenses, source commit, dependency provenance, and package checksums are inspected. These retained fixtures do not establish general CSS parity or standards conformance.

The attached reports identify the exact package, source, inputs, outputs, and public NuGet verification. Full source and reproduction commands are in the development guide.

NuGet package · C# quickstart and designed invoice · ASP.NET Core download starter

FullBleed.DotNet 0.1.4: correct regular font selection

FullBleed.DotNet 0.1.4 uses engine 2.5.8 and corrects regular-font selection when an italic face is registered first. Explicit face aliases retain priority. The managed API, native ABI, and runtime dependency graph are unchanged.

dotnet add package FullBleed.DotNet --version 0.1.4

The retained Northstar invoice now uses its intended regular brand face. Its PDF is 40,449 bytes, compared with 34,542 bytes for the older, incorrectly italic output. Extracted text is unchanged; the corrected PDF and page pixels match an explicit regular-face control. That control and the other four retained fixtures remain byte-identical across versions. Review appearance and line breaks when upgrading existing templates.

Twenty-two regular/italic family cases cover both registration orders, explicit faces, CSS mappings, ordinary rendering, fixed records, and reflow records. Independent readers check embedded font names and programs, extracted text, and page pixels. The same checker rejects the previous public 0.1.3 package for selecting an italic face for normal text.

The release passes twelve isolated consumers: .NET 8, 9, and 10 on Windows x64, Linux x64, Intel macOS, and Apple Silicon macOS. All six document fixtures and all twenty-two family cases agree across those consumers. Three fresh Windows consumers also verify the signed public NuGet download against the release artifacts.

The verification ZIP contains licensed font inputs, before/after outputs, independent reader reports, checker source, and CI/publication evidence. These checks cover the supplied fixtures; they do not establish universal parity, speed, or standards conformance. The NuGet package contains no document fonts; applications register their own assets.

NuGet package ? C# quickstart ? ASP.NET starter ? Reproduce the checks

Successful release workflow.

FullBleed.DotNet 0.1.3 ? smaller PDFs with verified font output

FullBleed.DotNet 0.1.3 uses Fullbleed engine 2.5.7, which compacts embedded font metadata. The managed API, native ABI, and application dependency graph are unchanged.

dotnet add package FullBleed.DotNet --version 0.1.3

Measured whole-PDF sizes for the retained synthetic fixtures:

Document	Package 0.1.2	Package 0.1.3
Styled Northstar invoice	81,227 bytes	34,542 bytes
Bold-text fixture	84,462 bytes	43,626 bytes
Two fixed records	48,286 bytes	7,299 bytes
Two reflow records	70,506 bytes	29,779 bytes
Unicode font fixture	54,189 bytes	7,377 bytes

Extracted text, native previews, and independently rendered PDFium pixels match the previous public package. FontTools checks the retained glyph programs, metrics, mappings, checksums, and notices. Four source fonts are exercised; a fifth registered sample font is unused in these outputs. Savings depend on document content and fonts.

The same assembled package passes twelve isolated consumers: .NET 8, 9, and 10 on Windows x64, Linux x64, Intel macOS, and Apple Silicon macOS. Every fixture's PDF and saved-PDF preview bytes match across these consumers. Native tests, managed tests, formatting, Clippy, package architecture checks, and required CLI integration also pass. The previous public package is retained as a negative control for the new font-metadata gate.

The verification ZIP contains source inputs, licensed fonts, before/after outputs, independent reader reports, CI evidence, and public NuGet verification. These checks establish behavior for the supplied fixtures; they do not establish general parity, rendering speed, or standards conformance. The NuGet package contains no document fonts; applications register their own assets.

NuGet package · C# quickstart · ASP.NET starter · Reproduce the font comparison

Successful release workflow.

FullBleed.DotNet 0.1.2

FullBleed.DotNet 0.1.2 fixes the sample, API, and license links in NuGet's README renderer. It keeps the Fullbleed 2.5.6 engine and rendering behavior from 0.1.1.

dotnet add package FullBleed.DotNet --version 0.1.2

C# quickstart and designed invoice · NuGet package · API reference

The release workflow builds and tests Windows x64, Linux x64, Intel macOS, and Apple Silicon macOS, then installs the same assembled package on all four platforms before publishing. The retained invoice and bold-text PDFs and previews match across those consumers. Independent text checks also pass. These fixtures do not establish universal platform parity or ISO conformance.

Release verification and trusted publishing. Attached checksums, package metadata, and output evidence identify the validated artifacts. NuGet adds a repository signature; the public download is checked against the original archive contents and native-library hashes.

FullBleed.DotNet 0.1.1 — native PDF generation from C#

FullBleed.DotNet 0.1.1 packages the Fullbleed 2.5.6 engine for C# and .NET 8. Render static HTML/CSS inside your application, including designed invoices, PNG previews, batches, and compiled variable-data records.

dotnet add package FullBleed.DotNet --version 0.1.1

C# quickstart and designed invoice · NuGet package · Native and managed API

The package includes native runtimes for Windows x64, Linux x64, Intel macOS, and Apple Silicon macOS. Native rendering needs no Python or browser runtime. The separate CLI adapter requires an independently installed Fullbleed Python CLI. The managed assembly has no third-party NuGet runtime dependencies.

This release pins the engine and its dependency graph, includes upstream license texts, and fixes duplicate searchable text in the weight-700 bold fixture. Four isolated consumers install the same assembled package; their invoice and bold PDFs and previews match. An independent PDF reader checks styled text and two compiled records. These checks cover the retained fixtures, not universal platform parity or ISO conformance.

All release checks and trusted publication passed. The attached package manifest, checksums, and cross-platform evidence identify the tested artifacts. NuGet adds a repository signature to its public download; its archive contents and native libraries are checked against the original release artifact.

MIT licensed. Report a .NET issue.

FullBleed.DotNet 0.1.0

FullBleed.DotNet 0.1.0

First release of the .NET 8 bindings for Fullbleed PDF Engine, built against Fullbleed 2.3.1.

Highlights

• Stable native ABI bridge with source-generated .NET interop.
• Ordinary rendering, structured diagnostics, metrics, previews, batch rendering, compiled copies, fixed bindings, and reflow bindings.
• PDF inspection plus template stamp/compose finalization.
• Runtime-discovering structured CLI client.
• LINQ-friendly columnar VDP APIs, examples, and tests.
• Registered-font fixed-VDP and finalized-preview parity with the linked Fullbleed engine.

Package and platforms

The attached FullBleed.DotNet.0.1.0.nupkg includes native runtimes for:

• win-x64
• linux-x64
• osx-x64
• osx-arm64

The attached package and symbols package were assembled and smoke-tested by the cross-platform release commit CI run. They are published here as GitHub Release assets; this release does not claim NuGet Gallery publication.

See CHANGELOG.md and the CI run for details.