Please turn JavaScript on

.NET Blog

Want to stay in touch with the latest updates from .NET Blog? That's easy! Just subscribe clicking the Follow button below, choose topics or keywords for filtering if you want to, and we send the news to your inbox, to your phone via push notifications or we put them on your personal page here on follow.it.

Reading your RSS feed has never been easier!

Website title: DevBlogs - Microsoft Developer Blogs

Is this your feed? Claim it!

Publisher:  Unclaimed!
Message frequency:  0.33 / day

Message History

As AI adoption scales, cost, uptime, and latency become first-class constraints on application architecture. Routing between models or providers is a lever on all three at once.

These new Microsoft.Extensions.AI primitives handle it directly: route by message content, fail over when a provider goes down, or build your own policy on the same abstractions, all as IChatCl...


Read full story

Instructions files have a habit of growing in only one direction.

A model makes a mistake, so somebody adds a rule. A tool changes, so somebody adds a workaround. A new model arrives, but the old guidance stays. Before long, the repository has an instructions file that reads like a combination of onboarding guide, style manual, troubleshooting diary, and prompt-enginee...


Read full story

Today, we are excited to announce the seventh preview release of .NET 11! This release includes improvements across libraries, the .NET Runtime, SDK, C#, ASP.NET Core, .NET MAUI, Entity Framework Core, F#, and Windows Forms. Check out the linked release notes below and get started today.


Read full story

Welcome to our combined .NET servicing updates for August 2026. Let’s get into the latest release of .NET and .NET Framework. Here’s a quick overview of what’s new in our servicing releases:

Security improvements

.NET has been refreshed with the latest update as of August 11, 2026. This update contains security and non-security fixes.

This month you will find th...


Read full story

When a test fails in CI, “the build is red” is only the starting point. The useful questions are whether this change caused the failure, whether the test has failed before, and where to find the evidence. If answering them means searching a job log, downloading an artifact, and finding the teammate who remembers how that test behaved last month, the report has not done enough...


Read full story