Installation

Documentize SDK can be installed through multiple methods, each tailored to different development environments and preferences. Below are the recommended ways to install Documentize:

1. NuGet (Preferred Method)

NuGet is the most straightforward and preferred method for installing Documentize, ensuring that you always have the latest version and updates directly within your development environment. Check more details about this installation method at How to install Documentize SDKs using NuGet.

2. MSI Installer

The MSI installer is a convenient option if you prefer to have the Documentize DLLs installed directly onto your system. This method is ideal for developers who may want to use Documentize across multiple projects without needing to manually manage DLL files. Check more details about this installation method at How to install Documentize SDKs using MSI.

3. ZIP Archive

For developers who prefer a manual approach, the ZIP archive contains the Documentize DLLs, which can be extracted and added to your project directly. Check more details about this installation method at How to install Documentize SDKs using ZIP.

Sep 13, 2024

Subsections of Installation

System Requirements

Documentize SDKs are designed to integrate with .NET applications and support various operating systems and development environments. Below are the key system requirements:

Supported Operating Systems

Windows

  • Windows 7 (x64, x86)
  • Windows 8, 8.1 (x64, x86)
  • Windows 10 (x64, x86)
  • Windows 11 (x64, x86)
  • Windows Server 2003 to Windows Server 2022 (x64, x86)
  • Cloud: Microsoft Azure

macOS

  • macOS 10.12 (Sierra) and later

Linux

  • Compatible with multiple Linux distributions:
    • Ubuntu (16.04, 18.04, 20.04, 22.04)
    • CentOS (7, 8)
    • Debian (9, 10)
    • OpenSUSE (Leap 15+, SLES 12+)

Android

  • Supports Android 8.0 (Oreo) and later.

Development Environments

  • Microsoft Visual Studio:
    • Visual Studio 2010 and later (including 2019 and 2022)
  • Supports any development environment targeting .NET platforms.

Supported .NET Frameworks

  • .NET Framework 4.0 and higher
  • .NET Standard 2.0 (.NET Core 3.1+)
  • .NET 6.0, .NET 7.0, .NET 8.0

Additional Notes

  • Adobe Acrobat is not required to run Documentize SDKs, but is recommended for viewing PDFs.
Sep 12, 2024

Declaration

Documentize.com SDKs require a Full Trust permission set when used within .NET applications. This permission level is essential for the SDKs to perform certain system-level operations, such as accessing registry settings, system files, and parsing fonts.

Why Full Trust is Required

The Documentize SDKs utilize core .NET system classes, which often need elevated permissions for the following reasons:

  • Registry Access: Some operations may require reading or writing to the system registry.
  • System Files: Access to system files beyond the application’s virtual directory may be necessary for certain tasks, such as handling fonts or performing file operations.

Limitations of Medium Trust Environment

In hosting environments that enforce Medium Trust security, several important permissions are restricted or unavailable. This could prevent the SDKs from functioning correctly in such environments. The following restrictions apply under Medium Trust:

  • OleDbPermission: Cannot use the ADO.NET managed OLE DB data provider to access databases.
  • EventLogPermission: Access to the Windows Event Log is prohibited.
  • ReflectionPermission: Prevents the use of reflection, which may affect certain dynamic operations.
  • RegistryPermission: Access to the system registry is denied.
  • WebPermission: Communication is restricted to predefined addresses or ranges as configured in the <trust> element.
  • FileIOPermission: Access to files is limited to those within the application’s virtual directory.
Apr 1, 2025

Non-Windows Environment

Documentize SDKs support .NET Standard 2.0, which allows them to be used in .NET Core applications running on Linux or other non-Windows environments. To ensure optimal performance and correct text rendering, follow the steps below:

1. Install libgdiplus Package

This package provides necessary GDI+ functionality, which is critical for rendering and processing PDFs. You can install it by running the following command in your terminal:

sudo apt-get install libgdiplus

2. Install Microsoft Compatible Fonts

For correct text rendering, install Microsoft TrueType fonts using the command:

sudo apt-get install ttf-mscorefonts-installer

These fonts should be placed in the /usr/share/fonts/truetype/msttcorefonts directory. If your system stores fonts in a different directory, update the path in your code before performing any operations with Documentize SDKs:

Documentize.Text.FontRepository.Sources.Add(new FolderFontSource("<path to ms fonts>"));

Tip

By ensuring these installations are complete and configuring the font path correctly, you can maximize the performance of Documentize SDKs on Linux or other non-Windows systems.

Apr 1, 2025

License and Evaluation

Evaluate Documentize for .NET

When you start working with Documentize products, you can use them immediately with a free evaluation license. This license allows developers and businesses to explore, test, and integrate Documentize features into their applications before making a purchase.

What Is an Evaluation License?

The evaluation license is a built-in, time-unlimited trial mode included in every Documentize product. It gives you access to most of the core features so you can fully evaluate the product’s capabilities in real-world scenarios. Whether you’re generating, editing, or converting documents, you can test performance and integration with your stack.

Key Features of the Evaluation License

  • No installation needed – Just download and start using Documentize products.
  • 🧪 Explore core functionality – Test essential features like document conversion, manipulation, and export.
  • 💻 Developer-friendly – Ideal for proof-of-concept (POC), integration testing, or technical evaluations.
  • 🔁 Easy to upgrade – Switch to a full license at any time without changing your implementation.

If you want to upgrade to a full license, you need add a next code:

License.Set("path_to_your_license_file.lic");

Limitations of the Evaluation Mode

While evaluation licenses offer broad access, there are a few limitations designed to protect the licensed product:

  • All pages in the generated PDF documents are watermarked.
  • In the evaluation version, you can only process the first four pages of a document.
  • Evaluation licenses are not intended for production or commercial deployment.

For full access without restrictions, you’ll need to purchase a valid Documentize license and apply it within your project.

How to Start Using the Evaluation License

No special setup is required. Simply download your desired Documentize SDK, and begin working with it. If no license file is applied, the product automatically runs in evaluation mode.

To test behavior with a valid license, you can also request a temporary full-featured license for in-depth evaluations.

When to Use the Evaluation License

You should use an evaluation license if:

  • You’re exploring Documentize capabilities for the first time.
  • You want to confirm compatibility with your application or platform.
  • You need to build a prototype or proof-of-concept before buying.
  • You’re comparing document automation solutions.

Get Started with Documentize Today

Evaluate Documentize products risk-free and see how they can enhance your document workflows. When you’re ready to move to production, upgrading to a full license is fast and seamless.

📘 Need Help? Visit our Documentation or Contact Us for assistance.

 English