PhoenixmlDb.Core
2.7.0
dotnet add package PhoenixmlDb.Core --version 2.7.0
NuGet\Install-Package PhoenixmlDb.Core -Version 2.7.0
<PackageReference Include="PhoenixmlDb.Core" Version="2.7.0" />
<PackageVersion Include="PhoenixmlDb.Core" Version="2.7.0" />
<PackageReference Include="PhoenixmlDb.Core" />
paket add PhoenixmlDb.Core --version 2.7.0
#r "nuget: PhoenixmlDb.Core, 2.7.0"
#:package PhoenixmlDb.Core@2.7.0
#addin nuget:?package=PhoenixmlDb.Core&version=2.7.0
#tool nuget:?package=PhoenixmlDb.Core&version=2.7.0
PhoenixmlDb.Core
Core types, interfaces, and XDM (XQuery Data Model) implementation for PhoenixmlDb — a modern embedded XML/JSON document database for .NET.
What's in this package
- Database interfaces —
IDocumentDatabase,IContainer,IDocumentfor storing and retrieving XML/JSON documents - XDM node types —
XdmElement,XdmAttribute,XdmDocument, etc. — the W3C XQuery Data Model - Transaction model —
IReadTransaction,IWriteTransactionwith MVCC snapshot isolation - Index configuration — path, value, full-text, and metadata indexes for fast queries
- XML parser and serializer — parse XML into XDM trees and serialize back
- Atomic value types — dates, times, durations, and other XSD types with correct semantics
When to use this package
Directly: If you're building a storage provider, query engine integration, or tooling that works with XDM types.
Indirectly: This package is a dependency of PhoenixmlDb.XQuery, PhoenixmlDb.Xslt, and the CLI tools. You typically don't reference it alone unless you need the core types without query/transform capabilities.
Quick example
using PhoenixmlDb.Core;
using PhoenixmlDb.Xdm.Parsing;
// Parse XML into an XDM tree
var parser = new XmlDocumentParser();
var result = parser.Parse("<order><item>Widget</item></order>");
var doc = result.Document;
// Navigate the tree
var root = doc.Children[0]; // <order> element
Console.WriteLine(root.StringValue); // "Widget"
Related packages
| Package | Description |
|---|---|
| PhoenixmlDb.XQuery | XQuery 4.0 query engine |
| PhoenixmlDb.Xslt | XSLT 4.0 transformation engine |
| PhoenixmlDb.XQuery.Cli | xquery command-line tool |
| 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
- No dependencies.
-
net8.0
- No dependencies.
NuGet packages (3)
Showing the top 3 NuGet packages that depend on PhoenixmlDb.Core:
| Package | Downloads |
|---|---|
|
PhoenixmlDb.XQuery
XQuery 4.0 query engine for PhoenixmlDb |
|
|
PhoenixmlDb.Xslt
XSLT 4.0 transformation engine for PhoenixmlDb |
|
|
Phoenixml.Platform.Editor.Xml
XML/XSD vocabulary binding for Phoenixml.Platform — concrete IDocument and ITreeNodeProvider implementations against PhoenixmlDb.Core's XDM, XSD schema validation pipeline. |
GitHub repositories
This package is not used by any popular GitHub repositories.
| Version | Downloads | Last Updated |
|---|---|---|
| 2.7.0 | 68 | 11/20/2026 |
| 2.6.2 | 189 | 11/19/2026 |
| 2.6.1 | 172 | 11/18/2026 |
| 2.6.0 | 614 | 10/20/2026 |
| 2.5.0 | 419 | 10/13/2026 |
| 2.4.0 | 244 | 10/9/2026 |
| 2.3.0 | 116 | 10/8/2026 |
| 2.2.0 | 193 | 10/6/2026 |
| 2.1.0 | 193 | 10/5/2026 |
| 2.0.0 | 1,678 | 9/15/2026 |
| 1.7.0 | 961 | 9/11/2026 |
| 1.6.7 | 1,044 | 8/24/2026 |
| 1.6.6 | 210 | 8/23/2026 |
| 1.6.5 | 205 | 8/21/2026 |
| 1.6.0 | 193 | 8/7/2026 |
| 1.5.0 | 138 | 8/6/2026 |
| 1.4.0 | 130 | 8/4/2026 |
| 1.3.0 | 437 | 7/27/2026 |
| 1.2.2 | 318 | 7/9/2026 |
| 1.2.1 | 184 | 7/8/2026 |
Minor because the public API adds members and marks two obsolete. Nothing is removed, and code that
uses an obsolete member still compiles; a project that treats warnings as errors sees CS0618 until
it moves to the replacement. One source change: the parameter of `AddNameIndex(string?)` is named
`namespaceName`, so a call that names the argument `namespaceUri:` does not compile.
- **A name index keeps its namespace name exactly as given.** `NameIndexDefinition` has a new
property, `NamespaceName` (`string?`). A namespace name is compared as a string, codepoint by
codepoint, so `http://example.com/` and `http://example.com/` are different namespaces. An index
declared with `AddNameIndex("http://example.com/")` matches the elements in that namespace. Any
non-empty string is accepted, relative names included, as the XML parser accepts them. `null` or
an empty string indexes names in all namespaces.
- **`NameIndexDefinition.NamespaceUri` is obsolete.** A `System.Uri` normalizes its text
(`http://example.com/` becomes `http://example.com/`). The property reads and writes
`NamespaceName` through `Uri.OriginalString`; its getter is `null` for a name that is not a URI
reference.
- **`IndexConfiguration.AddNameIndex(Uri)` is obsolete.** Use `AddNameIndex(string)`. The `Uri`
overload stores `Uri.OriginalString`, and its parameter has no default value. `AddNameIndex()` with
no argument selects the string overload and indexes names in all namespaces. An untyped `null`
argument is ambiguous between the two overloads; pass `(string?)null`.
- **The parameter of `AddNameIndex(string?)` is named `namespaceName`.** The code analysis rule CA2234
does not tell callers to use the `Uri` overload.
- **`XsDateTime.IsDateTimeStamp`** is a new `init` property (default `false`). It marks a value of the
derived type `xs:dateTimeStamp`, so that a type check can tell it from an `xs:dateTime` value with a
timezone. It takes no part in equality, hashing or ordering, and a `with` copy keeps it.
The obsolete members are removed in the next major version.