Running BCL easyPDF SDK in 64-bit environment
The 32-bit and 64-bit editions of BCL easyPDF SDK offer the same features and share the same API.
There is one notable exception to this: the ability to "print" common PDFs to PDF/A. Currently, the ability to "print" common PDFs to PDF/A is only available in the 32-bit edition (Note: It is generally inadvisable to convert PDF to PDF(/A)).
For Java users, please submit a Support Request if you have 64-bit JDK requirement.
Bear in mind that BCL 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.
Deploying in Win32
The 32-bit edition of BCL easyPDF SDK must be used, and the application that utilizes the SDK must also be 32-bit.
Deploying in Win64
Although Win64 operating system supports both 32-bit and 64-bit processes, all drivers, including printer drivers, must be 64-bit. Thus, the 64-bit edition of BCL 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.
|