Hi,

If you meat the ASPXToPDF sample, then you will need upgrade to EO.Web Controls 2010 first because ASPXToPDF does not exist in early versions. If you purchase the upgrade and EO.Pdf at the same time, we can give you an additional $50 discount.

If you do not wish to upgrade, you can still convert your page to PDF. Just converting an ASPX page to PDF itself does not have anything to do with EO.Web. You basically just call HtmlToPdf.ConvertUrl with your page Url to PDF. This works regardless whether the Url is an ASP.NET page or any other page. This means you do not have to use ASPXToPDF to export your page.

Special consideration needs to be taken if your page requires log in because the converter will not be going through the login page. See here for more details:

http://www.essentialobjects.com/forum/postst5528_How-to-convert-a-Web-page-that-requires-login-to-PDF.aspx

ASPXToPDF is a special ASP.NET server control that comes handy in that situation. It still relies on EO.Pdf to perform the actual conversion but it is a server control, thus it lives inside your session and have access to the current session login data. ASPXToPDF is the easiest solution for this scenario. However the original post in the above thread outlined one possible solution without ASPXToPDF for this scenario. This post also provides some additional information about this:

http://www.essentialobjects.com/forum/postst5713_Converting-HTML-String-to-PDF-with-Session-Based-Security.aspx

To sum it up, if your page does not need log in, then you do not need to do anything special at all. If your page does require login, then you will need to either upgrade in order to use ASPXToPDF control, or modify your server side code so that your page can work without login.

Hope this helps. Please feel free to let us know if you have any more questions.

Thanks!