iTextSharp is a C# port of iText, and open source Java library for PDF generation and manipulation. It can be used to create PDF documents from scratch, to convert XML to PDF (using the extra XFA Worker DLL), to fill out interactive PDF forms, to stamp new content on existing PDF documents, to split and merge existing PDF documents, and much more.
Several iText engineers are actively supporting the project on the iText mailing-list firstname.lastname@example.org and on StackOverflow: http://stackoverflow.com/questions/tagged/itextsharp
- PDF generation
- PDF manipulation (stamping watermarks, merging/splitting PDFs,...)
- PDF form filling
- XML functionality
- Digital signatures
This is open source in the same way that a patent troll is an inventor. Put very very simply, if you intend to use the libray be prepared to have to open source your own project, or pay an undisclosed sum. This is not in the spirit of the AGPL, questionably legal at best, and dogy in that a packaged fully endorsed compiled binary is downloadable from this site without an included license file. I will be reporting this project as inappropriate content for SourceForge based on the following text taken from the iText website: "Although iText is a free/open source software (F/OSS) project, giving you a lot of freedom and flexibility regarding the use of the iText software, this doesn’t mean you're free to do anything you want with the product: you have to respect the Affero General Public License. You can be released from the requirements of the license by purchasing a commercial license from iText Software Corp. Buying such a license is mandatory as soon as you develop commercial activities distributing the iText software inside your product or deploying it on a network without disclosing the source code of your own applications under the AGPL license. These activities include: offering paid services to customers as an ASP, serving PDFs on the fly in the cloud or in a web application, shipping iText with a closed source product."
Worst library ever!!! I would save more time and frustration if this library was never created. Instead of wasting time trying to figure out why the API is not doing what its name suggested(), time would be spend on create own API. Stay away from this crap if you have the choice.
Licence was changes and is now much, much more restrictive. Stick with v4; if you want a commercial product consider Prince (which is much easier to use) instead.