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

x64 Support

Beginning with easyPDF SDK 6.0, both 32-bit and 64-bit Windows are supported. The 32-bit and 64-bit editions of the SDK are separate packages, so be sure to use the correct one for your operating system as they are not interchangeable. Below are some notes to keep in mind when working on each platform.

32-bit Windows:

The 32-bit edition of easyPDF SDK must be installed, and the application that utilizes the SDK must also be 32-bit.

64-bit Windows:

The 64-bit edition of easyPDF SDK must be installed, which includes support for both 32-bit and 64-bit application development. The printer driver is exclusively 64-bit, but everything else is dual 32-bit and 64-bit.

Internet Information Services is 64-bit by default, although it is possible to switch it into 32-bit mode. For desktop application development, it is entirely up to our customers whether they target 32-bit, 64-bit or both. Generally speaking, 32-bit applications do not have a lot of disadvantages, other than the maximum memory of 4GB per process. 32-bit processes are definitely not slower than 64-bit ones, except when the 4GB memory limit is an issue.

In contrast, host applications that perform the printing (Word, Excel, PowerPoint, etc.) are strongly preferred to be 64-bit. Microsoft recommends installing 32-bit Office on 64-bit Windows. We strongly recommend the opposite for the purpose of easyPDF, especially for server-side printing. 32-bit host applications are required to use an intermediate printer spooler called "splwow64" to bridge between the 32-bit process and the 64-bit driver, which significantly reduces long-term reliability, robustness and the ability to recover from errors. On the other hand, if Office is sandboxed, even the 64-bit version uses "splwow64". Although sandboxing is generally a good idea, it causes enormous reliability issues with printing. For example, timeout and crash recovery will not work properly, because "splwow64" becomes the host, instead of Word or Excel. For this reason, it is incomparably more reliable to print from a 64-bit application than from a 32-bit one. Office sandboxing should also be turned off, if possible.

This has nothing to do with the customer's own applications. The host is the process that performs the raw printing, which is usually Word, Excel, PowerPoint, Internet Explorer, and other 3rd party software packages. The application using easyPDF can be written in 32-bit or 64-bit, as it has no effect on the printing robustness. However, if the customer develops code that becomes a printing host, then it should preferably be 64-bit on 64-bit Windows.

Additional Notes:

The 32-bit and 64-bit editions of easyPDF SDK offer the same features and share the same API.

There is one notable exception to this:

Bear in mind that easyPDF SDK supports a wide variety of languages and frameworks, and which one you use may affect whether your program runs as native 64-bit or legacy 32-bit under Win64. For instance, VB6 applications will always be 32-bit, .NET applications can be platform agnostic, or can specifically target 32-bit or 64-bit.