References ▼
Files for redistribution are installed by the LEADTOOLS setup. For more information on the installation directory structure, refer to Installation Directory.
Note: You may not copy or redistribute any of the following files without obtaining the proper license. In some cases, the license is included with your initial purchase of LEADTOOLS. In other cases, you must obtain a license from a third party or enter into a royalty agreement with LEAD to obtain the proper license. For these special licensing situations, see the notes below accompanying the specific file.
Note: You may not distribute the header files with your application, and you may not provide software development capabilities in your application.
Leadtools.dll is required for ALL .NET Class Library applications.
Note:
LEADTOOLS binaries for .NET 4.0 require the Microsoft Visual C++ 2017 Runtime.
The Microsoft Visual C++ 2017 Redistributable Package cannot be installed on some versions of Windows.
For supported versions, see Choosing a Deployment Method and Update for Universal C Runtime in Windows .
The Microsoft Visual C++ 2017 Runtime also requires the Windows Universal CRT library, which is distributed as part of Windows 10.
For information on how to redistribute the universal CRT, see Introducing the Universal CRT.
Note: The file names are the same for Win32 and x64. However, the actual binaries are different. For more information about distributing the Microsoft C/C++ runtime files, refer to: https://docs.microsoft.com/en-us/visualstudio/productinfo/2017-redistribution-vs.
The following table summarizes the files you must include with your distribution. Most files in the table are optional. These files are referred to as "Redistributables" in the License Agreement.
For information about runtime licenses, refer to About LEADTOOLS Deployment Licenses.
For information about the "nag" message and runtime licenses, refer to LEADTOOLS Nag Message.
Files to be Included with your Java Application
Make the DLLs in the LEADTOOLS Library available to your application in one of two ways:
The following redistributables are grouped together because each member contributes a separate portion of the support needed for that functionality.
| File Format Support | There are two categories of file format support: |
|---|---|
| OCR Support |
Before copying or redistributing any of the files for OCR functionality, you must first enter into a Royalty Agreement with LEAD. Contact the OEM Department. For details, refer to OCR Files to be Included with Your Application. |
| Annotations Support |
For a list of files required to support Annotations, click here. |
| Barcode Support |
Note: Before copying or redistributing any of the files for Barcode functionality, you must first enter into a Deployment License Agreement with LEAD. For more information, contact licensing@leadtools.com. For a list of files required to support Barcodes, click here. |
| Distributed Computing (Job Processor) Support |
Note: Before copying or redistributing any of the files for Barcode functionality, you must first enter into a Deployment License Agreement with LEAD. For more information, contact licensing@leadtools.com. For more information about deploying LEADTOOLS Distributed Computing (Job Processor), refer to Deploying LEADTOOLS Distributed Computing Applications. For a list of files required for Distributed Computing (Job Processor) support, click here. |
| Documents Support |
For a list of files required to support Documents functionality, click here. |
| Forms Support |
For a list of files required to support Forms functionality, click here. |
| PDF Support |
For a list of files required to support PDF functionality, click here. |
| Image Processing Support |
For a list of files required to support Image Processing functionality, click here. |
| JPIP Support |
For a list of files required to support JPIP functionality, click here. |
| DICOM Support |
For a list of files required to support DICOM, click here. |
| PACS Framework Data Access Layer and Rules Add-in Support |
For a list of files required to support the PACS Framework Data Access Layer and Rules add-in, click here. |
| 3D Medical Support |
For a list of files required to support server-side Medical 3D (3D Web Viewer), click here. For a list of files required to support Medical 3D, click here. |
| Medical Workstation Support |
For a list of files required to support Medical Workstation functionality, click here. |
| Clinical Context Object Workgroup (CCOW) Support |
For a list of files required to support Clinical Context Object Workgroup (CCOW) functionality, click here. |
| Windows Media Support |
For a list of files required to support Windows Media functionality, click here. |
| Demo DLLs Support |
For a list of the Demo DLLS required to support the examples, click here. |
Choosing which draw engine to use in an application depends, in part, on which platforms the application is targeted for deployment:
If an application will be deployed exclusively to Windows platforms, use DrawEngineType.DefaultEngine. It is based on Windows GDI/GDI+ and produces the fastest rendering.
If an application will be deployed to both Windows and non-Windows platforms (such as Linux, Android, macOS, iOS, and Universal Windows Platform (UWP)), use DrawEngineType.MultiplatformEngine. This ensures identical rendering across all platforms.
For more information, refer to LEADTOOLS Draw Engine and Multi-Platform Considerations and RasterImage and GDI/GDI+.
LEADTOOLS provides .NET developers with NuGet packages support as an additional means for obtaining the latest LEADTOOLS toolkit binaries. For details on the available selection, refer to the following resources:
LEADTOOLS NuGet Packages - NuGet packages available for download.
LEADTOOLS NuGet Packages Dependency Tree - Dependency graph of the LEADTOOLS NuGet packages.
Does your application require document recognition or conversion, but its implementation language is preventing you from using LEADTOOLS directly? Consider using the LEADTOOLS Cloud Services Web API instead. It is a high-powered and scalable Web API. Its hassle-free interface can be used to integrate advanced OCR, barcode, MICR, and document conversion into any application.
| Application-Specific Redistributable | Explanation |
|---|---|
| Leadtools.AddIn.BrokerHost |
PACS Framework Server add-in that hosts the LEADTOOLS Modality Worklist WCF service. Also requires Leadtools, Leadtools.Dicom, Leadtools.Dicom.AddIn, Leadtools.Dicom.Common, Leadtools.Dicom.Scu, Leadtools.Logging, and Leadtools.Medical.Worklist.Wcf. |
| Leadtools.Caching |
Caching support - used by the Document Library. |
| Leadtools.Codecs |
Required for reading and writing image files. See below for information on individual codec DLLs. XMP metadata functions also require Leadtools.Codecs.Xmp. |
| Leadtools.CloudServices |
Required for implementing high-level recognition, conversion, file verification, and image processing functionality. |
| Leadtools.ColorConversion |
Required for Colorspace conversion and some file formats. |
| Leadtools.Controls.WinForms |
WinForms implementation of Leadtools.Controls. Required for displaying images in Windows Forms applications. Provides support for zooming, panning, scrolling, etc. |
| Leadtools.Controls.Wpf |
WPF implementation of Leadtools.Controls. Required by Leadtools.Controls for WPF. Contains the ImageViewer control class. |
| Leadtools.Converters |
Required for loading/saving image and non-image data to the multiple image file formats supported by LEADTOOLS |
| Leadtools.CreditCards |
Required for scanning credit cards. Also requires Leadtools and Leadtools.Forms.Recognition |
| Leadtools.Drawing | Provides support for painting/drawing to a device, painting on the surface of a LEADTOOLS image, image conversion, region conversion, etc. |
|
Required for Image Optimization functionality. |
|
| Leadtools.Jpeg2000 | Required for applications that include JPEG 2000 JPX support. |
| Leadtools.Logging (PACS) | Required for implementing logging in your applications. |
| Leadtools.Logging.Medical (PACS) | Provides medical-specific extensions to the logging framework. Also requires Leadtools.Logging and Leadtools.Dicom. |
| Leadtools.Mrc | Required for LEAD MRC segmentation functionality and advanced PDF compression functionality. Also requires one or more file format codecs. |
| Leadtools.MediaWriter |
Required to burn DVD and ISO images to a DVD disk. It contains classes for the MediaWriter objects needed to create and burn disc images. It is included in the LEADTOOLS DVD Module. Also requires DSKERNEL2 for Win32 and DSKERNEL2x for x64. |
| Leadtools.Medical.DataAccessLayer (PACS) | Required for implementing customizable Data Access objects that work with any data store. |
| Leadtools.Medical.ExternalStore.DataAccessLayer (PACS) | Contains interfaces and classes for storing, querying, and updating general External Store information. |
| Leadtools.MedicalViewer | Contains the Leadtools.MedicalViewer control class. Also requires the Leadtools.Medical3D. |
| Leadtools.Medical.Media.DataAccessLayer (PACS) | Contains interfaces and classes for storing, querying, and updating DICOM Media Creation Managements IOD. |
| Leadtools.Medical.Logging.DataAccessLayer (PACS) | Required to store and access PACS Servers and client's event logs. |
| Leadtools.Medical.Storage.DataAccessLayer (PACS) | Required to store, query and update general DICOM Composite Instances. |
| Leadtools.Medical.Worklist.Wcf (PACS) | Provides the WCF services that interact with modality worklist databases. Also requires Leadtools, Leadtools.Dicom, Leadtools.Dicom.AddIn, Leadtools.Dicom.Common, Leadtools.Logging, Leadtools.Medical.DataAccessLayer, Leadtools.Medical.Worklist.DataAccessLayer |
| Leadtools.Medical3D | Support DLL for Leadtools.MedicalViewer. |
| Leadtools.Medical3D.Client | Support for server-side medical 3D volume rendering. |
| Leadtools.Medical.HL7 | Required for creating, parsing, and exchanging messages related to electronic health documents. |
| Leadtools.Printer | Required for Virtual Printer Driver functionality. Also requires the LEADTOOLS Virtual Printer Driver Engine Redistributable Files. |
| Leadtools.Printer.Client | Required for Virtual Printer Driver network printing functionality. Also requires the LEADTOOLS Virtual Printer Driver Engine Redistributable Files. |
| Leadtools.Printer.Client.Installer | Required for Virtual Printer Driver network printing functionality. Also requires the LEADTOOLS Virtual Printer Driver Engine Redistributable Files. |
| Leadtools.ScreenCapture | Required for Screen Capture functionality. |
| Leadtools.Services.Twain (WCF) | Provides a set of web services from controlling TWAIN devices. Also requires Leadtools, Leadtools.Codecs, and Leadtools.Twain. |
| Leadtools.SharePoint.Client |
Required for supporting client access to Microsoft SharePoint server. Also requires the Microsoft SharePoint Foundation 2010 Client Object Model Redistributable (Microsoft.SharePoint.Client and Microsoft.SharePoint.Client.Runtime). |
| Leadtools.SpecialEffects | Required for display effects and transitions. |
| Leadtools.Svg | Required to add vector load, edit, save, conversion, and display functionality to applications. |
| Leadtools.Twain | Required for TWAIN scanning functionality. |
| Leadtools.UserMapping.Agent | A sample assembly that implements a user mapping agent for the CCOW toolkit. |
| Leadtools.Vector | Required for supporting vector file formats. |
| Leadtools.Web | Required for WebForms applications. Some controls require that LEADTOOLS codec DLLs are available to your application. For more information, refer to Leadtools.Web.Controls.BrowserImageFormat. |
| Leadtools.Wia | Required for WIA scanning functionality. |
| Leadtools.WinForms.CommonDialogs.File | Required for File Open and File Save common dialogs. Also requires LEADTOOLS file format codecs. |
| Leadtools.WinForms.CommonDialogs.Color | Required for common dialogs that provide imaging-specific capabilitiews. Also requires LEADTOOLS file format codecs. |
| Application-Specific Redistributable | Explanation |
|---|---|
| Leadtools.AddIn.Router |
(Deprecated) Use the LEADTOOLS Rules add-in instead, which is a more powerful and flexible alternative. Adds DICOM routing functionality to a PACS Framework server. |
| Leadtools.AddIn.StoreProxy | (Deprecated) Use the LEADTOOLS Rules add-in instead, which offers a more powerful and flexible alternative. Provides a storage proxy for an existing DICOM Server. This makes it possible to use the PACS Framework routing ability, but use a different DICOM server implementation. |
| Leadtools.Windows.Controls | (Deprecated) Use Leadtools.Controls.Wpf instead. |