Use the image generation tool in Foundry Agent Service - Microsoft Foundry

Generate images from text prompts with the image generation tool in Microsoft Foundry Agent Service. Configure agents, deploy models, and save output.

Extend your coding agent with .NET Skills - .NET Blog

Introducing the dotnet/skills repository and how .NET agent skills can improve coding agent workflows.

Build a real-world example with Microsoft Agent Framework, Microsoft Foundry, MCP and Aspire - Microsoft for Developers

Building AI agents is getting easier. Deploying them as part of a real application, with multiple services, persistent state, and production infrastructure, is where things get complicated. Developers from the .NET community have requested whether a real-world example that shows running on local machine as well as on the cloud in a cloud-native way. We’ve […]

Dew Drop – March 10, 2026 (#4621) – Morning Dew by Alvin Ashcraft

🗂️ Custom Session Store for Complex Objects in ASP.NET Core

ASP.NET Core’s default session fails with complex objects. This post shows how to store them safely in memory.

Visual Studio Dev Essentials: Free, Practical Tools for Every Developer  - Visual Studio Blog

Visual Studio Dev Essentials is a free developer program that gives you access to tools, Azure credits, downloads, and training to help you build apps and grow your skills.

Extend your coding agent with .NET Skills - .NET Blog

Introducing the dotnet/skills repository and how .NET agent skills can improve coding agent workflows.

Async vs Sync in .NET: Understanding ThreadPool Impact | Stefan Đokić posted on the topic | LinkedIn

Some developers still think async/await makes code faster. I thought the same when I started with .NET. Then one day, our API started slowing down under load. Not because of the CPU. Not because of the database. Because we were blocking threads everywhere. .Result .Wait() Sync database calls Sync HTTP calls Everything worked perfectly… until traffic increased. What many developers miss is this: Async doesn’t make one request faster. A request that takes 400ms with sync code will still take ~400ms with async. The real difference is what happens to the ThreadPool. With synchronous code: Thread → waits for HTTP → waits for DB → waits for I/O The thread is blocked the whole time. With async code: Thread → starts I/O → returns to ThreadPool OS notifies completion → continuation resumes. That single difference is what allows ASP .NET Core to handle thousands more concurrent requests. The real killer I keep seeing in production codebases is this: Sync-over-async var result = httpClient.SendAsync(...).Result; This blocks the thread again and under load it can lead to ThreadPool starvation. And once that happens, your API starts feeling “mysteriously slow”. No CPU spikes. No database bottlenecks. Just no threads left to process requests. I made this visual to explain what actually happens inside ASP .NET Core. Curious: Have you ever debugged a production issue that turned out to be sync-over-async? __ 📌 Don't miss the next newsletter issue, 20,000 engineers will read it, join them: thecodeman.net 📌 Join our Free Closed .NET Hub (1.1k members) and get access to content nobody publicly has: https://lnkd.in/gu_5HiMD ♻️ Repost to others. 📂 You can save this post for later, and you should do it. ➕ Follow me ( Stefan Đokić ) to learn .NET and Architecture every day. | 32 comments on LinkedIn