.NET Development
-
Sep 21 2026
The two questions code coverage can't answer: property-based and mutation testing for .NET and Angular
Code coverage tells you a line ran. It doesn't tell you whether you tried the inputs that matter, or whether anything would notice if the line were wrong. Those are two separate gaps, and there's an old technique for each: property-based testing generates the inputs you didn't think of, mutation testing breaks your code to see if a test complains. Both are decades older than my interest in them, and what changed isn't the techniques. It's that generating code got cheap while checking it didn't. Here's how they work on .NET and Angular, what they cost, and why each one is the check on the other.
-
May 26 2026
What's new in Aspire 13.3
Aspire 13.3 lands WithBrowserLogs — a tracked Chromium browser as a child resource, streaming console and network events into the same dashboard timeline as your backend traces, with first-party commands for opening it, configuring it, and capturing screenshots. More on the rest of 13.3 to follow in upcoming parts.
-
May 2 2026
Azure Functions Consumption on Linux is going away, what are the migration paths?
Linux Consumption is going away, and Microsoft's migration guidance points at Flex Consumption. But is Flex actually the right destination for your apps, or are the other paths Azure Functions on Azure Container Apps, Container Apps Jobs, AKS with KEDA, or plain ACA worth a closer look?
-
Mar 30 2026
C# scripting in .NET 10: stop context-switching to your AI agent's scripts
You're debugging an issue and ask your AI agent to write a quick script that checks your database state. It hands you Python or JavaScript. You can read it, sure, but you can't review it at a glance the way you can with C. With .NET 10's dotnet run file.cs, there's no reason to leave your main coding language anymore for the utility scripts your agent writes during development.
-
Aug 11 2025
TimeProvider in .NET8, the solution to flaky tests with DateTime.Now issues
If you're still using DateTime.Now in your .NET tests, you're building on quicksand. Flaky time-dependent tests are some of the most frustrating issues—they pass locally, fail randomly in CI/CD, and destroy confidence in your deployment pipeline. Good news, .NET 8 brings us TimeProvider to solve this problem. This isn't just another abstraction—it's Microsoft's answer to a problem and baked directly into the framework to make time-dependent code reliably testable.