Typically, we use a base class that comprises these methods that all value object implementations should extend. In the above example, I’ve provided a basic implementation of value objects in C#.

In this example we will take advantage of a ConcurrentBag class to store objects. Note that the ConcurrentBag class in the System.Collections.Concurrent namespace provides a lock-free, thread-safe ...

I won't say that, all by itself, C# 9 is worth the migration to .NET 5 (I might make that claim about C# 8 and .NET Core 3.x, though). The new version of C# 9 is more than just a nice feature of .NET ...

I've got a C# class that is all string types, nothing fancy, and once the item is created it gets serialized with the new System.Text.Json stuff and then attempts to POST to a web server.

Under a new draft specification, C# and VB will be adding what they are calling a “record class”. This is essentially an immutable class defined solely by its constructor.

The methods in the God object then simply delegate work to the various utility classes and smaller objects that were created as the God object was refactored. If you do go with the facade approach, ...