Fonts not working on server (works locally) even though PDF is being created about wkhtmltopdf-dotnet

[markmcgookin]

Could you give me a link to this discussion on MSDN?

It's not much help, but have a read here.

I would recommend docker if you can to give you more control.

[HakanL]

Hey Mark, it sounds like this is an issue with the underlying wkhtmltopdf library, the DinkToPdf is just a wrapper around it. I think your best bet is to try the wkhtmltopdf library directly on the affected system to see if you can reproduce it and go from there.

[MDzyga]

I have the same problem and tried to use fonts from google fonts website like here: https://stackoverflow.com/questions/10611828/use-custom-fonts-with-wkhtmltopdf.
Locally it works, but after deploy on Azure App Service doesn't work.

[markmcgookin]

So I've discussed this with Microsoft over on MSDN and they had asked me to try a few things that I had already tried. None of which worked. It's still unclear whether this is an IIS issue or some web.config setting that we have no control over when deploying to Azure. It's not an issue with dink or wkhtmltopdf, it's an issue with the deployment to azure.

My solution (which Microsoft accepted and marked as the answer) was to quickly dump my webjob into a docker container, where I have full control over the environment... get my code up and running there and working locally. Then I deployed that to a kubernetes cluster in azure (a bit overkill, but apparently the container instance is obsolete and being phased out)... configuring k8s was by far the hardest bit, but I now have it up and running, because of the nature of containered apps I've got a bunch of replicas which will help with performance and I have full control over the fonts etc too. Just don't forget that you will need to add the ".so" library as well as the dll/dylib if you are running on linux.

[MDzyga]

Could you give me a link to this discussion on MSDN?