or subscribe with
Join 19,100+ readers for one email each week.
Digests » 362
Build the next-generation of performant and UX-refined Windows apps with Telerik UI for WinUI! The Telerik WinUI components equips you with the best possible tooling for your Windows app development - Fluent-inspired design, sport intuitive APIs and have full MVVM support. Check it out today.
this week's favorite
Server performance problems can happen for many different reasons. Memory issues, slow database requests, and too few machines are just some of them. I witnessed my fair share of problems and learned a few tricks along the way. In this article, I’ll tell you about 10 types of issues that can cause performance problems in your server. That’s not to say I categorized all possible problem types, but these might give you some ideas and nudge you in the right direction next time you’re digging into perf matters.
I’m going to talk about reflection-heavy libraries; I will describe the scenario I’m talking about - as it is commonly used today, the status quo, giving a brief overview of the pros and cons of this, and then present the case that times have changed, and with new language and runtime features: it may be time to challenge our way of thinking about this kind of library.
Continuing our series on the over 100 API changes in .NET 6, we look at extensions to the LINQ library.
In this tutorial, I look at the state of the Nullable Reference Types feature in C#, one year after its initial release.
The first thing he talked about, is how the current implementation of record uses a class (read: reference type) as the base object. There will also be a record struct variant available so the underlying type can be a value type. The difference is that a regular record will pass from function to function by reference and a record struct will be copied by its values. The record struct will include with support.