#TuesPechkin TuesPechkin is a .NET Wrapper for the wkhtmltopdf library. This is AnyCPU fork of TuesPechkin
- It supports .NET 2.0+, 32 and 64-bit processes, and IIS-hosted applications.
- Azure Websites does not currently support the use of wkhtmltopdf.
- It is not tested with any operating systems besides Windows.
- It is available as a NuGet package for your convenience.
- It is built and tested around wkhtmltopdf 0.12.4.
- Even if you use the IIS-compatible method documented below, you may only use one converter/toolset instance per application pool/process. A workaround is being researched for a future version.
The wkhtmltox.dll file and any dependencies it might have (for older versions, 0.11.0-) are not included in the TuesPechkin NuGet package; however, you can bring your own copy of the library or download one of the following NuGet packages that contain the library:
- TuesPechkin.Wkhtmltox.Win32
- TuesPechkin.Wkhtmltox.Win64
- TuesPechkin.Wkhtmltox.AnyCPU
You must have Visual C++ 2013 runtime installed to use these packages. Otherwise, you will need to download the MingW build of wkhtmltopdf and its dependencies from their website and use that with the library.
If something doesn't seem right with your converted document, try converting with wkhtmltopdf directly. If you still have the problem, then you will need to take your issue to wkhtmltopdf's issues. Any issues related to visual problems like this will be closed unless the reporter can show that the problem is unique to this library.
Please follow similar guidelines as StackOverflow -- that is, provide any contextual information that you can about your application to help solve the issue.
For 2.0.0 I am wanting to use the 'git flow' style of branching/merging/releasing. If you have a hotfix, please branch off of hotfix. If you are adding something, please branch off of develop. I won't fully re-explain the methodology here.
The API drastically changed once more for 2.0.0 for the sake of modularity and extensibility. Please read the following sections thoroughly.
TuesPechkin exposes an 'IDeployment' interface to represent the folder where wkhtmltox.dll resides. These are the officially supported implementations:
EmbeddedDeployment
- this is an abstract class with two official implementations: theWin32EmbeddedDeployment
andWin64EmbeddedDeployment
classes, available from NuGet in their own packages. It contains the wkhtmltopdf file(s) and requires anotherIDeployment
instance to tell it where to create the file(s). This is the recommended and easiest deployment to get started with.TempFolderDeployment
- this one generates a temp folder based on the base directory of your application, as well as whether you are running in 32 or 64 bit. Recommended for use with any of theEmbeddedDeployment
implementations.StaticDeployment
- use this one if you really know what you are doing with TuesPechkin and wkhtmltox.dll. It accepts a string path that you define.
TuesPechkin exposes an IToolset
interface to represent a set of functions from the wkhtmltopdf library. There are three officially supported implementations:
PdfToolset
- Exposes operations from wkhtmltox.dll to convert HTML into PDFImageToolset
- Exposes operations from wkhtmltox.dll to convert HTML into imagesRemotingToolset<TToolset>
- Manages a toolset of typeTToolset
across an AppDomain boundary. This is necessary for use in IIS-hosted applications.
There is also an abstract class from which you may inherit: NestingToolset
. It provides wrapping functionality that is used by RemotingToolset<TToolset>
.
TuesPechkin exposes an IConverter
interface. An implementation of IConverter
properly makes all of the calls to wkhtmltopdf to convert an IDocument
instance (which we will cover shortly.) TuesPechkin supplies two implementations:
StandardConverter
- A converter that may be used in single-threaded applicationsThreadSafeConverter
- A converter that manages a single background thread and queues document conversions against it. This is necessary for use in multi-threaded applications, including IIS-hosted applications.
TuesPechkin exposes three interfaces and one attribute that define an HTML document. These are:
WkhtmltoxSettingAttribute
: an attribute for properties that instructs anIConverter
to apply the property's value to the wkhtmltopdf global or object setting with the name passed to the attribute's constructor.ISettings
: a token interface whose implementors are implied to have properties decorated withWkhtmltoxSettingAttribute
and/or otherISettings
properties.IObject
: an interface that represents a wkhtmltopdf 'ObjectSettings'. It requires one method to be implemented:byte[] GetData()
. AllIObject
instances are alsoISettings
instances by inheritance.IDocument
: an interface that represents an HTML document. It requires one method to be implemented:IEnumerable<IObject> GetObjects()
. AllIDocument
instances are alsoISettings
instances by inheritance.
Because TuesPechkin exposes these interfaces/attributes, you are free to write your own implementations that support whichever wkhtmltopdf settings you so desire. If TuesPechkin's included HtmlDocument
class and its related classes do not provide support for a setting you want to use, you may then extend them or create your own classes altogether -- this also goes for use cases where you are only setting a handful of properties and you find the included implementations to be too verbose.
The included HtmlToPdfDocument
class and its related classes do not supply any default values to wkhtmltopdf.
Here is how an IDocument
is to be processed by an IConverter
:
- A wkhtmltopdf 'GlobalSettings' is created for the document.
- The
IDocument
is recursively crawled for allISettings
andWkhtmltoxSettingAttribute
-decorated properties; these properties are applied to the 'GlobalSettings'. - 'GetObjects()' is called on 'IDocument', and for each 'IObject' that is not null, a wkhtmltopdf 'ObjectSettings' is created and that 'IObject' is recursively crawled for all
ISettings
andWkhtmltoxSettingAttribute
-decorated properties; these properties are applied to the 'ObjectSettings'. The 'ObjectSettings' is then added to the converter.
var document = new HtmlToPdfDocument
{
GlobalSettings =
{
ProduceOutline = true,
DocumentTitle = "Pretty Websites",
PaperSize = PaperKind.A4, // Implicit conversion to PechkinPaperSize
Margins =
{
All = 1.375,
Unit = Unit.Centimeters
}
},
Objects = {
new ObjectSettings { HtmlText = "<h1>Pretty Websites</h1><p>This might take a bit to convert!</p>" },
new ObjectSettings { PageUrl = "www.google.com" },
new ObjectSettings { PageUrl = "www.microsoft.com" },
new ObjectSettings { PageUrl = "www.github.com" }
}
};
IConverter converter =
new StandardConverter(
new PdfToolset(
new WinAnyCPUEmbeddedDeployment(
new TempFolderDeployment())));
byte[] result = converter.Convert(document);
IConverter converter =
new ThreadSafeConverter(
new PdfToolset(
new Win32EmbeddedDeployment(
new TempFolderDeployment())));
// Keep the converter somewhere static, or as a singleton instance!
// Do NOT run the above code more than once in the application lifecycle!
byte[] result = converter.Convert(document);
IConverter converter =
new ThreadSafeConverter(
new RemotingToolset<PdfToolset>(
new WinAnyCPUEmbeddedDeployment(
new TempFolderDeployment())));
// Keep the converter somewhere static, or as a singleton instance!
// Do NOT run the above code more than once in the application lifecycle!
byte[] result = converter.Convert(document);
This work, "TuesPechkin", is a fork of "TuesPechkin" by tuespetre (Derek Gray.) used under the Creative Commons Attribution 3.0 license. This work is made available under the terms of the Creative Commons Attribution 3.0 license (viewable at http://creativecommons.org/licenses/by/3.0/) by cratu (Dmitry Shumkin)