Logo
My Account |  Site Map | Contact Us  
 The same content in Microsoft HTML help file format is included in the download package.
Deployment

To deploy a project using EO.Pdf, you need to include the following DLLs along with your project:

  • You must include EO.Base.dll and EO.Pdf.dll;
  • Unless you explicitly use the old browser engine, you should also include EO.WebEngine.dll and EO.WebBrowser.dll;
    -- OR --
  • If you do explicitly use the old browser engine, you must include EO.Pdf.Classic.dll;

There are no additional setups or configurations needed either on your server or your client's machine.

If you use ASPXToPDF, you must also include EO.Web.dll in your application's bin directory. If you use MVCToPDF, you must also include EO.Pdf.Mvc.dll in your application's bin directory.

Deploy to a shared hosting environment

If you plan to deploy EO.Pdf to a shared hosting environment, please check with your host company whether they support full trust. EO.Pdf makes numerous native API calls, thus it requires full trust to run. If your hosting company cannot grant full trust to your site, you may need to consider move your site to a dedicated server or virtual server.

Deploy to Windows Azure

If you plan to deploy to Windows Azure, make sure you deploy to a Virtual Machine. EO.Pdf does not support Windows Azure WebSite. This is because EO.Pdf uses Windows GDI but Windows GDI is not supported by Windows Azure WebSite. To resolve the issue, you can either deploy your site to a Virtual Machine, or isolate the PDF related feature into a separate Web Service that runs on a different server (either on a Windows Azure Virtual Machine, or a dedicated server hosted elsewhere), then call the web service from your Windows Azure WebSite.


Direct link to this topic