.NET open PDF in winform without external dependencies


Is there a FREE library which will allow me to open a pdf and show it on a winform project. I know I could open it in adobe reader or something but it always seems so bloated to me and I would be relying on it being installed. Is there a nice lightweight alternative where I could just include a dll in my project or similar avoiding external dependencies.

I don't need much functionality just view, change page zoom..

I have seen a few libraries but they seem to be about creating PDF's not viewing.

2/14/2009 6:29:08 PM

Accepted Answer

The ActiveX control installed with acrobat reader should work, either drop it in via the designer or use something like this.

This will require the relevant version of the reader is installed on the client but since you indicate that you could just launch that anyway this should not be a problem. reader

2/14/2009 8:30:01 PM

I'm not sure what you call a 'dependency' since you'll always have to rely on some external code to render the PDF unless you bundle the whole PDF rendering source inside your project.

There are some commercial renderers and very few free ones.

If you want to avoid dependencies that you can't bundle then maybe you could have a look at the source code for SumatraPDF, an OpenSource PDF viewer for windows that uses MuPDF.
There is also Poppler, a rendering engine that uses Xpdf as a rendering engine. All of these are great but they will require a fair amount of commitment to make make them work and interface with .Net.

Most other open source libraries are only used for creating and managing PDF pages and I don't know any that actually does rendering; it's such a hard problem to solve right.

You may still want to consider using GhostScript as an interpreter because rendering pages is a fairly simple process.
The drawback is that you will need to either re-package it to install it with your app, or make it a pre-requisite (or at least a part of your install process).
It's not a big challenge, and it's certainly easier than having to massage the other rendering engines into .Net.

Have a look at this SO question I answered today.
It contains some more information and a link to some working .Net code I posted on another forum a few months ago.

Licensed under: CC-BY-SA with attribution
Not affiliated with: Stack Overflow