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

System Requirements

Operating Systems

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 3.5 or 4.x is required for many features, including Office to PDF, EMF to PDF and XPS to PDF.

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 2007 has serious limitations that affect easyPDF SDK in a negative way. Office 2010 or newer is strongly recommended.

For Development Using the Native API (New)

Note: All sample applications assume Visual Studio 2010 or newer, and .NET 4.x.

For Development Using the COM API (Classic)

Note: All sample applications assume Visual Studio 2010 or newer, and .NET 4.x.

Note: By default, only the .NET 4.x COM Interop DLLs are installed. However, you may create your own COM Interop bridge. If requested, we can build .NET 2.0, 3.0 or 3.5 Interop DLLs for you, so you can use Visual Studio 2005, 2008.

Warning for Server-Side Customers About Major Windows Updates

Please note that installing a major Windows update, such as the Fall Creators Update, will momentarily break server-side Microsoft Office operation.

We recommend that every customer upgrades to the latest SDK build right after installing a major Windows update. If you are already on the latest SDK build, you need to uninstall and reinstall the SDK after your Windows is updated. Please remember that if you are using the Loader Service, the special user account must be reassigned to the service right after reinstalling easyPDF SDK.

In addition, it is necessary to manually log in to the special user account that is used for server-side Impersonation or the Loader Service. Windows needs to finish installing updates for each individual user, otherwise the user account is not ready for use. This only takes a minute, and you may log off right after the Windows desktop shows up.

This is all that is needed to get you up and running. If you are not ready to perform these operations, you should delay the installation of major Windows updates. This is only possible on Windows Server and Windows Professional. The Windows Home Edition does not provide an official way of delaying system updates.

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

Under Windows Vista, 7, 8.x, 10, Windows Server 2008, 2012, and 2016 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 Microsoft Excel 2016 and Microsoft Outlook

Microsoft Office is a desktop application that was not designed to be used from a Service process, such as IIS. We have provided two different workarounds, the Loader Service and the Impersonation API.

Due to a recent software update, the Impersonation API does not work with Microsoft Excel 2016 anymore. Most versions of Microsoft Outlook also fail with the Impersonation API.

Therefore, we recommend the use of the Loader Service instead, especially for those who need to print Excel or Outlook documents.

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. HTMLPrintJob also works, because it uses WebKit, instead of Internet Explorer.

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.

3rd Party Libraries Used

The following 3rd party libraries/software have been used by easyPDF SDK: