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 include the license file as an embedded resource. This section describes options of how this can be done, and also comments on some common questions.

License Applying Options

Licenses can be applied from various locations:

  • Explicit path
  • The folder containing the Aspose.Words.dll file
  • The folder containing the assembly that called Aspose.Words.dll
  • The folder containing the entry assembly (your .exe)
  • An embedded resource in the assembly is called Aspose.Words.dll
  • As a Metered License – a new licensing mechanism

When you reference Aspose.Words.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). Often the easiest way to set a license is to place the license file in the same folder as Aspose.Words.dll and specify just the filename without the path.

Apply License Using a File or Stream Object

The table below shows examples of options for calling SetLicense, depending on the type of your project.

Project Type SetLicense Calling
Windows Forms or Сonsole application Call SetLicense in your startup code before using Aspose.Words classes
ASP.NET application Call SetLicense from the Global.asax.cs (Global.asax.vb) file, in the protected Application_Start method. It is called once when the application starts.
Do not call SetLicense from the Page_Load methods since it means that the license will be applied every time a web page is loaded.
Class library Call SetLicense from the static constructor of your class that uses Aspose.Words.
The static constructor will be executed before an instance of your class is created to make sure that Aspose.Words license is properly set.
Load a License from a File

Using the SetLicense 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 SetLicense method:

Include the License File as an Embedded Resource

A neat way to package a license with your application and make sure it will not be lost is to include it as an embedded resource into one of the assemblies that call Aspose.Words. To include a file as an embedded resource, follow these steps:

  1. In Visual Studio, include the .lic file into the project using the “File | Add Existing Item…” menu.
  2. Select the file in the Solution Explorer and set “Build Action to Embedded Resource” in the Properties window.
  3. In your code, invoke SetLicense that passes only the short name of the resource file.

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.

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.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.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.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. LIC” in Windows Explorer. You will probably think that this is the real file name and call SetLicense passing it “Aspose.Words.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 SetLicense 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.