Dink2PDF Azure deployment.
So i’ve been using Dink2PDF to generate PDF files.
It requires this .dll file from their github repo titled ”libwkhtmltox.dll” to be used.
Now here’s the kicker, locally this method works fine. But if the method is generated through the Azure deployed backend the text isn’t generated properly and ends up just being a bunch of squares.
As the image supplied.
Ontop of this; you can only use the method ONCE after each deployment, the following times it starts looping endlessly forever.
Which leads me to believe that the issue stems from the deployed .dll file. How do you guys typically handle loose .dll files in cloud based environments?
It requires this .dll file from their github repo titled ”libwkhtmltox.dll” to be used.
Now here’s the kicker, locally this method works fine. But if the method is generated through the Azure deployed backend the text isn’t generated properly and ends up just being a bunch of squares.
As the image supplied.
Ontop of this; you can only use the method ONCE after each deployment, the following times it starts looping endlessly forever.
Which leads me to believe that the issue stems from the deployed .dll file. How do you guys typically handle loose .dll files in cloud based environments?
