Skip to main content

How to Specify PDF Builder for Output

We offer three different means of generating PDF output through our engines: our internal Fluent PDF renderer, Microsoft Office PDF and PdfTron. We use our internal PDF render by default. Here are the instructions on how to specify which PDF builder you want to use for output.

.NET Engine​

If you use the .NET RESTful engine, you can specify your desired PDF builder in the Web.config file. To do so set these properties:

<WindwardReports>
 <add key="use.external.output.builder" value="on" />  
 <add key="output.builder" value="net.windward.env.PDFTronOutputBuilder" /> 
</WindwardReports>
  • For Microsoft Office PDF builder, you will need to supply the path to the "OfficeOutputBuilder.dll" file in the bin folder of your engine:
<WindwardReports>
 <add key="use.external.output.builder" value="on" />  
 <add key="output.builder" value="{Path_To_OfficeOutputBuilder.dll};OfficeOutputBuilder.WindwardOutputBuilder"/>
</WindwardReports>
note

Make sure to include the name of the dll in the {Path_To_OfficeOutputBuilder.dll}

Troubleshooting​

If you run into issues with targeting a 32-bit (x86) application where your application throws the error:

Could not load file or assembly ‘PDFNet'...

You may need to setup a binding redirect in the web.config file for your .NET application.

To do this, in your web.config file of your application, you will need to add this section:

<dependentAssembly>
  <assemblyIdentity name="PDFNet" publicKeyToken="45663c462b939c60" culture="neutral" />
  <bindingRedirect oldVersion="0.0.0.0-11.9.8.6415" newVersion="11.9.8.6415" />
</dependentAssembly>

Where the newVersion and the range of oldVersion contains the latest version used of the PDFNet library.

Additional Information​

Additional information about the PDFNet library for .NET can be found here.

Additional information about the PDFNet library and targeting different CPU architectures in .NET can be found here.