This developer guide will help you understand the PDFKit.NET 4.0 class library. It walks through the main concepts and illustrates them with code samples. This guide is not a type reference. Instead, this is included in the evaluation download.
PDFKit.NET is a 100% managed (verifiable) .NET class library for creating and manipulating PDF documents. It consists of just a single assembly that can be xcopy-deployed. It has no dependencies other than the .NET framework. Central to PDFKit.NET is a consistent and highly intuitive object model consisting of classes like Document, PageCollection, Page, Canvas, Shape, Bookmark, Annotation, Field, etc. The focus of the development team is always to ease the task of integrating our class libray in a larger application. These are PDFKit.NET’s primary features:
Fill and flatten PDF forms
Split and assemble PDF documents
Apply security settings such as passwords
Stamp content on new and existing pages
Support for CMYK and Grayscale colorspace
Read, Create and Modify Actions, Sticky Notes and Links
Adobe LiveCycle Designer compatibility (static forms only)
Extract and search text
Digitally signing and verification
Native .NET 2.0 support, including 64-bit support
What’s new in 4.0?
The following features have been added in 4.0:
We added a WPF-only build without a reference to System.Drawing
We added support for QR barcodes.
The ImageShape now supports loading of JBIG2 images.
.NET 1.1 is no longer supported
Code Samples in this Guide
All non—trivial code samples are available as ready-to-run Visual Studio .NET projects. These samples are included in the installation package which can be downloaded from our web site.
Just unzip to any folder and open codesample.sln in either Visual Studio.NET 2003 or 2005 (will convert first). Each code sample is available as a separate project inside this solution. If the code sample is part of the solution, the name of the corresponding project is included in the caption line of the code sample.
Upgrading from PDFKit.NET 3.0
PDFKit.NET 4.0 is fully backwards compatible. Simply replace the assembly and recompile.
Please send us Feedback!
Please help us improve this document. If you have any questions, suggestions or find anything in this document is incorrect or missing then let us know at email@example.com.
We try to adhere as much as possible to Microsoft’s “Design Guidelines for Developing Class Libraries”. The guideline can be found here: