List<T> is one of the most commonly used types from .NET Framework Base Class Library. Although it is used so often not everyone is really familiar with how the class works internally. Almost everyone knows that
T array internally to store the items. But for most people that’s the only internal detail they know. In next few blog post I’ll try to step through
List<T> source code and point some interesting implementation details that every .NET developer should be aware of.
A lot of LINQ to XML questions on StackOverflow are being answered using
Descendants() method calls. It looks like most of people think it’s the best way to handle and query XML document: it’s easy to use, you don’t have to worry about whole tree structure. It just works. But are these solutions really good ones? Is
Descendants() method really that good as it seems to be? I would say: NO! I think common LINQ to XML queries should not use
Descendants(). I’ll try to answer it shouldn’t be used in this blog post.
First non LINQ-related question on my blog, but another one in response to great StackOverflow question: Casting generic parameter to and from integer. Every day you can find something that inspires you to do your own research and think hard why things work like they do. That’s exciting, isn’t it?
Another blog post in response to a StackOverflow question. It’s about LINQ again, but it’s no as low-level as the one from previous post. This time the question is quite simple: How to search Hierarchical Data with Linq.
The question is simple: does LINQ optimize multiple Where calls? I think most people would say no. I did say no too! Google says no - unless you dig really deep! But what is the correct answer to that question?