Licensing and Subscription

Sometimes, in order to study the system better, you want to dive into the code as fast as possible. To make this easier, Aspose.Words provides different plans for purchase or offers a Free Trial and a 30-day Temporary License for evaluation.

Free Trial or Temporary License

Aspose.Words is incredible software that developers can try before purchasing.

Free Trial

The evaluation version is the same as the purchased one – the trial version simply becomes licensed when you add a few lines of code to apply the license.

The Trial version of Aspose.Words without the specified license provides full product functionality, but inserts an evaluative watermark at the top of the document upon loading and saving and limits the maximum document size to a few hundred paragraphs.

Temporary License

If you wish to test Aspose.Words without the limitations of the Trial version, you can also request a 30-day Temporary License. For more details, see the Get a Temporary License page.

Purchased License

After purchase, you need to apply the license file or stream. This section describes options of how this can be done, and also comments on some common questions.

Protecting Your Purchased License

After purchasing a license, you need to carefully read the information on page Protecting Your Purchased License to protect your license file. Please note that this page is available for viewing only if you have a paid license.

License Applying Options

Licenses can be applied from various locations:

  • Explicit path
  • The folder containing the python script that calls Aspose.Words for Python via .NET
  • Stream
  • As a Metered License – a new licensing mechanism

Apply License Using a File or Stream Object

When developing your application, call set_license in your startup code before using Aspose.Words classes.

Load a License from a File

Using the set_license method, you can try to find the license file in the embedded resources or assembly folders for further use.

The following code example shows how to initialize a license from a folder:

Load a License from a Stream Object

The following code example shows how to initialize a license from a stream using another set_license method:

Apply Metered License

Aspose.Words allows developers to apply a metered key. This is a new licensing mechanism.

The new licensing mechanism will be used along with the existing licensing method. Those customers who want to be billed based on the use of API features can use the Metered Licensing.

After completing all the necessary steps to obtain this type of license, you will receive the keys, not the license file. This metered key can be applied using the Metered class specially introduced for this purpose.

Do not call the SetMeteredKey method frequently so that this licensing method properly accumulates consumption and reports it to us. Just instantiate the Aspose.Words library, call SetMeteredKey once, then leave the library instantiated and reuse it.

The following code example shows how to set metered public and private keys:

Changing the License File Name

The license filename does not have to be “Aspose.Words.Python.NET.lic”. You can rename it to your liking and use that name when setting a license in your application.

“Cannot find license filename” Exception

When you purchase and download a license, the Aspose website names the license file “Aspose.Words.Python.NET.lic”. You download the license file using your browser. In this case, some browsers recognize the license file as XML and append the .xml extension to it, so the full file name on your computer becomes “Aspose.Words.Python.NET.lic.XML”.

When Microsoft Windows is configured to hide extensions for known file types (unfortunately, this is the default in most Windows installations), the license file will appear as “Aspose.Words.Python.NET.lic” in Windows Explorer. You will probably think that this is the real file name and call set_license passing it “Aspose.Words.Python.NET.lic”, but there is no such file, hence the exception.

To solve the problem, rename the file to remove the invisible .xml extension. We also recommend you disable the “hide extensions” option in Microsoft Windows.

Using Multiple Aspose Products

If you use multiple Aspose products in your application, such as Aspose.Words and Aspose.Cells, here are a few useful tips:

  • Set the License for each Aspose product separately. Even if you have a single license file for all components, for example, “Aspose.Total.lic”, you still need to call set_license separately for each Aspose product that you use in your application.
  • Use the Fully Qualified License Class Name. Each Aspose product has a License class in its own namespace. For example, Aspose.Words has aspose.words.License and Aspose.Cells has aspose.cells.License class. Using the fully qualified class name allows you to avoid confusion as to which license applies to which product.