Our great sponsors
-
gotenberg
A developer-friendly API for converting numerous document formats into PDF files, and more!
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
-
-
PdfSharpCore
Port of the PdfSharp library to .NET Core - largely removed GDI+ (only missing GetFontData - which can be replaced with freetype2)
-
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
-
-
-
WkHtmlToPdf-DotNet
C# .NET Core wrapper for wkhtmltopdf library that uses Webkit engine to convert HTML pages to PDF.
-
scryber.core
Scryber.Core is a dotnet html to pdf engine written entirely in C# for creating beautiful flexible, flowing documents from html templates including css styles, data binding, svg drawing and encryption
I remember I used Razor to build HTML that I could then throw into wkhtmltopdf. There is a c# wrapper somewhere on github.
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).
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).
PdfSharpCore https://github.com/ststeiger/PdfSharpCore, a .NET Core port of PdfSharp, might come to the rescue as it has largely removed GDI+.
BlazorReports
Do you know carbone.io https://github.com/carboneio/carbone it’s work with templates (docx, xmlx, etc) you cant run a micro service with a endpoint and, from .Net call that API and send payload data. Work ready
Gotta plug a rendering service my company created and then open sourced -- runs on top of react-pdf. Basically it exposes the rendering engine via a RESTful API.
Gotta plug a rendering service my company created and then open sourced -- runs on top of react-pdf. Basically it exposes the rendering engine via a RESTful API.
If you wnat to take a look on how to optimise this flow, use flsgs and ideas from this well made Elixir project, https://github.com/bitcrowd/chromic_pdf
I just googled real quick and this popped up: https://github.com/HakanL/WkHtmlToPdf-DotNet
u/WolfenBass1, just spotted your post, and feel free to check out Scryber.Core. It sounds like it supports what need, and will run client-side in Blazor (as well as server side). Using templates, based on html with data binding with expressions you should be able to do what you need. It is open source, and free. Also on Nuget, and any feedback is gratefully received.