TUnit is a newer framework that launched its first alpha releases in 2024 and is on the path to a v1.0.0 release.

https://andrewlock.net/converting-an-xunit-project-to-tunit

Here's your comprehensive guide to understanding and building Model Context Protocol (MCP) Servers for C# developers. It’s a great hands-on resource for exploring MCP and AI assistant integration in .NET environments. 📚 https://msft.it/6041sRjhd

Bit different from usual ASP.NET stuff, but you might find this interesting.

https://youtu.be/JGwFsyyewYc?si=Udwc19INncdm1IOk

In real-world applications, duplicate API requests are more common than many developers expect. Users double-click buttons, mobile apps retry requests automatically, networks fail and resend calls, and background jobs may retry failed operations.

https://medium.com/stackademic/how-to-prevent-duplicate-api-requests-in-net-c54e4770da2d

If your .NET pods are each using 1–2 GB of RAM, you may be leaving a lot of pod density — and money — on the table. Here are the first things I would look at.

https://ardalis.com/top-10-ways-to-reduce-net-memory-usage-in-kubernetes/

NET 11 is presented as a release that “turns performance up to eleven,” delivering hundreds of targeted optimizations across the runtime, JIT, GC, async infrastructure, and core libraries. The article highlights major advances such as deeper devirtualization, smarter inlining, expanded escape analysis, leaner delegate structures, and a redesigned async/await system driven by the JIT rather than the compiler. Together, these improvements reduce allocations, shrink call overhead, streamline async state machines, and unlock faster execution paths—resulting in noticeably better real‑world performance without requiring developers to change their code.

https://devblogs.microsoft.com/dotnet/performance-improvements-in-net-11/

OnTheFlySettings - Update your Asp .Net API/App settings without re-start. Zero downtime!
https://dev.to/veritassoftware/ontheflysettings-update-your-asp-net-apiapp-settings-without-re-start-zero-downtime-2mj0

For years, APIs have had one primary audience: applications. A frontend calls an endpoint, receives a response, and the developer handles whatever happens next. All of it was from a human user. Now, we have a new player: AI. Instead of simply following predefined application logic, an agent can decide which endpoints to call, determine the order of operations, retry failed requests, and carry out multi-step tasks based on a user's goal. Your API is no longer just serving an application, it may be serving an AI system capable of taking action. Companies like Stripe, Twilio, and Shopify have already launched dedicated Model Context Protocol servers to capture agent-driven traffic.

https://blog.elmah.io/designing-apis-for-ai-agents-your-api-has-a-new-user/

AWS Transform now converts Azure SDK .NET apps to AWS SDK equivalents. It detects Azure services, maps them to AWS, rewrites code, and validates output. Supported conversions: Azure Functions to Lambda, Blob Storage to S3, Queue Storage to SQS, and Cosmos DB to DynamoDB (preview). Available in 8 regions: US East, Mumbai, Tokyo, Seoul, Sydney, Canada, Frankfurt, London.

https://aws.amazon.com/about-aws/whats-new/2026/10/aws-transform-azure-to-aws-code-conversion/