dotnet

New and old ways of creating your own exceptions in dotnet with C# 11 and .NET 7

Most of the new features in C# 11 are incremental language improvements. However, one of these features stuck me immediately as something we don’t need – and also really need to do more.

The C# 11 required keyword lets you reduce constructor boiler plate code and ensure that new objects have required property members set when using inline initializers.

In this article we’ll explore the top 10 mistakes I see new and seasoned developers make with exception management in dotnet source code. These principles should be valid for all dotnet languages, but examples will be provided in C#.

The C# nameof expression is not going to revolutionize the way you write code, but it is likely to improve the maintainability and accuracy of the code – at least a little bit.

In this article we’ll explore what generics are in C# and how implementing your own generic types and generic methods in C# can help level up your coding ability.

Snapshot testing lets you add a broad safety net to your application and are available in common languages like JavaScript and dotnet.

Newer .NET developers are sometimes confused when they encounter readonly members in classes and the newer init-only setters. In this article we’ll explore both keywords along with the related get-only auto property. Finally, we’ll help you understand when to use each of these powerful language features.

Let’s take a look at some of the more common mistakes I see in C# code, explore why they’re mistakes, and introduce better ways of doing things.

This article first appeared at KillAllDefects on January 21st, 2020. Let’s talk about how LINQ’s GroupBy method makes grouping data in C# easy. We’ll start basic and then go over every available…