Table of Contents
- Getting Started
- EO.Pdf
- Overview
- Installation and Deployment
- Using HTML to PDF
- Using PDF Creator
- Working with Existing PDF Files
- Using in Web Application
- Advanced Topics
- EO.Web
- EO.WebBrowser
- EO.Wpf
- Common Topics
- Reference
Web Application Setup |
Setting up a Web application to use EO.Pdf library is exactly the same as setting it up for a regular application.
Inside your Web application, you can use EO.Pdf by:
- Using ConvertHtml/ ConvertUrl directly as you would in a traditional application. In this case you only need to reference EO.Pdf.dll;
- Using ASPX to PDF if your application is a Web Form application. If you use ASPX to PDF, you must also reference EO.Web.dll in your Web application. You can find EO.Web.dll inside "Samples\Web\Bin" sub directory inside the installation folder. You can also download and install the full EO.Web Controls from our download page. The full installation contains detailed documentation and samples for all controls in our EO.Web Controls product. While you do need an EO.Web license to use most controls in EO.Web Controls, you do not need an EO.Web license to use ASPX To PDF. ASPX To PDF is covered by EO.Pdf license. ASPX To PDF is physically packaged inside EO.Web because it share low level code with other EO.Web controls, however license wise it is considered a part of EO.Pdf product;
- Using MVC to PDF if your application is a MVC application. Like ASPXToPDF, MVCToPDF is also a part of EO.Pdf product and is covered by EO.Pdf license. So you do not need additional license to use this feature.