View Full Version : ASP to PDF

10-08-2003, 06:46 PM
Which component do you suggest?
I need to convert some invoices from HTML to PDF.. or if possible creating the PDF right from code without showing the HTML...

10-09-2003, 05:32 AM

Questions like this can only be best answered with links.
Methinks Google.com will help aswell.

10-09-2003, 05:39 AM
I would have said then:

Which component you have worked with can you recommend?

I can also Google it and get 2'345,768 entries...

Just trying to save some time and gain some experience from other programmers...


10-09-2003, 03:07 PM
I've used PDFLib (www.pdflib.com), a commercial ASP component that'll generate PDF's on the fly. It's not that cheap (I think about Ģ600 per server license but I might be wrong) but it works well enough. I found it quite a learning curve - the manual is extensive, and you quickly realise the complexity of managing colours, fonts, resolutions, bleed and all the other features of print-quality PDF.

10-09-2003, 05:14 PM
Thanks Spudhead, I have checked your suggestion and as you mention is a bit pricey...it is full of features though...
I have been recommended by a friend the following component: http://www.edcomponents.com
It is only $75 and I was playing with the trial version last night.
It seems to be what I need.
I will use it to create an invoice on the fly, so I really donīt need all the nice features related to image handling, etc.

10-09-2003, 07:26 PM
If you have the opportunity to use .NET, check out this open source project: http://sourceforge.net/projects/pdflibrary/ (sourceforge.net)

It works really well. Reviewing the code will also help gain a better understanding of how exactly PDFs are generated...

10-09-2003, 09:25 PM
Thanks khillabolt,
I do not know .Net yet it is something I have to start thinking to move to...
I have found plenty of pdf resources for .NET, so the move has to come soon...

10-14-2003, 02:39 AM
I'm with you guys there. I have already programmed windows applications using .NET, and it is fairly easy (and fun!).

The hard part comes with hacking the bad client-side code that .NET generates when it comes to web apps - and making it compliant (and able to work cross-browser).


I will have some solutions in that regard in the not-too-distant future hopefully though, using C# (IMHO the cleanest "Microsoft" language - which isn't surprising since it's basically an attempt to copy Java). :D