Skip to main content
dotnet-htmlpackager package icon

dotnet-htmlpackager

HtmlPackager is a small console .NET SDK tools used to package HTML content into a self contained HTML document either as a single file or console output stream, a folder with all dependencies copied to local or a zip file. It provides a automated way to perform a similar task to what Browser **Save As...** does to capture page output to disk. The packager can create: * A single, self-contained and very large HTML file with all resources embedded inline * A single output stream into StdOut that contains self contained HTML output as above * An HTML file with all resources copied local into the same folder as the document * A zip file of the latter output This package is for the .NET SDK tooling, there are also packages for Chocolatey (HtmlPackager) as a standalone Console Windows exe, and a Nuget .NET Standard Library package (westwind.htmlpackager) for the underlying API.

Total Downloads
8.9K
8,862
Published
Oct 19, 2024
Latest stable version

Install

.NET CLI
dotnet add package dotnet-htmlpackager --version 0.2.5
Package Manager Console
Install-Package dotnet-htmlpackager -Version 0.2.5
PackageReference
<PackageReference Include="dotnet-htmlpackager" Version="0.2.5" />

Frameworks

No framework metadata available.

Dependencies

No declared dependencies.

Adoption guide

Assess this package against its supported frameworks, license, maintenance signals and dependency graph before making it a project standard.

No SPDX license expression is published. Review the license text and your organisation's policy before redistribution.

No target framework metadata is available. Confirm compatibility in a representative project before standardising on this package.

How to read this guidance

Sources: published NuGet v3 registry metadata and explicit NuBrowse editorial guides. Refresh: package metadata is refreshed from NuGet when the page loads. Limit: this is not a security, legal or compatibility guarantee; validate the selected version in your project.

Useful next steps

Move from package metadata to a concrete selection or review workflow.