PuppeteerSharp VS library

PuppeteerSharp

Otherwise, any pdf to hml chromium based solution hosted via docker, like gotenberg](https://github.com/gotenberg/gotenberg) or browserless.io(which is free if you create open source). Generating pdfs from html directly in .NET was always a pain. Wkhtml (and wrappers that use it) uses WebKit and comes with a load of issues of its own, similar to running and styling anything in Safari. Using chromium based engine saves a lot of time as it's the most popular way of doing it these days. You can also use puppeteer-sharp with local chromium if you host your app on something that allows it(f.e. not Azure Functions).

Puppeteer Sharp is a port of the popular Headless Chrome NodeJS API built by Google. Puppeteer Sharp was written in C# and released in 2017 by Darío Kondratiuk to offer the same functionality to .NET developers.

there is a dotnet package for using headless chrome: https://www.puppeteersharp.com/ its a port of the nodejs package of the same name

For the actual conversion of html to pdf we use PuppeteerSharp (https://www.puppeteersharp.com ) but you need browserless for that, which requires an api key (don’t know the pricing)

The README in the GitHub site has been good enough for me: https://github.com/hardkoded/puppeteer-sharp

Iv'e been using https://github.com/hardkoded/puppeteer-sharp for html to pdf conversion for quite some time with success. (in both .net framework and .net core)

Just generate HTML and use https://github.com/hardkoded/puppeteer-sharp to produce a PDF from headless Chrome.

Another idea is to maybe generate the document as HTML first and then convert the HTML to a PDF (with somehting like PuppeteerSharp. I have found this more flexible in the past, but I have not personally done with with nested tables.

Give the official QuestPDF repository a star ⭐ so more people will know about it. Most developers evaluate project maturity based on the star count so let's help them make the right decision!

There are already a couple of free or paid libraries in the .NET ecosystem that can be used to generate PDF files. The way how QuestPDF differs is simple: instead of relying on an HTML-to-PDF conversion, it implements its own layouting engine that renders the full content using the SkiaSharp library (a Skia port for .NET, used in Chrome, Android, MAUI, etc.).

Hi, can you please elaborate more about your question? Or create a discussion on the repository page? https://github.com/QuestPDF/library/discussions I am not sure exactly what requirement you would like to achieve :)

QuestPDF is my go-to.

Hi :) That is a good point about most of the APIs available. I truly believe that it does not apply to the QuestPDF library. The Fluent API here is used only to describe the document's content, to create new element instances and assign them to parents. In other words, there is no business logic involved in this code area. Please analyze the QuestPDF.Fluent namespace. You will find that most of the API invocations are super simple and straightforward.

check out https://github.com/questpdf/library