Unfortunately changing which pdf-ing method we use is not optional. the service uses http://www.html-to-pdf.net/ (the ExpertPDF)
it does all the .NET stuff and we already have the service built, the higher ups are not so interested in rewriting it, even tho it kind of sucks (b/c it relies on the local version of IE, and on our production machines, we cant change that without interrupting service, which we're highly reluctant to do). Can anyone help with the original problem of accessing elements inside an IFrame and measuring them? Thanks, -Izzy On May 19, 2:19 pm, Sanford Whiteman <[email protected]> wrote: > Guess you've already eval'd this, but does the HTML-to-PDF *only* > parse HTML? I'm thinking of abcPDF, which we use -- we were tempted to > use the HTML-to-PDF "screen shot" because it seemed easier, but it > also has robust, true PDF generation from (.NET) code. Tried the HTML > screen shot until we went crazy. Then we just buckled down, created > PDF templates, learned the object model, and now fetch from the DB > into the template. We get truly pixel-perfect PDFs now and everyone is > happier. > > -- S.
