PhoenixmlDb.Core 2.0.0

dotnet add package PhoenixmlDb.Core --version 2.0.0
                    
NuGet\Install-Package PhoenixmlDb.Core -Version 2.0.0
                    
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.Core" Version="2.0.0" />
                    
For projects that support PackageReference, copy this XML node into the project file to reference the package.
<PackageVersion Include="PhoenixmlDb.Core" Version="2.0.0" />
                    
Directory.Packages.props
<PackageReference Include="PhoenixmlDb.Core" />
                    
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.Core --version 2.0.0
                    
#r "nuget: PhoenixmlDb.Core, 2.0.0"
                    
#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.Core@2.0.0
                    
#: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.Core&version=2.0.0
                    
Install as a Cake Addin
#tool nuget:?package=PhoenixmlDb.Core&version=2.0.0
                    
Install as a Cake Tool

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 interfacesIDocumentDatabase, IContainer, IDocument for storing and retrieving XML/JSON documents
  • XDM node typesXdmElement, XdmAttribute, XdmDocument, etc. — the W3C XQuery Data Model
  • Transaction modelIReadTransaction, IWriteTransaction with 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"
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 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.
  • 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.0.0 0 9/15/2026
1.7.0 816 9/11/2026
1.6.7 836 8/24/2026
1.6.6 185 8/23/2026
1.6.5 180 8/21/2026
1.6.0 162 8/7/2026
1.5.0 113 8/6/2026
1.4.0 108 8/4/2026
1.3.0 365 7/27/2026
1.2.2 297 7/9/2026
1.2.1 159 7/8/2026
1.2.0 332 6/28/2026
1.1.9 331 6/17/2026
1.1.8 210 6/14/2026
1.1.7 142 6/9/2026
1.1.6 121 6/9/2026
1.1.5 325 5/23/2026
1.1.4 423 5/17/2026
1.1.3 172 5/14/2026
1.1.2 232 5/12/2026
Loading failed

**Major because it breaks builds, not only behaviour.** Part of the coordinated
namespace-consolidation train: `PhoenixmlDb.Core`, `PhoenixmlDb.XQuery` and `PhoenixmlDb.Xslt`
all move to 2.0.0 together.

> **This follows 1.7.0 directly.** Core was not part of the 1.8.0 train — it was unchanged, so
> nothing was published for it — and there is no Core 1.8.0 or 1.9.0 to look for.

### Breaking

- **`NamespaceId.PhoenixmlDb` (id 9, `https://schemas.phoenixml.dev/2026/db`) is retired.** The
 constant remains, marked `[Obsolete]`, and the registry no longer carries a row for it.

 **If you build with `TreatWarningsAsErrors` and name that constant, this release fails your
 build.** If you read id 9 out of `NamespaceRegistry` you now get nothing back. Both are
 deliberate: the namespace held only `dbxml:metadata`, which has moved.

- **Extension functions now live in `NamespaceId.PhoenixmlFunctions` (id 13),**
 `https://schemas.phoenixml.dev/2026/functions`, conventional prefix `phx`. All six extension
 functions move there — see `PhoenixmlDb.XQuery` 2.0.0.

- **`dbxml` now means only `https://schemas.phoenixml.dev/2026/meta`.** It is no longer
 overloaded between metadata and extension functions.

### Fixed

- **A no-namespace element opened in the ambient default namespace** rather than the empty one.
 An element written with no prefix, inside a scope carrying a default namespace, took that
 namespace instead of none.