PhoenixmlDb.Xslt 1.6.2

.NET 8.0 This package targets .NET 8.0. The package is compatible with this framework or higher.
There is a newer version of this package available.
See the version list below for details. 
dotnet add package PhoenixmlDb.Xslt --version 1.6.2
                    


                    

                
NuGet\Install-Package PhoenixmlDb.Xslt -Version 1.6.2
This command is intended to be used within the Package Manager Console in Visual Studio, as it uses the NuGet module's version of Install-Package. 
<PackageReference Include="PhoenixmlDb.Xslt" Version="1.6.2" />
For projects that support PackageReference, copy this XML node into the project file to reference the package. 
<PackageVersion Include="PhoenixmlDb.Xslt" Version="1.6.2" />
                    


                            Directory.Packages.props
                        

                    

                
<PackageReference Include="PhoenixmlDb.Xslt" />
                    


                            Project file
For projects that support Central Package Management (CPM), copy this XML node into the solution Directory.Packages.props file to version the package. 
paket add PhoenixmlDb.Xslt --version 1.6.2
                    


                    

                
#r "nuget: PhoenixmlDb.Xslt, 1.6.2"
#r directive can be used in F# Interactive and Polyglot Notebooks. Copy this into the interactive tool or source code of the script to reference the package. 
#:package PhoenixmlDb.Xslt@1.6.2
#:package directive can be used in C# file-based apps starting in .NET 10 preview 4. Copy this into a .cs file before any lines of code to reference the package. 
#addin nuget:?package=PhoenixmlDb.Xslt&version=1.6.2
                    


                            Install as a Cake Addin
                        

                    

                
#tool nuget:?package=PhoenixmlDb.Xslt&version=1.6.2
                    


                            Install as a Cake Tool

PhoenixmlDb.Xslt

XSLT 4.0 transformation engine for PhoenixmlDb — transform XML documents into HTML, JSON, CSV, text, or other XML formats.

Features

  • XSLT 3.0/4.0 — template matching, streaming, accumulators, packages, maps/arrays
  • All output methods — HTML5, XML, XHTML, JSON, text, CSV, adaptive
  • Multiple outputs — xsl:result-document for multi-file generation
  • Full XPath 4.0 — 240+ built-in functions available in all expressions
  • Packages — reusable stylesheet libraries with visibility control

Quick example

using PhoenixmlDb.Xslt;

var transformer = new XsltTransformer();
await transformer.LoadStylesheetAsync(
    File.ReadAllText("style.xsl"),
    new Uri(Path.GetFullPath("style.xsl")));

transformer.SetParameter("title", "My Report");
var html = await transformer.TransformAsync(
    File.ReadAllText("data.xml"));

// Handle secondary outputs (xsl:result-document)
foreach (var (href, content) in transformer.SecondaryResultDocuments)
    File.WriteAllText(Path.Combine(outputDir, href), content);

See the full API overview in the README.

Package Description
PhoenixmlDb.Core Core types and XDM data model (dependency)
PhoenixmlDb.XQuery XQuery 4.0 query engine (dependency)
PhoenixmlDb.Xslt.Cli xslt command-line tool

Documentation

Full documentation at phoenixml.dev

License

Apache 2.0

Product Compatible and additional computed target framework versions.
.NET net8.0 is compatible.  net8.0-android was computed.  net8.0-browser was computed.  net8.0-ios was computed.  net8.0-maccatalyst was computed.  net8.0-macos was computed.  net8.0-tvos was computed.  net8.0-windows was computed.  net9.0 was computed.  net9.0-android was computed.  net9.0-browser was computed.  net9.0-ios was computed.  net9.0-maccatalyst was computed.  net9.0-macos was computed.  net9.0-tvos was computed.  net9.0-windows was computed.  net10.0 is compatible.  net10.0-android was computed.  net10.0-browser was computed.  net10.0-ios was computed.  net10.0-maccatalyst was computed.  net10.0-macos was computed.  net10.0-tvos was computed.  net10.0-windows was computed. 
Compatible target framework(s)
Included target framework(s) (in package)
Learn more about Target Frameworks and .NET Standard.

