Skip to main content
Westwind.HtmlPackager package icon

Westwind.HtmlPackager

HtmlPackager is a small library 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 an automated, programmatic 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 Standard 2.0 library, there are also packages for Chocolatey (HtmlPackager) as a standalone Windows exe, and a cross platform .NET SDK Tool(dotnet-htmlpackager).

Total Downloads
10.1K
10,094
Published
Nov 6, 2018
Latest stable version

Install

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

Frameworks

.NETFramework4.5 .NETStandard2.0

Dependencies

HtmlAgilityPack
.NETFramework4.5
[1.8.9, )
HtmlAgilityPack
.NETStandard2.0
[1.8.9, )

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.

Compatibility metadata lists 2 target frameworks; confirm the exact target used by your application.

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.