Analyzing your prompt, please hold on...
An error occurred while retrieving the results. Please refresh the page and try again.
What is this page about?
This page describes installation steps for Aspose.Words.
Make sure your machine meets the system requirements before you begin.
This article explains how to install Aspose.Words for .NET on your computer.
NuGet is the easiest way to download and install Aspose.Words for .NET APIs. To do this, follow these steps:

The selected API will be downloaded and referenced in your project.
You can also update Aspose.Words for .NET to the desired version using Manage NuGet Packages.
You can also install or update Aspose.Words for .NET APIs using the Package Manager Console. To do this, follow these steps:

Install-Package Aspose.Words and press Enter to install the latest full release into your application
-prerelease suffix to the command to specify that the latest release, including hotfixes, should also be installed.


In Package Manager Console, you can also use the Update-Package Aspose.Words command to check for updates to the Aspose.Words package and install them if present. You can also add the -prerelease suffix to update the latest release.
Aspose.Words for .NET can be installed by direct downloading the MSI installer from the downloads section.
To Install Aspose.Words for .NET, follow these steps:
Aspose.Words_{LatestVersion}.msi from the downloads section


All Aspose .NET components are recommended to run with the Full Trust permission set. This is because Aspose .NET component sometimes needs access to registry settings and files located in places other than the virtual directory, such as reading fonts. Furthermore, Aspose.NET components are based on core .NET system classes, some of which also require Full Trust permission to run in some cases.
Internet Service Providers hosting multiple applications from different companies mostly enforce Medium Trust security level. In the case of .NET 2.0, such a security level may impose the following constraints, which may affect the ability of Aspose.Words to perform properly:
For these reasons specified above, it is recommended to run Aspose.Words with Full Trust permissions. You may find that some of library features will work when performing different tasks with Medium trust, and some will not, for example, rendering. This can be related to GDI+ image processing calls.
Q: How do I apply my Aspose.Words license after installing the library?
A: Add the license file (e.g., Aspose.Words.lic) to your project and load it at runtime with License license = new License(); license.SetLicense("Aspose.Words.lic");. This should be done before any Aspose.Words API calls to ensure the evaluation mode is disabled.
Q: Are licenses from newer Aspose.Words versions compatible with older library versions?
A: Yes. Aspose licenses are generally backward compatible; a license generated for a newer version works with older versions of Aspose.Words. However, features introduced after the older version will not be available.
Q: Do I need to reinstall the license when I update Aspose.Words via NuGet?
A: No. The license file is part of your application, not the NuGet package. After updating the package, keep the same license file in your project and continue loading it as before.
Q: Why does Aspose.Words require Full Trust, and can I run it under Medium Trust?
A: Full Trust is needed for operations that access the registry (font enumeration) and the file system outside the application folder. Under Medium Trust, some features—especially rendering to images or PDFs—may fail. If you must use Medium Trust, limit operations to those that do not require external resources.
Q: What should I do if the installer does not add the assemblies to the GAC or Visual Studio reference list?
A: Manually add a reference to the installed DLLs (e.g., Aspose.Words.dll) by right‑clicking the project → Add Reference → Browse to the installation folder. Ensure the target framework of your project matches the DLL version.
Analyzing your prompt, please hold on...
An error occurred while retrieving the results. Please refresh the page and try again.