Analyzing your prompt, please hold on...
An error occurred while retrieving the results. Please refresh the page and try again.
Install Aspose.HTML for .NET when your C# application needs to create, load, edit, parse, save, or convert HTML-related documents. The recommended installation method is NuGet, because it keeps package references and dependencies inside your project file.
For most .NET projects, install Aspose.HTML with NuGet. Use dotnet add package Aspose.HTML from the command line, Install-Package Aspose.HTML in Visual Studio Package Manager Console, or the NuGet Package Manager GUI.
NuGet is the preferred way to add Aspose.HTML for .NET to a C# project. It records the package reference in the project, restores dependencies automatically, and makes package updates easier.
Use .NET CLI when you work from a terminal, automate project setup, or manage SDK-style projects.
1dotnet add package Aspose.HTMLTo update the package reference later, run the same command again or specify an exact version:
1dotnet add package Aspose.HTML --version <version>Without --version, the command resolves the latest available package version from the configured NuGet sources and updates the project reference.
Use Package Manager Console when you work inside Visual Studio and prefer NuGet commands.
1Install-Package Aspose.HTMLTo include prerelease builds when they are available, add the -Prerelease option:
1Install-Package Aspose.HTML -PrereleaseTo update an existing package reference, use:
1Update-Package Aspose.HTMLTo install Aspose.HTML for .NET from the Visual Studio NuGet UI:
Aspose.HTML.Aspose.HTML package.Use MSI or direct DLL references only when NuGet is not available in your environment, for example in restricted build systems or legacy projects. NuGet remains the safer default for most new .NET applications.
To install with MSI or DLL references:
Aspose.Html resolve correctly.| Issue | Cause | Fix |
|---|---|---|
dotnet add package Aspose.HTML cannot find the package | The project uses a private NuGet source, offline feed, or a NuGet configuration that does not include nuget.org. | Check configured package sources and make sure the feed that contains Aspose.HTML is available to the project or CI environment. |
The namespace Aspose.Html is not resolved | The package was not installed into the selected project, restore did not complete, or the wrong project is active in Visual Studio. | Install the package into the target project, run package restore, rebuild the solution, and check that the project file contains the package reference. |
| An older package version remains after update | The project or solution may pin an exact package version, use a lock file, or restore from a cached source. | Check the package version in the project file, update the reference explicitly, clear or refresh package caches if needed, and restore again. |
| Installation succeeds but rendering output differs on Linux or Docker | The package is installed, but the runtime image may not include fonts or native dependencies required for rendering. | Review System Requirements and configure Linux or Docker dependencies before testing rendering workflows. |
NuGet is recommended for most projects. It records the Aspose.HTML package reference in the project file, restores dependencies automatically, and makes updates easier than manual DLL references.
Yes. Use dotnet add package Aspose.HTML for SDK-style projects or Install-Package Aspose.HTML in the Visual Studio Package Manager Console.
Use MSI or direct DLL references only when NuGet is unavailable, for example in restricted build environments or legacy projects that cannot restore packages normally.
Use dotnet add package Aspose.HTML --version <version> from the command line, or select the required version in the NuGet Package Manager UI.
For basic document loading and conversion workflows, the package reference is the main installation step. For Linux, macOS, Docker, or hosted server deployments, also check runtime dependencies, fonts, permissions, and supported frameworks in System Requirements.
Analyzing your prompt, please hold on...
An error occurred while retrieving the results. Please refresh the page and try again.