The hardware and software environment required to successfully deploy applications using the EVO HTML to PDF Converter is described below.
Operating System
The product is compatible with Windows XP, Windows 2003 Server and later versions of Windows. Windows 7 64-bit or Windows 8 64-bit are recommended for development and Windows Server 2008 R2 or Windows Server 2012 are recommended for deployment.
Hardware Architecture
The product should work without problems both on 32‐bit and 64‐bit versions of Windows. However, when converting very large HTML documents the memory consumption can go high and in this case it is recommended to run the converter in a 64‐bit process which has a larger address space. When using the library in ASP.NET you have to set 'Enable 32-bit' flag of the IIS application pool on false to make sure the converter runs in a 64-bit process.
Internal Memory
The converter uses the internal memory for intermediate data structures and to store the generated PDF document. Function of the HTML document the internal memory usage during conversion can be lower or higher. In general it is recommended to have a server with at least 2GB of free RAM where to deploy your application using the converter. If you convert very large HTML documents you should make sure you run the converter in a 64-bit process. See the previous section for more details.
.NET Runtime Version
The converter library is compatible both with .NET Framework 2.0 and 4.0 runtimes. There are two distinct sets of libraries and samples in the same installation folder: for .NET CLR 2.0 (which is the runtime for .NET 2.0, .NET 3.0 and .NET 3.5) and for .NET CLR 4.0 (which is the runtime for .NET 4.0 and .NET 4.5). In general it is recommended to use the version of the library targeting the .NET 4.0 runtime.
ASP.NET Trust Level
The converter needs Full Trust level in ASP.NET applications. This is the default trust level in IIS.