Perhaps an issue with different versions of Acrobat reader? I d look into this.

This doesn t make a lot of sense because AbcPdf uses service side logic to create the PDF based on what methods you are using to create the document (ex. AddImageUrl vs drawing out the document manually, etc.).

For what it s worth the staff at WebSuperGoo (the vendor of AbcPdf) is great with replying to support questions such as this. I ve run across a few edge cases with their product that they ve always followed up with workarounds or alternatives to address in a timely manner.

make sure you have media="print" for the CSS style sheet! Just spent ages looking at this pulling my hair out and was about to email WebSuperGoo then that thought came to me. just about to back out all the changes I ve made to my code and test again but it looks like with EngineType.Gecko it needs to be media="print" where as with EngineType.MSHtml it can be media="screen".....

very odd but hope that helps someone!

Make sure that the CSS is an absolute URL rather than relative, or add a base tag to the header of the HTML

For example, rather than

<style type="text/css" href="/styles/somecss.css" rel="stylesheet" />

use

<style type="text/css" href="http://myserver.com/styles/somecss.css" rel="stylesheet" />

Also if you site is SSL or authenticated then you will have to either make the area with the stylesheet un-authenticated, or, set the password and username attributes of the PDF object so that ABCPdf can authenticate

You can try the following in version 9

doc.HtmlOptions.PageLoadMethod = 
     PageLoadMethodType.WebBrowserNavigate;

I am using Version 10 of ABCpdf and I found that the style sheet path should be absolute instead of relative.

I changed the stylesheet path from "C:MyProjectResourcesStyles.css" to "http:www.MyDomain.comResourcesStyles.css" and it worked.

Although, version 6 seems to be working with relative paths. I didnot check it with other versions

As per WebSuperGoo support:

(Query # : 6.17)

HTML does not exist within a file and so it does not have a location.

External stylesheets and images are often referenced via relative URLs. Because the HTML has no location it is impossible to resolve these relative references.

So you need to provide your stylesheet and image links as absolute references. Or you may be able to use the HTML BASE element to specify an appropriate base location. Or you can save your HTML to file in an appropriate location and then use AddImageUrl.

Have you tried;

theDoc.HtmlOptions.DoMarkup = true;

This forces the engine to process the HTML before rendering.