Evaluation Limitations and Licensing of GroupDocs.Signature
Evaluation Limitations and Licensing of GroupDocs.Signature
Leave feedback
Note
You can use GroupDocs.Signature without the license. The usage and functionalities are pretty much same as the licensed one but you will face few limitations while using the non-licensed API.
Evaluation Limitations
You can easily download GroupDocs.Signature for evaluation. The evaluation download is the same as the purchased download. The evaluation version simply becomes licensed when you add a few lines of code to apply the license. You will face following limitations while using the API without the license:
Only first 2 pages are processed.
Trial badges are placed in the document on the top of each page.
Licensing
The license file contains details such as the product name, number of developers it is licensed to, subscription expiry date and so on. It contains the digital signature, so don’t modify the file. Even inadvertent addition of an extra line break into the file will invalidate it. You need to set a license before utilizing GroupDocs.Signature API if you want to avoid its evaluation limitations.
The license can be loaded from a file or stream object. The easiest way to set a license is to put the license file in the same folder as the GroupDocs.Signature.dll file and specify the file name, without a path, as shown in the examples below.
Setting License from File
The code below will explain how to set product license.
// For complete examples and data files, please go to https://github.com/groupdocs-Signature/GroupDocs.Signature-for-.NET// Setup license.Licenselicense=newLicense();license.SetLicense(licensePath);
Setting License from Stream
The following example shows how to load a license from a stream.
// For complete examples and data files, please go to https://github.com/groupdocs-Signature/GroupDocs.Signature-for-.NETusing(FileStreamfileStream=File.OpenRead("GroupDocs.Signature.lic")){Licenselicense=newLicense();license.SetLicense(fileStream);}
Note
Calling License.SetLicense multiple times is not harmful but simply wastes processor time. If you are developing a Windows Forms or console application, call License.SetLicense in your startup code, before using GroupDocs.Signature classes.
When developing an ASP.NET application, you can call License.SetLicense from the Global.asax.cs (Global.asax.vb) file in the Application_Start protected method. It is called once when the application starts. Do not call License.SetLicense from within Page_Load methods since it means the license will be loaded every time a web page is loaded.
Setting Metered License
Note
You can also set Metered license as an alternative to license file. It is a new licensing mechanism that will be used along with existing licensing method. It is useful for the customers who want to be billed based on the usage of the API features. For more details, please refer to Metered Licensing FAQ section.
Here are the simple steps to use the Metered class.
Create an instance of Metered class.
Pass public & private keys to SetMeteredKey method.
Do processing (perform task).
Call method GetConsumptionQuantity of the Metered class.
It will return the amount/quantity of API requests that you have consumed so far.
Call method GetConsumptionCredit of the Metered class.
It will return the credit that you have consumed so far.
Following is the sample code demonstrating how to use Metered class.
// For complete examples and data files, please go to https://github.com/groupdocs-Signature/GroupDocs.Signature-for-.NETstringpublicKey="";// Your public license keystringprivateKey="";// Your private license keyMeteredmetered=newMetered();metered.SetMeteredKey(publicKey,privateKey);// Get amount (MB) consumeddecimalamountConsumed=GroupDocs.Signature.Metered.GetConsumptionQuantity();Console.WriteLine("Amount (MB) consumed: "+amountConsumed);// Get count of credits consumeddecimalcreditsConsumed=GroupDocs.Signature.Metered.GetConsumptionCredit();Console.WriteLine("Credits consumed: "+creditsConsumed);
Was this page helpful?
Any additional feedback you'd like to share with us?
Please tell us how we can improve this page.
Thank you for your feedback!
We value your opinion. Your feedback will help us improve our documentation.