or subscribe with
Join 20,300+ readers for one email each week.
Digests » 243
In 2018, 6.2M developers around the world used C#, mostly working on a desktop, AR/VR, and gaming projects. Is this going to change in 2019? Tell us - take this survey and join 20,000+ devs globally who shape future trends. You may win one out of $12,000 worth of prizes or $1,000 in cash for referring other developers to take the survey! Open until Feb 3rd. Hurry up - take the survey now!
this week's favorite
This is the first article on my exploration into improving LINQ performance using value type enumerators, refs, duck typing, interface constraints, IReadOnlyList interface and so on.
The CLR makes heavy use of a technique known as stack walking (or stack crawling). This involves iterating the sequence of call frames for a particular thread, from the most recent (the thread’s current function) back down to the base of the stack.
So you want to add some sort of networking functionality to your C# application? Then this little blog-post is for you! It doesn’t even matter if you’d consider yourself a noob because I’m about to make network code real easy for you.
So, some of you may not know about this keyword at all, but at one point in your life you may find out and feel that it will be useful to use it when you are doing mathematical operations in your code. Let’s start by discussing what this keyword provides.
Understanding deadlocks, show common deadlock types, how to solve them, how to debug them and best practices to avoid them.