Hey, I'm Steven a .NET Developer in Switzerland. I am a Microsoft MVP. Also, this blog is open source on GitHub.
Thanks to @toupswork for starting a funny discussion about extension properties on a recent post I made: "Adding static getter thanks to extensions". Therefore let's discuss two ridiculous ideas to add properties to existing types using extension methods in C# 14.
I vibe-coded a small tool to get a grasp on your projects MEMORY.md that is in ~/.claude.
xUnit.v3 got a new major release. This blog post is more about the consequences of that for your local build and CI/CD pipelines than about the new features.
Quite some time passed since I posted a changelog to the .NET Toolbox. And there are big news: The Toolbox is running dotnet native in the browser thanks to wasm and Mono!
As always my yearly take on the latest .NET release. In a few months dotnet 11 will be released and I wanted to have a look into some performance metrics.
Here a simple scenario: You have a StringComparer and you want to add your own comparer to the mix - for example a "natural sort" order, so "file2" sorts before "file10" instead of after.
With C# 14 we can extend the family and make it feel natural!
Blazor is a bit talkative when it comes to the Developer Console. PageSpeed Insights for example does complain:
Browser errors were logged to the console
The fix is easy.
LinkedIn: The "professional" network where critical thinking takes a backseat and everyone is an expert in everything.
Signals - more often used in Angular - are a nice way to tell the UI that something has changed. Blazor doesn't have that natively, but how would it look, if it did?
If you use AsSplitQuery anywhere in your codebase, EF Core 11 has a present for you: your queries get faster.