Microsoft releases .NET 11 with a broader toolkit for agent applications
Microsoft releases .NET 11 with a broader toolkit for agent applications
Microsoft released .NET 11 on November 10, combining its annual application-platform update with tools for building and working alongside AI agents. The release includes C# 15 and is a Standard Term Support version, with two years of support. .NET 10 remains a supported long-term option. Microsoft announcement
For AI developers, Microsoft highlights Microsoft.Extensions.AI for accessing models, Model Context Protocol for connecting tools, and Microsoft Agent Framework for agents and workflows. Experimental Blazor components support the Agent User Interaction Protocol, or AG-UI, for agent-driven web experiences. The announcement also points to .NET Skills, MAUI DevFlow for inspecting running applications, and an upgrade canvas for reviewing modernization work. Those capabilities connect AI development to the existing application stack rather than introducing another foundation model. Microsoft announcement
The distinction between a generally available platform and individual experimental features matters. Developers can adopt the supported runtime without assuming every AI-facing component carries the same stability guarantees. Microsoft explicitly labels the Blazor AI components experimental. Microsoft announcement
The accompanying technical overview describes changes that also matter to services behind agents. Runtime-native asynchronous execution no longer requires a preview-feature switch for projects targeting .NET 11, while compilation and continuation changes aim to reduce overhead. The SDK enables its Native AOT command-line entry point and MSBuild server by default. These are implementation changes, not independently measured application-speed guarantees. Technical overview
Operational changes include OpenTelemetry for command-line telemetry, broader test-run controls and revised container-publishing behavior. The runtime also raises minimum hardware requirements for x86/x64 and Arm64 systems. Teams evaluating an upgrade should therefore check deployment compatibility alongside application and dependency tests, rather than treating the AI additions as the whole migration decision. Technical overview
For organizations already building in .NET, the practical significance is a more integrated route from model calls to tools, workflows and user interfaces. That is an editorial assessment of the release’s scope, not evidence that autonomous applications have become reliable without testing. This article relies on Microsoft’s announcement and documentation; no runtime benchmarks or agent applications were independently tested.
Primary sources rechecked November 15, 2026.
Sources and citations
Revision history
Published .