Text, JSON and XML Components

Encoding, StringBuilder, regular expressions, JSON, XML and LINQ-style XML.

5 physical componentsSource 6d429559

Targets in this family

Component	Kind	Production dependencies	Representative header
`Text`	static	`Buffers`, `Core.Base`	`System/Text/ASCIIEncoding.hpp`
`Text.Json`	static	`Core.Base`, `Text`, `Collections.Core (private)`	`System/Text/Json/JsonCommentHandling.hpp`
`Text.RegularExpressions`	interface	`Core.Base`	`System/Text/RegularExpressions/Capture.hpp`
`Xml`	static	`Core.Base`, `Uri`, `Diagnostics (private)`	`System/Xml/ConformanceLevel.hpp`
`Xml.Linq`	static	`Core.Base`, `Xml`	`System/Xml/Linq/Extensions.hpp`

Text

Text covers encodings, builders, formatting helpers and Base64-related surfaces. The string model is UTF-8 based; several index and length APIs therefore use bytes where .NET uses UTF-16 code units.

Regular expressions

Text.RegularExpressions is header-only and provides the project’s curated regex surface. Treat pattern, option and Unicode behavior as a practical subset rather than a guarantee of the entire .NET engine.

JSON

Text.Json uses vendored nlohmann JSON machinery behind Sharp Runtime-compatible types. Serialization is curated; general .NET reflection-driven serialization infrastructure is not present.

XML

Xml uses vendored tinyxml2, exposed publicly where XmlDocument headers expose its types. Xml.Linq adds LINQ-style names, elements and documents. Xml.XPath is a compatibility alias of the physical Xml archive because their implementations have mutual binary dependencies.

Strictness matters

Recent remediation tightened XML lifecycle and strictness behavior. XPath covers the implemented subset; variables, custom functions and general extension contexts are not a full System.Xml.XPath engine.

Complete catalogue

See all 41 physical components for external dependencies, ownership and direct graph details.