PhoenixmlDb.Xslt
1.6.10
See the version list below for details.
dotnet add package PhoenixmlDb.Xslt --version 1.6.10
NuGet\Install-Package PhoenixmlDb.Xslt -Version 1.6.10
<PackageReference Include="PhoenixmlDb.Xslt" Version="1.6.10" />
<PackageVersion Include="PhoenixmlDb.Xslt" Version="1.6.10" />
<PackageReference Include="PhoenixmlDb.Xslt" />
paket add PhoenixmlDb.Xslt --version 1.6.10
#r "nuget: PhoenixmlDb.Xslt, 1.6.10"
#:package PhoenixmlDb.Xslt@1.6.10
#addin nuget:?package=PhoenixmlDb.Xslt&version=1.6.10
#tool nuget:?package=PhoenixmlDb.Xslt&version=1.6.10
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-documentfor 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.
Related packages
| 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 | Versions 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. |
-
net10.0
- PhoenixmlDb.Core (>= 1.6.7)
- PhoenixmlDb.XQuery (>= 1.6.9)
-
net8.0
- PhoenixmlDb.Core (>= 1.6.7)
- PhoenixmlDb.XQuery (>= 1.6.9)
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 |
|---|---|---|
| 2.1.0 | 0 | 9/17/2026 |
| 2.0.0 | 81 | 9/15/2026 |
| 1.8.0 | 175 | 9/14/2026 |
| 1.7.0 | 73 | 9/11/2026 |
| 1.6.15 | 167 | 9/9/2026 |
| 1.6.14 | 117 | 9/7/2026 |
| 1.6.13 | 158 | 9/2/2026 |
| 1.6.12 | 121 | 8/30/2026 |
| 1.6.11 | 107 | 8/29/2026 |
| 1.6.10 | 173 | 8/27/2026 |
| 1.6.9 | 104 | 8/26/2026 |
| 1.6.8 | 102 | 8/26/2026 |
| 1.6.7 | 107 | 8/24/2026 |
| 1.6.6 | 112 | 8/23/2026 |
| 1.6.5 | 130 | 8/22/2026 |
| 1.6.4 | 132 | 8/16/2026 |
| 1.6.3 | 103 | 8/14/2026 |
| 1.6.2 | 102 | 8/13/2026 |
| 1.6.1 | 124 | 8/4/2026 |
| 1.6.0 | 122 | 7/31/2026 |
Consumes PhoenixmlDb.XQuery 1.6.9, which carries the `format-dateTime(@untypedAttr, ...)` fix.
### Nodes from `fn:transform` kept the node but lost its tree
Reported by Martin Honnen via sxq, an XQuery implementation of Schematron. Nodes handed back
with `delivery-format='raw'` arrived stripped of their ancestors:
fn:path() was: /Q{}book[1] /Q{}book[1]
now: /Q{}books[1]/Q{}book[1] /Q{}books[1]/Q{}book[2]
Both results claimed to be the root of their own tree — and, as he noticed, reported the SAME
path, because each was. The cross-store transport carried only the node's own serialization,
and re-anchoring reparsed that into a fresh document, so a `<book>` became a one-element tree
by construction. It now carries the serialized ROOT plus a child-index chain down to the node.
A second fault, independent and not in the report: re-anchoring ran per item, so two siblings
were parsed into two separate copies of their document and would not have shared a parent.
Each distinct root is now parsed once for the whole result, so `$r[1]/.. is $r[2]/..` holds.
His diagnosis pointed at `xsl:evaluate`; that was innocent — `fn:transform` raw with a
stylesheet function that merely selects nodes reproduces it identically.
### `document-node(element(x:report))` matched nothing
Also from Martin Honnen. A name test nested inside a kind test never had its namespace
resolved, so the matcher's "this shouldn't happen" branch returned false and the template
silently matched nothing. `element(x:report)` was broken the same way and unreported.
### Errors report instead of crashing
The CLI printed a clean error line and then rethrew, so .NET appended "Unhandled exception"
and a stack trace on top, exiting 134. It now reports and exits 2. All twelve W3C error codes
that were thrown as bare `InvalidOperationException` now carry an error code and a stylesheet
location.
### Absent-focus guards removed
Four guards claimed to handle an absent focus and could not — they caught an exception type
neither context implementation throws. Making them work breaks W3C `accumulator-061` both ways
it can be attempted, so the escaping error and the sentinel are load bearing. The misleading
code is gone and the behaviour is unchanged; see BUGS.md #17 before making them live.
Xslt.Tests 1310 passed, 0 failed, 1 skipped (1289 at 1.6.9)
XSLT conformance 10237/10630 = 96.30%