If you've been working with C# since the introduction of null-conditional operators in C# 6.0, you've likely appreciated how ?. and ?[] simplified null-checking when reading values. But what about writing values conditionally? That's where C# 14's null-conditional assignment comes in—and it's a nice improvement for modern C# development.
C# 14 introduces the field keyword, a contextual keyword that reshapes how we write property accessors. This feature eliminates the need for explicit backing fields while maintaining full control over property logic. Let's explore how this powerful addition simplifies C# code and improves developer productivity.
Dapr is an impressive set of APIs for building distributed applications with any language and platform. It provides a set of building blocks that you can use to build microservices. Dapr is based on sidecar architecture. Meaning that you need to run a Dapr sidecar for each of your applications. How do you debug your Dapr apps effectively? If you have been using PowerShell scripts to run and attach your debugger, you know how tedious and error-prone it can be. Ready to see how to use Rider or Visual Studio to debug your Dapr apps with ease and confidence?
With my team, we like to keep our C# code base updated. So, recently we went to .NET 7 and C# 11. At the same time, we were still adopting some of the new capabilities of .NET 6 and C# 10. Our code base is large, so it takes some time. One of the new features that we planned to use was the ArgumentNullException.ThrowIfNull method, which throws an exception if an argument is null. In this post, I will show you how I effortlessly did that refactoring by letting the machine work and not the human 😁 (me). In the past, I used the same approach to migrate lots of code that used Assert.True() to Assert.That(, Is.True) and for some other even more complex cases. We will use ReSharper and Rider for that.
