Adobe® PDF Library

Required Components, .NET Core

The .NET Core interface requires its native Windows dependencies when deploying to Windows, its native Linux dependencies when deploying to Linux, and its native macOS dependencies when deploying to macOS.

DLL files

All library files located in \Binaries are required.

DL180PDFL.dll PDF Library primary DLL file
DL180ACE.dll Adobe Color Engine
DL180AdobeXMP.dll XMP metadata
DL180AGM.dll Adobe Graphics Manager printing engine
DL180ARE.dll Adobe Raster Express
DL180AXE8SharedExpat.dll XML processing
DL180BIB.dll Bravo interface binder
DL180BIBUtils.dll Bravo interface binder utilities
DL180CoolType.dll CoolType Typography Engine
DL180JP2K.dll JPEG2000 Library
icuuc*.dll International Components for Unicode
icudt*.dll International Components for Unicode

.NET Core

For .NET Core, dependencies include:

  • Datalogics.PDFL.dll
  • The Microsoft Visual Studio 2017 C++ Runtime .dll files

On Windows systems, copy the .dll files from the Microsoft.VC141.CRT subdirectories into the executable directory. It is important to use the runtime libraries supplied with the specific distribution to ensure the correct version will be found.

The .NET Core interface depends on these Microsoft runtime libraries on Windows only.  You need to copy these files to the same folder where you copy Datalogics.PDFL.dll.


There are three plug-ins with supporting DLL files:

DL180XPS2PDF.ppi XPS to PDF conversion
DL180PDFlattener.ppi transparency flattener
DL180PDFProcessor.ppi PDF/A and PDF/X conversions
DL180pdfport.dll Plug-in dependency
DL180pdfsettings.dll Settings for plug-ins

For Linux or macOS the DLL and plug-in files will have similar names, but may begin with lib and end with .so, .framework, or .dylib.

Optical Character Recognition (OCR) processing

The .NET Core interface for the Adobe PDF Library provides an Optical Character Recognition (OCR) utility that can recognize images in a PDF document. The OCR utility recognizes text within each image, and then saves that text to a new PDF export file, with that text underlaying the image where it was found.

The Adobe PDF Library uses a software product called the Tesseract 3 OCR Engine. The tessdata directory holds the language files to support OCR processing to identify text in images in PDF documents. The default languages offered include English, Dutch, French, German, Italian, Spanish, Portuguese, Mandarin, Japanese, and Korean.

Note that the OCR engine in Adobe PDF Library is only compatible with the Windows 64 and Linux 64 platforms for the Java and .NET interface. For .NET Core, the OCR engine is supported in 64 bit for Windows, Linux, and macOS.

The OCR engine library is stored in the DotNETCore/Binaries directory:

dltesseract3.dll Windows Linux
libdltesseract3.dylib macOS

Two sample programs show how to use OCR processing, AddTextToImage and AddTextToDocument. These samples are found in the /OpticalCharacterRecognition folder.


The files found in the folders under Resources are used for a variety of operations, including creating/setting text and extracting or parsing content. Most of these are font files. Datalogics recommends that you include all of the resources in the \Resources tree with your distribution. If, however, you need to limit the total size of the files included in your application, some of the components in the \Resources folder can be removed.

  • Font. This folder includes CJK fonts. These are Multi-byte (16 bit) character fields mostly used by Chinese, Japanese, and Korean characters (CJK). Thus a CJK character is twice as wide as a normal single-byte character space. The double byte character field is needed because these languages have so many characters that a single 8 bit character field is not enough to represent all of them, but the font files that result tend to be larger than typical fonts. You can leave these files out of your distribution package if you will not be processing documents with CJK content.
  • CMap . Some fonts in PDF files use predefined mappings between character encodings and specific, predefined character identifier sets. These mappings are called Character Maps (CMaps), and we recommend that they all be included with your distribution, even though they can be quite large.
  • Joboptions. Joboption files are used only by the standard plug-ins provided with the Library. You can leave them out of your distribution if your applications will not be using the plug-ins.
  • Color. This is used for rendering, printing, and conversion operations, as well as the XPS2PDF plugin.
  • Unicode. Used for text extraction and for text conversion during printing, rendering, and conversion operations. We recommend that all Unicode font files be included. Unicode is an international font standard.
  • tessdata. This folder contains training data for applications that use the OCR engine. It can be removed if OCR is not used.

The .NET Core interface will look for the Resources folder under the primary deployment folder. The Font, CMap, Color, and Unicode path names can be specified during the Library initialization.