Running easyPDF SDK in 64-bit environment
Last Updated: 5/24/2012
The 32-bit and 64-bit editions of BCL easyPDF SDK offer the same features and share the same API
BCL easyPDF SDK version 6.0 and up support
Win64 running on the x64 chip set. 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.
are some notes to keep in mind when working on each platform.
- The 32-bit edition of easyPDF SDK must be used, and the
application that utilizes the SDK must also be 32-bit.
- Win64 supports both 32-bit and 64-bit processes. However all
drivers, including printer drivers, must be 64-bit. Thus, the
64-bit edition of easyPDF SDK must be used.
- The application that utilizes the SDK, by contrast, can be
either 32-bit or 64-bit. That choice is entirely up to you as the
SDK will work either way.
- However If your computer is running a 32-bit Installation of Office or any other host application on a 64-bit Operating System, our SDK will need to create a temporary copy of the input file in order to function. This means the MakeTempCopyOfInput property must be set to True, as it is by default.
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:
- Currently, the ability to "print" common PDFs to PDF/A are only
available in the 32-bit edition (note, however, that while
technically possible, converting from PDF to PDF is generally
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 are platform agnostic and will always run as 64-bit
under Win64, and in some cases cross compilers will allow you to
toggle between 32-bit and 64-bit binaries.
Also be aware that although our SDK can run through a 32-bit
application even on a 64-bit machine, this will require that the
SDK make use of an interpreter application, which can cause a
significant decrease in performance.