Digests » 332
this week's favorite
We’ve launched a new Game Development with .NET section on our site. It’s designed for current .NET developers to explore all the choices available to them when developing games. It’s also designed for new developers trying to learn how to use .NET by making games.
This small post is an attempt to understand, and explain one specific nuance of how Blazor re-renders the UI.
The first and most important thing to know about C# as a programming language is this: C# is a strongly-typed language. This means that every variable, every constant, every class, every single object ever created using C# has a type. It is impossible for an object to exist in C# without it having a type.
Memory problems in a big .NET application are a silent killer of sorts. Kind of like high blood pressure. You can eat junk food for a long time ignoring it until one day you face a serious problem. In the case of a .NET program, that serious problem can be high memory consumption, major performance issues, and outright crashes. In this post, you’ll see how to keep our application’s blood pressure at healthy levels.
Learn about using the null object pattern with ILogger and ILoggerFactory to avoid NullReferenceExceptions without forcing implementors to supply logging instances.