Publish Azure App Service and Azure Function Apps on Windows

EvoPdf Chromium for .NET is a library that can be easily integrated in Azure App Service and Azure Functions for Windows to convert web pages and HTML strings to PDF or to image.

The HTML to PDF converter component of the library uses a rendering engine based on Chromium, which can render all modern HTML, CSS and JavaScript content in conformance with the latest standards.

EvoPdf Chromium for .NET can run in Azure App Service and Azure Functions Windows 64-bit applications without installing anything and without any prior configuration of the deployment environment. The steps necessary to use the library in your own Azure App Service and Azure Function applications are detailed below.

The .NET library targets the .NET Standard 2.0 and therefore it can be used in any .NET Core or .NET Framework application which is compatible with this standard.

Create a new .NET project in Visual Studio and use the NuGet Package Manager from Visual Studio to add a reference to the EvoPdf.Chromium.Windows package from NuGet.

After the NuGet package has been installed, at the top of your C# source file add the using EvoPdf.Chromium; statement to include the EvoPdf.Chromium namespace in your application code and to make the library API available to your application.

// add this using statement at the top of your C# file
using EvoPdf.Chromium;

You are now ready to use the library to convert web pages and HTML code to PDF or to Image using EvoPdf Chromium for .NET.

With the code below you can convert a HTML string to a PDF document in a memory buffer and then save the data from buffer into a file.

// create the converter object in your code where you want to run conversion
HtmlToPdfConverter converter = new HtmlToPdfConverter();

// convert a HTML string to a memory buffer
byte[] htmlToPdfBuffer = converter.ConvertHtml("<b>Hello World</b> from EVO PDF !", null);

With the code below you can convert an URL to a PDF document in a memory buffer and then save the data from buffer into a file. The URL can also be a local file path prefixed by the 'file://' URI scheme.

// create the converter object in your code where you want to run conversion
HtmlToPdfConverter converter = new HtmlToPdfConverter();

// convert an URL to a memory buffer
string htmlPageURL = "http://www.evopdf.com";
byte[] urlToPdfBuffer = converter.ConvertUrl(htmlPageURL);

With the code below you can convert in your ASP.NET Core applications a HTML string to a PDF document in a memory buffer and then send it for download to browser.

// create the converter object in your code where you want to run conversion
HtmlToPdfConverter converter = new HtmlToPdfConverter();

// convert a HTML string to a memory buffer
byte[] htmlToPdfBuffer = converter.ConvertHtml("<b>Hello World</b> from EVO PDF !", null);

FileResult fileResult = new FileContentResult(htmlToPdfBuffer, "application/pdf");
fileResult.FileDownloadName = "HtmlToPdf.pdf";
return fileResult;

With the code below you can convert in your ASP.NET Core applications an URL to a PDF document in a memory buffer and then send it for download to browser. The URL can also be a local file path prefixed by the 'file://' URI scheme.

// create the converter object in your code where you want to run conversion
HtmlToPdfConverter converter = new HtmlToPdfConverter();

// convert an URL to a memory buffer
string htmlPageURL = "http://www.evopdf.com";
byte[] urlToPdfBuffer = converter.ConvertUrl(htmlPageURL);

FileResult fileResult = new FileContentResult(urlToPdfBuffer, "application/pdf");
fileResult.FileDownloadName = "UrlToPdf.pdf";
return fileResult;

Uncheck the Deploy as ZIP package option when you create the publish profile in Visual Studio.

The minimum supported hosting plan size is B1 (1 core, 1.75GB). The recommended minimum hosting plan size is B2 (2 cores, 3.5 GB RAM) or a higher plan. The Free and Shared plans are not suitable for running the converter.

After the profile was created, before starting the publishing, select Portable as Target Runtime.

Publish the application in Azure App Service for Windows.

Uncheck the Run from package file option when you create the publish profile in Visual Studio.

Select the App service plan or Premium for Plan Type option in publish profile creation wizard. The Consumption plan is not suitable for running the converter.

The minimum supported hosting plan size is B1 (1 core, 1.75GB). The recommended minimum hosting plan size is B2 (2 cores, 3.5 GB RAM) or a higher plan. The Free and Shared plans are not suitable for running the converter.

After the profile was created, before starting the publishing, select Portable as Target Runtime.

Publish the Azure Function application for Windows.

Everything should have been configured at this point and now you can run your application. Alternatively, you can follow the same instructions from this document to build and publish in Azure App Service for Windows our demo application for ASP.NET.

Reference

Other Resources