Updated on 2008/09/17: Fixed problem when skipping elements. Updated on 2008/09/15: Fixed problem when trying to read missing attributes. One of new features introduced in .NET 3.5 that I welcomed the most was LINQ to XML. The old DOM API was a bit clumsy to use, and the simple fact that you don't need owner documents any more makes the new XElement much more flexible and pleasant to work with than the old XmlElement. Also new is an API for streaming XML output, XStreamingElement, that by using defe[...]

Did you know that the Avalon project (the original name of WPF) was started back in 2001, even before .NET Framework 1.0 was released, from the team that originally developed Internet Explorer 4 DHTML support and the XMLHttpRequest API that enables AJAX? I've learned that and some other interesting trivia from this Channel 9 video: Michael Wallent: Advent and Evolution of WPF

I've been lately looking at some channel 9 videos, and found a lot of great stuff there. Two that I found particularly interesting were these: Expert to Expert: Contract Oriented Programming and Spec# Ted Neward: On Java and .NET, Software Academics versus Practioners, General Purpose Programming Languages

Can Erten created a very useful expression tree to CodeDom converter. He wrote about it here: Expression Trees-Lambdas to CodeDom Conversion. I created a visual studio debugger visualizer based on it. You can find it in attachment. Just copy the assembly to My Documents\Visual Studio 2008\Visualizers and you're set. I also attached the full source code. ExpressionCodeDomVisualizer.dll ExpressionCodeDomVisualizerSourceCode.zip