What is the difference between TallPDF.NET and PDFKit.NET?
TallPDF.NET allows you to define the content as sections and paragraphs after which it will flow the content into pages. PDFKit.NET on the other hand, requires you to place content at exact location at page objects. In other words, TallPDF.NET has a flow layout model and PDFKit.NET has a canvas layout model.
I open the type reference (.chm) but each page seems to be missing?
By default XP SP2 does not trust a .chm that originates from the internet. Right-click the help file, select 'Properties' and click the 'Unblock' button on the 'General' tab.
Can PDFKit.NET 3.0 be used on a shared web server where I am not allowed to do any machine level configuration?
Yes, PDFKit.NET 3.0 is verifiable (or 100% managed). This means that to use PDFKit.NET in your ASP.NET application, you only have to copy the assembly to the bin folder of your virtual folder.
I am now using PDFKit.NET 2.0 and want to upgrade to 3.0. Is 3.0 fully backwards compatible?
No, in order to make the object model more consistent and introduce new functionality, we had to break backwards compatibility. The evaluation download includes a developer guide which has a chapter that discusses upgrading in detail.
Is it possible to create high resolution PDF's, such as 300 or even 600 dpi?
All text and curves in a PDF are vector-based so resolution does not apply to these types of graphics. Resolution does apply to embedded images though. The effective resolution of an embedded image follows directly from its physical width and height (these are set by the client application) and the resolution of the image itself (this is a given). For example, say you have a 300 x 400 bitmap and you add this to a PDF using the ImageShape. If you then set the width and height of this image to 75 x 100 points, then the effective resolution of the image is ( 300 / 75 ) * 72 = 288 DPI.
Is PDFKit.NET 3.0 Vista, Windows 7 and Windows Server 2008 compliant?
Yes, fully.