Analyzing your prompt, please hold on...
An error occurred while retrieving the results. Please refresh the page and try again.
System Requirements
Contents
[
Hide
Show
]Aspose.HTML for .NET is a standalone C# library for opening, analyzing, editing, creating, and converting HTML, XHTML, SVG, MHTML, Markdown, and EPUB documents. It does not require Microsoft Office, Adobe Acrobat, a browser UI, or third-party conversion tools to be installed on the target machine.
This page lists the operating systems, .NET frameworks, development environments, and permission requirements supported by Aspose.HTML for .NET.
Supported Operating Systems
Aspose.HTML for .NET can run on 64-bit and 32-bit operating systems where a supported .NET Framework, .NET Core, or modern .NET runtime is installed, including but not limited to the versions listed below.
| Operating system | Supported versions |
|---|---|
| Microsoft Windows | Microsoft Windows Server 2022 (x64) Microsoft Windows 2019 Server (x64) Microsoft Windows 2016 Server (x64) Microsoft Windows Server 2012 R2 (x64) Microsoft Windows Server 2012, 64-bit edition (x64) Microsoft Windows Server 2008 R2 SP1 (x64) Microsoft Windows Server 2008 SP2 (x64, x86) Microsoft Windows 11 (x64) Microsoft Windows 10 (x64, x86) Microsoft Windows 8.1 (x64, x86) Microsoft Windows 8 (x64, x86) Microsoft Windows 7 SP1 (x64, x86) Microsoft Azure |
In order to use Aspose.HTML for .NET on Linux or macOS, install .NET Core 2.1 or later.
.NET Core 2.1 is supported on the following distributions and versions:
| Operating system | Supported versions |
|---|---|
| macOS | Sierra 10.12+ (x64) |
| Linux | Red Hat Enterprise Linux 6, 7, 8 (x64) CentOS 7+ (x64) Oracle Linux 7+ (x64) Fedora 30+ (x64) Debian 9 (x64) Ubuntu 16.04, 18.04, 19.04, 19.10 (x64) Linux Mint 17+ (x64) openSUSE 15+ (x64) SUSE Enterprise Linux (SLES) 12 SP2+ (x64) Alpine Linux 3.8+ (x64) |
Depending on your Linux distribution or macOS version, and because Aspose.HTML for .NET uses the System.Drawing.Common assembly, you may need to install additional native dependencies. The full list of supported distributions and required dependencies is available in Microsoft documentation for .NET on Linux and .NET on macOS.
For containerized Linux deployments, see Run Aspose.HTML in Docker.
Supported Frameworks
Aspose.HTML for .NET provides assemblies compiled for the following framework:
| Framework specification |
|---|
| .NET Standard 2.0 |
Therefore, Aspose.HTML for .NET is compatible with the following .NET Framework, .NET Standard, .NET Core, and modern .NET versions:
| .NET Framework | .NET Standard | .NET Core | .NET |
|---|---|---|---|
| .NET Framework 4.6.1 | .NET Standard 2.0 | .NET Core 2.0 | .NET 5.0 |
| .NET Framework 4.6.2 | .NET Standard 2.1 | .NET Core 2.1 | .NET 6.0 |
| .NET Framework 4.6.3 | .NET Core 2.2 | .NET 8.0 | |
| .NET Framework 4.7 | .NET Core 3.0 | .NET 9.0 | |
| .NET Framework 4.7.1 | .NET Core 3.1 | .NET 10.0 | |
| .NET Framework 4.7.2 | |||
| .NET Framework 4.8 | |||
| .NET Framework 4.8.1 |
Some Microsoft libraries used by Aspose.HTML for .NET no longer support legacy frameworks. If a project targets an unsupported or legacy framework, a build warning or error can appear. You can handle this in one of the following ways:
- Update the project to a newer supported framework.
- Suppress target framework support build warnings by adding the following property to the project file:
1<PropertyGroup>
2 <SuppressTfmSupportBuildWarnings>true</SuppressTfmSupportBuildWarnings>
3</PropertyGroup>If you suppress this warning, some library features may not work correctly on the legacy target framework.
Development Environments
You can use Aspose.HTML for .NET to develop applications in any development environment that targets the .NET platform. The following environments are explicitly supported:
| Development environment |
|---|
| Microsoft Visual Studio 2005 |
| Microsoft Visual Studio 2008 |
| Microsoft Visual Studio 2010 |
| Microsoft Visual Studio 2011 |
| Microsoft Visual Studio 2012 |
| Microsoft Visual Studio 2013 |
| Microsoft Visual Studio 2015 |
| Microsoft Visual Studio 2017 |
| Microsoft Visual Studio 2019 |
| Microsoft Visual Studio 2022 |
| Visual Studio Code with C# tooling |
| JetBrains Rider |
| .NET CLI |
For installation options, see Install Aspose.HTML for .NET.
Trust Level
Generally, all Aspose .NET components require Full Trust permissions set. The reason is that Aspose .NET components need to access registry settings, system files other than the virtual directory, and other resources for certain operations, such as reading fonts. Moreover, Aspose .NET components, including Aspose.HTML for .NET, are based on core .NET system classes that also require Full Trust permissions set in many cases.
Internet service providers hosting multiple applications from different companies often enforce a Medium Trust security level. Such a security level may set the following constraints, which can affect the ability of Aspose.HTML for .NET to perform properly:
| Permission | Medium Trust constraint |
|---|---|
| RegistryPermission | Registry access is not available. |
| WebPermission | The application can communicate only with an address or range of addresses defined in the <trust> element. |
| FileIOPermission | The application can access only files in the application’s virtual directory hierarchy. |
Due to the reasons specified above, it is recommended that Aspose.HTML for .NET is run on servers granting Full Trust permissions.
Common System Requirement Issues
| Issue | Cause | Fix |
|---|---|---|
| Build warning for a legacy target framework | Some Microsoft libraries used by Aspose.HTML for .NET no longer support older target frameworks. | Update the project to a newer supported framework. Suppress the warning only when you understand that some features may not work correctly. |
| Application works on Windows but rendering differs on Linux | Linux and minimal Docker images may not include fonts, fontconfig, globalization data, or native graphics dependencies. | Install the required fonts and native packages in the runtime environment. For Docker, configure the runtime stage of the image. |
| Text is missing in converted PDF or image output on Linux | No usable TrueType/OpenType fonts are installed, or the configured custom font folder does not contain the required fonts. | Install fonts under the system font directory or configure a complete custom font folder. Rebuild the font cache when fonts are installed during image build. |
| Remote CSS, images, or fonts are not loaded | The runtime environment restricts network access, certificates, or allowed URLs. | Allow access to required remote resources, install CA certificates, or package resources locally with the input document. |
| Conversion fails in shared hosting or older ASP.NET hosting | Medium Trust can restrict registry, file I/O, and network permissions required by .NET APIs and rendering workflows. | Use Full Trust or an equivalent permission model that allows the application to access files, fonts, temporary paths, and network resources required by the workflow. |
FAQ
Do I need Microsoft Office, Adobe Acrobat, or a browser installed?
No. Aspose.HTML for .NET is a standalone library and does not require Microsoft Office, Adobe Acrobat, a browser UI, or third-party conversion tools for supported document processing and conversion workflows.
Which .NET version should I choose for a new project?
For new development, choose a currently supported .NET version whenever possible. Aspose.HTML for .NET provides a .NET Standard 2.0 assembly, so the practical choice depends on your application lifecycle, deployment target, and Microsoft support policy for the runtime you use.
Can Aspose.HTML for .NET run on Linux and macOS?
Yes. Install .NET Core 2.1 or later and make sure the operating system has any native dependencies required by your rendering workflow, especially fonts and graphics-related packages.
What should I check before running Aspose.HTML in Docker?
Use a .NET runtime or SDK image that matches your target framework, install fonts and fontconfig, configure UTF-8/globalization support, install CA certificates if remote resources are loaded, and make sure dependencies are installed in the runtime stage of the Dockerfile.
Is Full Trust required?
Full Trust is recommended for server-side use. Medium Trust can block registry access, file access outside the virtual directory, or network access, which may affect loading resources, reading fonts, and saving converted output.
Next Steps
- Installation – install Aspose.HTML with NuGet, .NET CLI, Package Manager Console, DLL references, or MSI.
- Licensing – apply a license or request a temporary license before production testing.
- How to Run the Examples – download and run C# examples from GitHub.
- Run Aspose.HTML in Docker – configure Linux container dependencies for rendering workflows.