Weekly .NET Roundup: Agent Framework, Aspire, and Build 2026
This week in .NET, the Build 2026 recaps and session watchlists make one theme hard to miss: Microsoft is treating agentic workflows as something .NET teams should build, ship, and operate, not just demo. Alongside guidance for tracking .NET 11 and upcoming C# features, we saw practical patterns for grounded assistants (“golden repos” in ArchAngel) and a clear push toward multi-agent distributed apps with .NET Aspire and Microsoft Agent Framework. We also get a preview of where modernization is heading, with the .NET Day on Agentic Modernization connecting migrations to governed tool-calling flows through Copilot, Foundry services, and MCP-style integrations.
This Week's Overview
Agentic .NET and AI: from Build recaps to multi-agent app patterns
Microsoft Build 2026 continued to set the direction for .NET teams building with AI, with a clear emphasis on agentic workflows, Foundry services, and Copilot tooling that spans IDEs, CLIs, and SDKs. Building on last week's shift toward “plan then act” Copilot workflows plus runtime governance and observability, the Build recap highlights the breadth of announcements - from new Copilot surfaces and models to Agent Framework and governance specs - while the .NET-specific session guide points developers to the talks that matter most for day-to-day platform decisions.
For .NET developers, the practical takeaway is that “agentic” is no longer just a demo theme; Microsoft is publishing building blocks (Agent Framework, Foundry agent services, and governance patterns) that are meant to show up in real apps and pipelines. If you are tracking .NET 11 and upcoming C# features, the session roundup is also a useful index for what to watch (including union types and updates across ASP.NET Core, Blazor, and .NET MAUI) so you can align experiments with what is likely to land.
ArchAngel and “golden repos” as an educational pattern
ArchAngel frames an AI coding assistant as an education tool that enforces repository-backed standards inside the IDE, not as a generic code generator. The reference architecture leans on Semantic Kernel, Microsoft Agent Framework, Azure AI Foundry, and an LSP (Language Server Protocol) layer so guidance can be grounded in a team's “golden repos” (known-good examples of conventions and patterns).
This is a useful pattern even outside classrooms: teams that struggle with consistency can treat “golden repos” as the source of truth and push feedback left into the editor. The key design choice is grounding suggestions in real, versioned engineering standards rather than ad hoc prompt rules, which should make the assistant's feedback easier to trust and audit.
Multi-agent distributed apps with .NET Aspire + Microsoft Agent Framework
A .NET AI Community Standup walked through building distributed multi-agent apps using .NET Aspire for orchestration and Microsoft Agent Framework (MAF) for agent behaviors and collaboration. The ski resort demo focuses on agents exchanging context and coordinating tasks, which is the part many teams get stuck on once they move past single-agent prototypes.
If you are already using Aspire to model dependencies and local dev environments, the session is a good signal that “agents as distributed components” is becoming a first-class scenario, continuing last week's thread of treating agent sessions and components as observable, debuggable workloads in the same toolchain as your services. The Foundry connection matters because it points to a likely deployment shape: agents that run as services, connect to managed model endpoints, and share state through well-defined context handoffs.
.NET Day on Agentic Modernization (June 16 livestream)
Microsoft is using a dedicated livestream to connect modernization tasks (like WinForms and legacy app upgrades) with agentic tooling such as GitHub Copilot, Aspire, Microsoft Agent Framework, and Foundry. Following last week's emphasis on starting modernization with assessments and explicit plans before execution, the agenda explicitly calls out Copilot for Azure and Azure MCP (Model Context Protocol) as part of migration and deployment workflows, which hints at where Microsoft expects operational automation to land: in governed tool-calling flows rather than one-off scripts.
For teams planning upgrades, the timing is useful because it links the “what” (modernize existing apps) to the “how” (agents + MCP-style tooling integrations). If you are evaluating these approaches, this event should help clarify which parts are productized patterns versus custom engineering.
Build 2026 watchlists for .NET teams
Two curated guides make it easier to navigate the Build sprawl this year. Jon Galloway's recap aggregates the big platform moves across Foundry, Copilot (including app/SDK/CLI surfaces and new models), Azure, Windows, Visual Studio, and mentions of .NET 11, while Daniel Roth's post narrows the focus to .NET sessions that cover language/runtime direction and AI building blocks.
If you have limited time, these posts work well as a planning tool for internal brown-bags: pick one track for platform (NET 11 and C#), one for app frameworks (ASP.NET Core/Blazor/MAUI), and one for AI (Foundry + Agent Framework + Copilot integration). The shared theme is that IDE and platform updates are being designed to support agent workflows end-to-end, not as separate add-ons.