Further research identified a number of. Three libraries in particular iTextSharp, PdfSharp and MigraDoc stood out from this group as being the most complete, feature-rich and well documented options. Although my research probably wouldn't have counted as commercial development, I was sufficiently motivated to experiment with PdfSharp and Migradoc first, which are released under the MIT license free for any use.
In doing so I established that these two libraries were very well written, easy to use and very well documented. The objective of this post is thus to publicise my experience with these libraries and to encourage their use by other developers requiring PDF export functionality. The key difference between PdfSharp and Migradoc is the level of control available to the developer. In PdfSharp you are responsible for controlling every aspect of the rendering process which is done by drawing lines, strings and shapes at specified coordinates on a PDF graphics context.
The only drawback with PdfSharp is that it requires the developer to do a lot of work. For some applications the level of control required by the developer will necessitate the use of this library, but for other occasions, the MigraDoc library is here to help. Migradoc provides a domain model for document generation and allows you to construct a document using sections, paragraphs and tables, etc. This library vastly simplifies document generation by automating many of the rendering tasks, with the obvious limitation of reduced rendering control.
For simple documents this may not be a problem, but can be an issue if more complex output is required. For example, my experimentation with Migradoc found that the edges of a wide table were truncated if the columns did not fit onto a single page. I thus implemented a more sophisticated rendering mechanism loosely based on the algorithms found in DGVPrinter , which separates a table's columns onto multiple pages. The most appropriate library to use is thus very much dependent on the task at hand.
If you are performing simple PDF rendering Migradoc may well suit your needs. However, for those more complex situations the lower-level PdfSharp library is always available. Because the two libraries are so closely related you can also render a single document by using a combination of both libraries, although I did encounter some limitations with this to be discussed later. The availability of documentation was a considerable factor in deciding to experiment with PdfSharp and Migradoc. The numerous examples available on the support website provide an excellent developer resource when combined with the extensive sample applications bundled with the libraries.
In my opinion the same cannot be said of iTextSharp, which largely relies on the Java-based iText documentation and a commercially published book. Furthermore, because Migradoc is built upon PdfSharp this is another excellent source for examples.
In this section I will briefly illustrate how a PDF document is generated using PdfSharp and Migradoc, highlighting both the overall simplicity and some of the differences between the two approaches.
PdfSharp utilises a PdfDocument object, to which we add and render individual pages. In the example below I create a new document and set some of the available document information properties before adding a single A4 page.
I then proceed by obtaining an XGraphics object and render to it using low-level methods. In the example I draw two strings of text in roughly the centre of the page using a specified font. I then draw two horizontal lines above and below the text, save the document and display it to the user. As can be seen, one of the drawbacks of PdfSharp is that features such as text-wrapping are not implemented. To achieve text wrapping one must manually measure the lengths of strings and wrap the text accordingly.
Furthermore, the current document y position must also be tracked as rendering is performed. In this simple example tracking the y position is trivial, although rendering does become slightly more challenging when more complex rendering is performed e.
Re-generating the above document in Migradoc is useful for demonstrating both the pros and cons of each library. Unlike PdfSharp, Migradoc uses a Document object to which document elements e. The document is rendered using a PdfDocumentRenderer. However, complications arise when one tries to do anything out of the ordinary. Similarly, there is no way to position the table in a specific location i.
However, Migradoc does perform text-wrapping for us, which is clearly beneficial when rendering large amounts of text.
One can clearly see that the best library to use will depend on the output you wish to produce. However, do keep in mind that mixing both libraries is also possible see the PdfSharp Samples project or here for an example.
Correspondingly, part of my investigation focused on the printing aspects of PdfSharp, for which I identified two options. This approach is particularly neat and simple, as demonstrated by the following example:. Yes, create a shortcut to the ps1-file. Then, change it's path to.
Thanks a lot, I'm rather new to this PS and all, and still trying to get my basics working, how do i make it parse the directory and loop til all the files without extensions are handled, and is it possible to put the PS in the dir, and just doubleclick it?
I tried this script and I could see that it was making PDFs with the same name as the files, which is what I want. Unfortunately, it printed single blank pages. Please open a new topic with your issue and a copy of your script. This topic is closed and answered. Office Office Exchange Server.
Not an IT pro? Internet Explorer TechCenter. Sign in. United States English. As far as the resolution of the images, they are full size. For some reason the designer insists on creating the document at half size. JasonSpr, are you saying that enlarging at the rip, even though the images would be dpi, would yield satisfactory results? Last edited: Sep 1, JasonSpr said:. An example: if your images are 3x3, dpi, stored in the pdf at 1.
Wouldn't it have to be stored in the PDF at 1. Yes turn off any downsampling or optimization during the normalization. This way the file will be used at max resolution for the images before the scale. Good luck p. You must log in or register to reply here. Similar threads A. Replies 2 Views Oct 9, anfrmite. Replies 6 Views Oct 1, Ashok Taneja. File Recovery Service is in High Demand.
0コメント