Browse .NET Roundups (11)

This week in .NET centers on staying current and testing early: Microsoft shipped August 2026 servicing updates for .NET 10, 9, 8, and .NET Framework, while .NET 11 Preview 7 continued to advance runtime, SDK, and the major app stacks. On the AI side, Microsoft.Extensions.AI added routing and failover primitives that help teams run multi-model and multi-endpoint setups more safely, and Copilot workflows picked up practical improvements from instruction hygiene guidance to local Ollama-based integrations. Rounding things out, Visual Studio 18.9 improved Git submodule management inside the IDE, and agent governance guidance focused on reducing Teams noise and enforcing runtime allow/deny tool-call policy with auditing.

This week's .NET roundup centers on making agent and MCP workloads reliable in the real world, from durable long-running tasks on Azure App Service to the stateless-first direction in MCP C# SDK 2.0. On the security and supply chain front, NuGet.org is capping API key lifetimes (pushing teams toward OIDC-based Trusted Publishing), while ASP.NET Core in .NET 11 preview expands automatic CSRF defenses using Fetch Metadata headers. We also cover practical developer experience updates, including richer CI test reporting in Microsoft.Testing.Platform, Blazor performance and lifecycle tweaks in .NET 11 Preview 7, and a concrete local AI sample for live speech-to-text with Foundry Local.

This week's .NET roundup centers on MCP becoming a practical foundation for agent tooling, with the MCP C# SDK v2.0 and new Agent Framework hooks that let agents discover skills at runtime with clearer safety boundaries. Visual Studio and VS Code also pushed further into agent-driven workflows, from a Copilot Chat Agent preview to an MCP-backed MSBuild binlog analyzer that can explain failures and performance bottlenecks. On the engineering side, the focus shifted to reliable automation (a unit-test agent that validates tests end-to-end and traced multi-agent orchestration with OpenTelemetry) plus a solid web security refresher on Fetch Metadata headers for defense-in-depth CSRF protection.

This week in .NET, Microsoft Agent Framework hit a more practical stride with a batteries-included runtime (Harness) and Declarative Workflows 1.0 that moves multi-agent orchestration into YAML you can review and change without rewriting core code. On the web stack, .NET 11 Preview 6 focused on safer defaults and sharper APIs, including async validation for minimal APIs, automatic CSRF protection, and OpenAPI updates that help keep server and client contracts aligned. We also saw VS Code refine the in-editor agent experience and more hands-on guidance for building MCP servers in .NET, with sampling and logging patterns that improve repeatability and observability. Rounding things out, hybrid integration stayed in focus with a detailed walkthrough for running Azure Logic Apps Hybrid on a self-managed Kubernetes setup.

This week's Weekly .NET Roundup centers on two tracks: staying current with July 2026 servicing updates (including CVE fixes, containers, and known issues) and getting early signal from .NET 11 Preview 6. Mobile teams have a clear action item with .NET MAUI moving to CoreCLR-only on Android, iOS, and Mac Catalyst, while Visual Studio continues to expand Copilot workflows with built-in Agent Skills, model selection, and new extension governance options. We also cover practical modernization and agent operations patterns, from a structured ASP.NET-to-.NET 10 course to OpenTelemetry-instrumented local agents, plus a Durable Functions approach for long-running MCP tools on Azure Functions.

Welcome to this week's Weekly .NET Roundup, where the themes are clear: tighter security scanning and more practical, governed agent workflows. CodeQL 2.26.0 adds AI prompt injection detections and improves query accuracy across languages, which is relevant for .NET repos that mix C#, JavaScript/TypeScript, and GitHub Actions-heavy CI. On the productivity side, Copilot's new upgrade canvas, real-world cross-repo agent automation patterns, and Agent Framework updates (orchestration patterns and stable skills) show how teams are turning agents into repeatable workflows. We also cover VS Code Copilot governance details, Logic Apps Standard moving closer to Functions-style hosting for .NET, and the growing link between agent platforms (Foundry) and UI patterns in Blazor.

Welcome to this week's .NET Roundup. Microsoft set a clear planning deadline with .NET 8 and .NET 9 ending support on November 10, 2026, pushing teams to budget upgrade work toward .NET 10 and revisit TargetFramework and dependency constraints. On the AI tooling side, the focus shifted from chat-based demos to repeatable workflows: MCP-powered build diagnostics in GitHub Actions, practical auditing and OpenTelemetry for agent governance, and patterns for building tools (Functions, search) with safer data access. We also saw platform-focused updates like SkiaSharp 4 for .NET MAUI, a C# preview feature for closed class hierarchies, Azure Blob client-side integrity checks reaching GA, and a useful warning about ambiguous routes when inheriting ASP.NET Core controllers.

Welcome to this week's Weekly .NET Roundup, where the center of gravity kept shifting from chat-based assistance to agentic workflows you can host, secure, and observe in real apps. Azure Functions gained richer MCP building blocks (including Entra ID auth and structured responses), Blazor demos showed agents triggering UI actions through components, and Microsoft Agent Framework pushed the "agent harness" idea as a practical control plane for approvals and telemetry. On the platform side, .NET 11 preview 5 introduced StringBuilder.MoveChunks() to reduce allocations in hot text pipelines, while Azure tooling and IDE updates (azd, Azure SDK, VS Code, and Visual Studio) focused on tightening day-to-day loops for provisioning, AI-assisted development, and cost/usage visibility.

This week's Weekly .NET Roundup spans three practical threads: getting ready for platform changes, tightening security posture, and making AI-assisted development more repeatable. We cover the Logic Apps shift toward Azure Functions out-of-proc hosting on the road to .NET 10, plus .NET 11 Preview 5 and June 2026 servicing fixes you should roll into SDK mirrors, container images, and CI. On the tooling side, MCP shows up in build-log investigation and assistant skills, while agent middleware patterns and OpenAI-compatible endpoints point toward production-ready agent hosting. We also look at a real npm supply chain compromise that matters to polyglot .NET pipelines, and hands-on database guidance for Postgres performance, temporal modeling, and RAG at scale.

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 .NET roundup spans language changes, dependency hygiene, and how agent-driven development fits into real engineering workflows. On the platform side, C# proposals like caller-unsafe boundaries and .NET 11 preview union types aim to make APIs more explicit and domain models easier to reason about, while Blazor WebAssembly adds a Web Worker template to move heavy work off the UI thread. In build and security tooling, NuGet package pruning and audit-by-default raise the baseline for actionable vulnerability signals with less restore-graph noise. We also look at how Copilot planning, governance extensions, and OpenTelemetry tracing (including Aspire Dashboard) are pushing agent sessions toward the same reviewability and observability standards as production services.