All EO DLLs are 100% managed DLLs. So you can simply include the DLLs with your distributions. There are no additional setup/configuration needed on the runtime environment. This topic outlines which DLLs are needed for each products as well as common deployment scenarios.

EO.Pdf

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

• You must include EO.Base.dll, EO.Pdf.dll, EO.WebEngine.dll and EO.WebBrowser.dll;
• If you use ASPXToPDF, you must also include EO.Web.dll;
• If you use MVCToPDF, you must also include EO.Pdf.Mvc.dll;
• If you use the WPF version of the PdfViewer class, you must also include EO.Pdf.Wpf.dll;

EO.Web

See here for more details.

EO.WebBrowser

To deploy EO.WebBrowser, you must include EO.Base.dll, EO.WebEngine.dll and EO.WebBrowser.dll. These DLLs contain all the core code as well as the Windows Forms WebControl.

If your project uses WPF and you use the WPF WebControl class, then you also must include EO.WebBrowser.Wpf.dll in your distribution.

EO.Wpf

EO.Base.dll and EO.Wpf.dll are the only files needed at runtime.

Deploy to a shared hosting environment

If you plan to deploy EO to a shared hosting environment, please check with your host company whether they support full trust. EO products 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 products do not support Windows Azure WebSite. This is due to fact that Windows Azure WebSites run in shared environment where multiples WebSites share one server and Microsoft restricts what each WebSite can do to avoid mistakes in one WebSite from accidently affecting other WebSites. To resolve the issue, you can either deploy your site to a Virtual Machine, or isolate the EO 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.