Licensing and evaluation Leave feedback

To study the system, you may want quick access to the API. To make this easier, GroupDocs.Merger provides different plans for purchase and offers a Free Trial and a 30-day Temporary License for evaluation.

Note

Note that there are a number of general policies and practices that guide you on how to evaluate, properly license, and purchase our products. You can find them in the Purchase Policies and FAQ section.

After buying, apply the license file or include it as an embedded resource.

License needs to be set:

• Only once per application domain
• Before using any other GroupDocs.Merger classes

Licenses can be applied from different locations:

• Explicit path
• The folder containing the GroupDocs.Merger.dll file
• The folder containing the assembly that called GroupDocs.Merger.dll
• The folder containing the entry assembly (your .exe)
• As a Metered License that allows you to pay for your usage. For details, see the Metered Licensing FAQ.

When you reference GroupDocs.Merger.dll in the application, the library is copied to your output directory (unless Copy Local in the properties for that entry is set to false). The easiest way to set a license is often to place the license file in the same folder as GroupDocs.Merger.dll and specify just the filename without the path.

Use the setLicense method to license a component.

Calling setLicense multiple times is not harmful, it simply wastes processor time.

Calling setMeteredKey multiple times is not harmful either but wastes processor time and can accumulate consumption improperly.

After obtaining the license, set it. This section explains how to do this. When developing your application, call the setLicense method in your startup code before using the GroupDocs.Merger classes.

The following code snippet shows how to set a license from file:

const licensePath = "path to the .lic file";
const license = new groupdocs.merger.License()
license.setLicense(licensePath); 

The following code snippet shows how to set a license from a stream:

const fs = require('fs')  
  
const licensePath = "path to the .lic file"
const license = new groupdocs.merger.License()
const licStream = fs.createReadStream(licensePath)
groupdocs.conversion.License.setLicenseFromStream(license, licStream, err => {
  if (err) {
    console.log(`Set license error: ${err}`)
  } else {
    console.log('License set OK')
  }
})

You do not have to name the license file “GroupDocs.Merger.lic”. Feel free to rename it as you prefer, and use that name when setting the license in your application.

When you buy and download a license from the GroupDocs website, the license file is named “GroupDocs.Merger.lic.” Download it using your browser. Sometimes, browsers recognize it as XML and add the .xml extension, making the full file name “GroupDocs.Merger.lic.XML” on your computer.

If Microsoft Windows is set to hide file extensions (which is the default in most installations), the license file will show as “GroupDocs.Merger.lic” in Windows Explorer. You might assume this is the actual file name and call the setLicense method with “GroupDocs.Merger.lic”, but there is no such file, leading to an exception.

To fix this issue, rename the file to remove the hidden .xml extension. Additionally, we suggest disabling the “Hide extensions” option in Microsoft Windows.

You can also try GroupDocs.Merger without buying a license.

The evaluation version is identical to the purchased one; it becomes licensed once you set the license. You can set the license using methods described in the following sections of this article.

The evaluation version has the following limitations:

• Rendering is limited to the first 2 pages.
• Trial badges are added to the top of a rendered page.

If you want to test GroupDocs.Merger without the limitations of the trial version, request a 30-day Temporary License. For details, see the “Get a Temporary License” page.