A carefully curated weekly newsletter for .NET developers to help you learn and stay on top of technology.
Join over 23,900 readers for a free weekly email with fresh news, articles and tutorials.
- Learn from the best.
- Follow the latest in the ecosystem.
- Keep an eye on useful tools and libraries.
- And finally. Get inspired. Every week.
What our readers say about the newsletter?
I've actually used a few of these at my job. I hope to use some of these in the near future with .NET 6.
This week was very informative, thank you! I haven't heard about standard feature flags before, and the post about LINQ was surprising. DiagnosticListener might also come in handy some day.
Great concept coverage on articles!
Loved the article about The Operation Result Pattern, which I recommended to friends and colleagues, and made me migrate my Azure Function to .NET 6.
#435 — October 03, 2022
Data grids are the gold standard for displaying large amounts of data in business applications. In this article we’ll explore the idea of using a data model to reduce the amount of user interface (UI) code that needs to be written by the enabling auto generation feature on the Telerik UI for Blazor data grid.
this week's favorite
Did you ever wonder why you "should" use async and await in your ASP.NET Core applications? Most probable you heard something about performance. And there is some truth to it, but not in the way you might think.
I became aware recently that there were many C# compiler errors that do not have a corresponding documentation page. That documentation is open-source and I chose to spend some time contributing some pages for the community. Looking at a language feature from the perspective of its compile-time errors is rather enlightening, so I'd though I'd write a bit about these features in hopes of offering a better understanding for my readers.
C# 11 improves Structs compared to C# 10 (and earlier). Before C# 11, every Struct properties in the constructor had to be initialized or risk a compilation error. C# 11 fixes that and we will see how in this post.
When you don't have any fallback operation to manage null values (eg: retry pattern), you should throw an exception instead of returning null.