Editor's note
I pulled together a pretty varied lineup this time: AI agents show up all over the place, but so do the fundamentals like error handling and data access. The ASP.NET 10 piece on IExceptionHandler and Problem Details is practical, and the EF Core vs Dapper comparison is the kind of decision guide people keep coming back to.
Agents and .NET design choices
Enjoying the newsletter? Your feedback helps us grow and reach more developers.
Today's Articles
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Jasen's take on today's picks
Getting Started with Agents in VS Code
Quick start on agents in VS Code; useful if you want to see the workflow before the buzzwords take over.
.NET AI Community Standup: Squad: AI agent teams for any project
SQUAD looks like a serious attempt at multi-agent coordination for .NET devs, not just another demo.
Visual Studio’s built-in agents are getting more capable, especially around debugging and profiling.
Standardizing Global Errors: Using IExceptionHandler and Problem Details Services in ASP.NET 10
Modern ASP.NET error handling with Problem Details is one of those upgrades that pays off immediately in real apps.
Custom Agents in Visual Studio: Built in and Build-Your-Own agents
Readonly, immutable, and frozen are easy to confuse; the benchmarks make the tradeoffs concrete.
Readonly vs Immutable vs Frozen in C#: differences and (a lot of) benchmarks
The EF Core vs Dapper comparison is a solid refresher for choosing productivity or control deliberately.
C# 13 & .NET 9 — Part 16: Blazor, Blazor Server vs. Blazor WebAssembly
Vertical slices inside a modular monolith is a very practical architecture conversation, not an abstract one.

















