Dotnet Extensions v11.0.0 Release Introduces New Document Abstractions
The dotnet/extensions repository has published version 11.0.0 alongside .NET 11, introducing new experimental document processing and extraction APIs alongside various stability upgrades. The release also brings sliding-window retry budgets for HTTP resilience and promotes server latency telemetry to a stable status.
What changed From the source
The dotnet/extensions repository released version 11.0.0 on November 11, 2026, shipping alongside .NET 11 with new net11 targets added to packages. Key updates include experimental document processing abstractions, HTTP resilience enhancements, and various logging and caching fixes.
In this release, HTTP server latency telemetry APIs transitioned from experimental status to stable. New experimental additions include shared Documents abstractions via Microsoft.Extensions.Documents.Abstractions, Document Extraction capabilities in dedicated packages, and a sliding-window retry budget for HTTP resilience configured through options and builder extensions. Additionally, HybridCacheOptions.DisableCompression was marked as obsolete.
- Added new experimental Documents abstractions and Document Extraction packages.
- Promoted HTTP server latency telemetry (AddHttpServerLatencyTelemetry) to stable.
- Introduced sliding-window retry budget and selectable defaults for HTTP resilience.
- Marked HybridCacheOptions.DisableCompression as obsolete.
- Added descriptions to metric attributes and instrument descriptions across telemetry.
At a glance · AI & .NET
What changedWhy it mattersWho should careUpgrade and migration considerations
Why it matters Analysis
The introduction of shared document and extraction abstractions standardizes how text and data ingestion handle document formats, which may simplify future AI and data pipeline implementations. Stabilizing HTTP server latency telemetry gives production environments reliable metrics without relying on experimental warning suppressions.
The addition of a sliding-window retry budget gives developers finer control over transient fault handling in HTTP calls, helping prevent retry storms under degraded network conditions. Meanwhile, marking older caching options obsolete indicates a shift toward cleaner configuration patterns in HybridCache.
- Standardized document extraction assists developers building data ingestion workflows.
- Telemetry stability reduces friction when monitoring production server latency.
- Retry budgets improve application resilience under heavy failure loads.
Who should care Analysis
Developers working with .NET 11 and updating their foundational libraries will be directly affected by these package updates. Teams implementing document processing pipelines or AI features can evaluate the new experimental packages to see if they fit their architecture.
Engineers maintaining resilient HTTP clients and utilizing advanced telemetry instrumentation will benefit from the upgraded diagnostic capabilities and stable latency measurement tools.
- .NET developers upgrading applications to target .NET 11.
- Teams building AI ingestion or document processing workflows.
- Architects focusing on HTTP resilience and distributed application telemetry.
Upgrade and migration considerations Analysis
Teams adopting version 11.0.0 should review experimental warning codes if they consume the newly introduced document extraction or HTTP retry budget features, as these APIs are subject to change. The source material does not specify exact step-by-step migration guides beyond acknowledging obsolete properties like HybridCacheOptions.DisableCompression.
Developers should audit their configurations for obsolete members and verify compatibility when moving package references to target .NET 11.
- Review usage of obsolete HybridCache options during updates.
- Note experimental diagnostic codes associated with new document and resilience features.
- The source does not specify a detailed step-by-step migration guide.
Sources and further reading
- Release notes for v11.0.0 on GitHub (original source)
Original: “dotnet/extensions releases v11.0.0”, dotnet/extensions releases (Microsoft.Extensions.AI and more), published 11 Nov 2026, retrieved 11 Nov 2026. This article was drafted with AI assistance from the official source and passed automated fact and quality checks. Spotted a mistake? See our corrections policy.