Hey, I'm Steven a .NET Developer in Switzerland. I am a Microsoft MVP. Also, this blog is open source on GitHub.
Microsoft.Extensions.Configuration has had ConfigurationKeyNameAttribute since .NET 6 which it lets you rename the key a property maps to. But there was never an official way to say "don't bind this property at all." That gap is finally closed in .NET 11 with ConfigurationIgnoreAttribute.
Some time ago (over 4.5 years ago!) I wrote a blog post titled: "A better enumeration - Type safe from start to end". While cool and so - it had some issues. Let's tackle them!
What is the output of that code snippet?
Console.Write(new Derived("Test"));
public abstract record Base(string Key)
{
public override string ToString() => Key;
}
public sealed record DerivedRecord(string Key) : Base(Key);
Probably "Test"?
We have Join. We have LeftJoin. We have RightJoin. But somehow we still don't have a proper full outer join in LINQ. That might come soon!
I am using a tool called Handy, which is basically nothing else than speech to text. But it does it so well that I thought, okay, let's give it some broader audience.
Sometimes doing arbitrary stuff feels just good! So let's do that!
Some time back I wrote about "async2 - The .NET Runtime Async experiment concludes" basically moving the async state machine into the runtime. Now with .NET 11 we are seeing the fruits of that labor.
The first preview of .NET 11 and C# 15 did just release. Some weeks back I did add already an article about that: "Collection Expression Arguments in C# 15+". Well quicker than anticipated that feature is now part of it!
In Dezember 2025 and January 26 I created a small helper tool: the .NET Toolbox. I also made a post about, if you wanna be "up to speed": ".NET Toolbox". I did some bug fixes and updates.
I came across a recent thing, where I hit the limit with the "normal" approach of modeling my entity and had to resort to extension methods.