Using Your GroupDocs License

To find out how to apply a license, follow the appropriate link below.

Note: If you have bought GroupDocs.Total for .NET, Java, Node.js or Python then your license file will work with all .NET, Java, Node.js or Python products respectively.
 

License Class Conflict

Each GroupDocs product includes a License class. If you use more than one GroupDocs product in the same solution then you may get a naming conflict. To fix it, please specify the fully qualified name of the class when you use License.SetLicense method. For example, for .NET use GroupDocs.Conversion.License and for Java use com.groupdocs.conversion.License.

Protecting your License File

If you have purchased an OEM license you may distribute GroupDocs in your application to customers. This means the license file will be included with your application which poses a potential security risk that someone could find the license and copy or leak it to others. Embedding the license as an internal resource protects it to a degree, but the original file can still be retrieved from the deployment package. To protect your license file more securely you need to use encryption.

Once you have paid for a license file you will be able to access instructions to encrypt your license. Note you will be unable to access this page without a paid order.