EVO PDF Logo

EVO PDF Client for .NET Core Overview

EVO PDF Client for .NET Core

EVO PDF Client library for .NET Core can be easily integrated in any application targeting the .NET Core or .NET Standard 2.0 to create, read, edit and save PDF documents. A central component of the library is the HTML to PDF Converter which allows you to convert web pages, HTML strings and streams to PDF or to image. The converter has support for HTML5, CSS3, SVG, Canvas, Web Fonts and JavaScript. It combines the powerful printer friendly PDF format with the flexibility of the HTML format into a modern tool for creating nicely formatted and easily maintainable PDF reports and documents.

The library is much more than just a HTML to PDF converter. You can also convert HTML to raster images or HTML to SVG, you can edit, merge or split existing PDF documents, convert Word and Excel documents to PDF, convert PDF document pages to images, to HTML or to text documents, extract images from PDF documents or search text in PDF documents.

In order to use the EVO PDF Client for .NET Core in your applications you first have to install the EVO PDF Server. The server can be installed as Azure Cloud Service Worker Role, Azure Cloud Service Web Role, Azure Service Fabric Application, IIS ASP.NET Web Application or Windows Service.

EVO PDF Client

EVO PDF Client for .NET Core is delivered as a ZIP archive you can download from website and extracted in a local folder. The product folder has the following structure:

  • Bin - this folder includes the development library for .NET Core

    • EvoPdfClient_NetCore.dll - the library built for .NET Standard 2.0 you can reference in your .NET Core and other type of applications compatible with this standard

    • EvoPdfClient_NetCore.xml - the library API documentation in XML format

  • Demo - this folder includes the demo Visual Studio projects for ASP.NET Core targeting .NET Core 6.0 and later versions

  • Help.chm - the library documentation and API reference

  • NuGet.txt - offers information about using the EVO PDF Client for .NET Core NuGet package

  • Readme.txt - contains important information about using the EVO PDF Client for .NET Core

  • EULA.txt - the EVO PDF Software End User License Agreement

EVO PDF Server

Before starting to use the EVO PDF Client for .NET Core in your applications you first have to install the EVO PDF Server. You can find more information about downloading and installing the server in Server Installation section.

After the EVO PDF Server was installed, you are ready to use the EVO PDF Client Library for .NET Core. Create in Visual Studio an application targeting .NET Core or .NET Standard 2.0 and reference the library assembly EvoPdfClient_NetCore.dll or the NuGet Package and copy the code lines from the sections below to use the HTML to PDF Converter component to create a PDF document from a web page.

You can also use directly our demo applications for ASP.NET Core from Demo folder. They offer an interface to enter the installed server IP address or the web service URL, function of the type of server you installed.

Use a local EVO PDF TCP/IP Server

If the EVO PDF Server is installed on the same Windows machine where you run your application then the HTML to PDF Converter client object constructor does not need additional parameters.

A typical scenario for this usage case is when you install the EVO PDF Server in a Windows Service on the same machine running the client library.

The client HTML to PDF Converter object above will try to connect to the EVO PDF Server installed on the localhost default IP address 127.0.0.1 on the default TCP port 40001.

C#
using EvoPdfClient;
HtmlToPdfConverter htmlToPdfConverter = new HtmlToPdfConverter();
byte[] outPdfBuffer = htmlToPdfConverter.ConvertUrl(url);
Use a remote EVO PDF TCP/IP Server

If the EVO PDF Server was installed as a TCP/IP server on a remote machine then you'll have to specify the HTML to PDF Service IP address in the HTML to PDF Converter client object constructor.

A typical scenario for this usage case is when you install the EVO PDF Server in an Azure Cloud Service Worker Role, in an in an Azure Service Fabric Application or in a Windows Service on a remote Windows machine.

The code below initializes a HTML to PDF Converter object that will connect to to a server running on a specified IP address and TCP port. If the port is not specified then the default port 40001 will be used.

C#
using EvoPdfClient;
HtmlToPdfConverter htmlToPdfConverter = new HtmlToPdfConverter(serverIP, serverPort);
byte[] outPdfBuffer = htmlToPdfConverter.ConvertUrl(url);
Use a remote HTML to PDF HTTP Server

If the EVO PDF Server was installed as a HTTP server on a remote machine then you'll have to specify the HTML to PDF Service HTTP URL address in the HTML to PDF Converter client object constructor.

A typical scenario for this usage case is when you install the EVO PDF Server in an Azure Cloud Service Web Role or in an IIS ASP.NET Web Application.

The code below initializes a HTML to PDF Converter object that will connect to to a server running at a specified HTTP URL.

C#
using EvoPdfClient;
HtmlToPdfConverter htmlToPdfConverter = new HtmlToPdfConverter(true, serverHttpUrl);
byte[] outPdfBuffer = htmlToPdfConverter.ConvertUrl(url);
See Also

Reference

Other Resources