Using Your Aspose License

Your Conholdate purchase is made up of both Aspose and GroupDocs APIs. You will receive one license file which will work with the APIs from both websites. Both Aspose and GroupDocs are made up of various products and you will need to apply the license for each product.

 

Aspose のライセンスの使用方法

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

注記:

1. Aspose.Total を .NET、Java、Android、SharePoint、Reporting Services、または JasperReports 用に購入した場合、ライセンス ファイルはそれぞれの .NET、Java、Android、SharePoint、Reporting Services、JasperReports 製品すべてで機能します。
2. ライセンスは下位互換性がありませんのでご注意ください。

 

ライセンス クラスの競合

Each Aspose product includes a License class. If you use more than one Aspose 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 Aspose.Words.License and for Java use com.aspose.words.License.

ライセンス ファイルの保護

If you have purchased an OEM license you may distribute Aspose 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.
 

 

GroupDocs のライセンスの使用方法

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

注記:

1. GroupDocs.Total を .NET または Java 用に購入した場合、ライセンス ファイルはそれぞれの .NET または Java 製品すべてで機能します。
2. ライセンスは下位互換性がありませんのでご注意ください。
    

ライセンス ファイルの保護

If you have purchased an OEM license you may distribute Aspose 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.