I agree Mcgurk, really no one should be using undocumented keywords. I also agree about the volatile thing; we have a 250k line C# codebase and not a single volatile (or undocumented) keyword usage. :-)

We use yield all the time, however, despite the article mentioning how rarely used that is.

He missed some big, undocumented keywords like __makeref, __arglist and others.

This is negative alarmist bull crap.

He starts out the post by saying, "use reflector only when you really have to. Using it is technically breaking the EULA."

He then goes on to describe another unrealistic situation: you saw some code, you implemented something similar, then Microsoft sues you.

While it may be technically true that if you copy something Microsoft has a patent on that they might sue you for copy infringement.

But let's be practical here -- has Microsoft ever sued anyone for breaking the EULA by using Reflector? Come on.
Likewise, MS isn't going to sue if you create a class that looks a lot like the patented XYZ class.

Microsoft uses their patent portfolio defensively. They're not gonna come knocking on your door out of the blue and sue you for a class that looks something like theirs. Jeez.

James and Aaron, this benefits developers in 3 ways beyond what Reflector gives us:

First, the source comments are intact, which means it becomes easier to understand .NET library source code.

Second, the code structure and local variable names are preserved.

Third, we can use the debugger to step in to .NET libraries and use the threads, locals, watch, etc. windows.

Someone should start a CodePlex project containing handy extension methods.

This shows off both the power and potential for abuse of LINQ queries.

Now this is pretty cool, nice work guys.

I'd also add, it only makes sense that a SQL developer himself reacts negatively to anything that downplays the importance of writing SQL by hand.

Bad, bad article. Misleading, uninformed about LINQ, seems to think stored procs are the be-all and end-all, doesn't realize LINQ can use sprocs. Bad article, please do not vote up this uninformed crap.

Damien's right, the Ribbon and Navigator is pay for, everything else is free.

However, I must say that the KryptonToolkit is one of the finest I've ever used. Very easy to use and also very easy to use as a skinner for other controls, including both standard WinForms controls as well as your own custom controls. Go grab this excellent toolkit before he decides to start charging for it. :-)

They make "fetal" mistakes? :-) How childish. ;-)

You can also use the DebuggerDisplay attribute, which I find to be superior than ToString.

[DebuggerDisplay("Count = {Count}")]
class MyCollection
{
....
}

Great article, but very old, written 4 years ago. Still relevant, however.

I'm still seeing it as down. Isn't working in either Firefox 2 nor IE 7.

Link appears to be dead.

Yes, but at 24 bytes, the compression dictionary would be pure overhead, and would actually add to the size of the download.