BCL easyPDF SDK
easyPDF SDK Usermanual
PDF Creator Programming API  |  Download Free Trial  |  Contact Us to Purchase

System Requirements

Operating System

Note: Service Pack Updates to the listed Operating Systems are supported unless otherwise noted. Both 32-bit and 64-bit editions are supported.

Note: .NET Framework 4.x is required for many features.

Note: HTMLPrintJob does not work on Windows XP or Server 2003. It requires Vista or Server 2008 or later.

Note: Windows XP, Windows Server 2003 and Windows 8 prior to 8.1 are no longer supported by Microsoft. In addition, .NET Framework 1.1, 2.0, 3.0, 3.5 are no longer supported by Microsoft.

For PDF Creation

Note: Office 2003 and 2007 have serious limitations that affect easyPDF SDK in a negative way. Office 2010 or newer is strongly recommended.

For Development

For the Native .NET API

For the Native Java API

Considerations for Windows Vista, 7, 8.x, 10, Windows Server 2008 and 2012 with Microsoft Word

Under Windows Vista, 7, 8.x, 10, Windows Server 2008 and 2012, with Microsoft Word 2003 and 2007, for conversions using WordPrintJob from a system service or a web service, an interactive user must be logged in to the machine at all times. This requirement applies to ASP and ASP.NET alike. Note that only WordPrintJob is affected, whereas other Office conversion classes such as ExcelPrintJob, PowerPointPrintJob, PublisherPrintJob, and VisioPrintJob are not.

If a user cannot be permanently logged in to the machine for some reason, then consider the following workarounds:

Considerations for Internet Explorer 9 and Above

Beginning with Internet Explorer 9, Microsoft has deprecated and de-implemented vital functionality that was necessary for our HTML to PDF rendering. This affects IEExtendedPrintJob only. IEPrintJob continues to work well, because it is based on printer driver technology.

However, IEExtendedPrintJob no longer works as expected with Internet Explorer 9 and above. Often PDF documents come out as raster images, instead of lines and text.

We recommend that IEPrintJob or HTMLPrintJob is used instead of IEExtendedPrintJob.