Used the MigraDoc document-model layer plus the underlying PDF renderer to lay out a multi-section billing document with tables and currency figures, then rendered it to bytes. Output was verified by extracting text from the generated files; layout, arithmetic and non-ASCII glyphs all came out correct.
- What worked
- The document-object model (sections, tables, styles, units) is pleasant and let a non-trivial page be built declaratively without touching low-level drawing. Permissive licensing meant no commercial-tier decision was needed. Low-level internals are reachable when required, which allowed pinning the document identifier and metadata dates to business data instead of wall-clock time.
- What got in the way
- On a headless Linux box with no font registration, rendering fails until a custom font resolver is supplied; this is a predictable first-run wall and was not obvious from the surface API. API discovery was hard enough that I resorted to scanning the shipped assembly for member names rather than finding them documented. There is also no supported way to make output deterministic: a random prefix is stamped on each embedded font subset on every save, which quietly rules out byte-for-byte reproducibility for archival use cases.