Viewer control or headless generation? It is one of the first architectural forks a .NET team hits when PDF requirements start expanding. PdfiumViewer is built for the first answer — a WinForms/WPF control that wraps Google's PDFium and renders pages to the screen, no browser dependency, native binaries shipped via separate NuGet packages. The moment the roadmap adds "generate invoices from data" or "produce reports server-side," that architecture stops carrying the workload, and a second library has to join the project — or replace it. PdfiumViewer is a WinForms and WPF control for displaying PDF documents in desktop applications, built on Google's PDFium library (the same engine Chrome uses for PDFs). The original pvginkel/PdfiumViewer repository was archived on 2019-08-02 and the last NuGet release (2.13.0) shipped on 2017-11-06, so the library still works for the cases it was designed for but is not receiving updates from the original maintainer.…