I just found an intersting interview with Scott Guthrie, the General Manager for .NET:

http://msdn2.microsoft.com/en-us/arcjournal/bb266332.aspx

It contains some nice anecdotes about the early days of .NET ('The only compiler they had was this thing called "simple managed C," which we affectionately called "smack."'), talks about the role of an architect ('The super-senior architects who have the biggest impact can marry deep, deep technical and design skills with people skills and collaborative abilities.') and the status of .NET ('I think the hallmark of a good framework doesn't lie in the applications people build on it that you had expected them to build, but in the fact that customers and developers were able to take it far beyond what you had imagined').

Lutz released a cool new version 5.0 of .NET Reflector. You can find details about the new features here: http://www.aisto.com/roeder/paper/reflector5.ppt

Updated versions of the FileDisassembler and the SQLBrowser are located here on my website: http://www.denisbauer.com/NETTools.aspx

Please let me know, if you run into any issues.

Scott wrote a nice post about the coolest of the new features: The "code://" protocol handler.
http://www.hanselman.com/blog/Reflector5ReleasedWorldDominationAssured.aspx

The following code in C# works for my sample:

for(int i = 0; i < HG1.Items.Count; i++)
{
    HierarGrid c = (HierarGrid) HG1.Items[i].Cells[1].FindControl("DCP").FindControl("Panel_Author_Title").FindControl("ChildTemplate_Author_Title").FindControl("HG1");
    for(int j = 0; j < c.Items.Count; j++)
    {
        string title = c.Items[j].Cells[2].Text;
    }
}

Remark: ?Author_Title? is the name of the DataRelation that I am using.

I just published a new version 2.2 of the HierarGrid and the DynamicControlsPlaceholder that hopefully fixes all problems with reloading UserControls under ASP.NET 1.0-2-0. As before, both components are compiled against .NET 1.0 but tested with 1.1 and 2.0.

V2.2.0.0 (published 2006-05-12)

Download here

Did you notice that the new version of .NET Reflector supports reading PDB files? This means that local variables are now correctly named during decompilation and are no longer called local[x].

Currently Reflector expects the PDB file next to the assembly to pick it up. I think it would be a nice feature if you could specify an alternative symbol path.