NuGet packages

This package is not used by any NuGet packages.

GitHub repositories

This package is not used by any popular GitHub repositories.

Version Downloads Last Updated
1.6.3 0 8/14/2026
1.6.2 0 8/13/2026
1.6.1 101 8/4/2026
1.6.0 106 7/31/2026
1.5.0 125 7/27/2026
1.4.25 103 7/17/2026
1.4.24 87 7/14/2026
1.4.23 129 7/12/2026
1.4.22 106 7/10/2026
1.4.21 108 7/9/2026
1.4.20 101 7/9/2026
1.4.19 99 7/9/2026
1.4.18 97 7/8/2026
1.4.17 103 7/7/2026
1.4.16 129 6/30/2026
1.4.15 107 6/25/2026
1.4.14 114 6/22/2026
1.4.13 120 6/21/2026
1.4.12 112 6/19/2026
1.4.11 113 6/18/2026
Loading failed

### Fixes

- **An `xsl:attribute` (or `xsl:namespace`) inside a typed `xsl:variable` / `xsl:param` / `xsl:with-param` body no longer raises a spurious `XTDE0420` when the construction happens inside a temporary tree.** An `as=`-typed sequence-constructor body builds a *sequence*, not a temporary tree (XSLT 3.0 §9.3) — no document node wraps it, so attribute and namespace nodes are legal members of the result. The engine left the document-construction depth at whatever the enclosing scope had, so `<xsl:attribute>` inside `<xsl:variable as="attribute()*">` looked like an attempt to attach an attribute to a document node and failed with `XTDE0420: Cannot add an attribute node to a document node`. The typed variable, param, with-param, and param-default-body seams now neutralize that depth for the body and restore it afterwards, matching what the user-function seam already did. `as="document-node()"` is deliberately excluded — that body really is wrapped in a document node. Reported by Martin Honnen against DocBook xslTNG 2.8.0 and 2.8.3 (`modules/attributes.xsl:421`), where the `<xsl:variable name="attr" as="attribute()*"><xsl:apply-templates select="@*"/></xsl:variable>` idiom appears roughly twenty times; the whole document transform failed on the sample article. Regression since the DocBook support landed in the 1.4.x–1.5.x line.

- **An `xsl:namespace` that re-declares a binding the element already has is now a no-op instead of emitting a duplicate declaration.** Adding a namespace node for a (prefix, URI) the element under construction already carries is not an error — `XTDE0430` covers only the case where the URIs *differ* — but the engine emitted both, producing two identical `xmlns:p` attributes on one start tag and output that is not well-formed XML. A conflicting URI still raises `XTDE0430`, and a redundant re-declaration of a binding an ancestor already provides is now omitted (same infoset, one fewer declaration). Found while generating DocBook xslTNG's `param.xsl` with our own engine: `tools/generate-parameters.xsl` uses `xsl:namespace-alias` to put the result root in the XSL namespace and then re-declares that same binding with `<xsl:namespace name="xsl">`, so the generated stylesheet could not be reparsed.

### Testing

- Both fixes carry regression tests (`MartinDocBookTypedAttributeVariableTests`, `NamespaceDuplicateDeclarationTests`) covering the reported shapes, the guard cases that must keep failing, and the `as="document-node()"` exclusion. Neither bug was reachable by the existing suites: the unit suite was green at 1196 and the W3C conformance suite asserts only that some tests passed, so it cannot fail on a regression. A repro harness that runs the engine against the real DocBook xslTNG stylesheets now ships in `.claude/skills/engine-repro/`; it builds a runnable xslTNG tree from a source checkout using the engine itself, with no Java, Gradle, or network dependency.