Fog Creek Software
Discussion Board

Welcome! and rules

Joel on Software

Not a question, more a recommendation

I hope that everyone using .NET has a copy of Lutz Roeder's utilities, especially the latest version of Reflector.NET

I can't recommend these tools highly enough. If you want to know how .NET is written, just disassemble it into IL, C#, VB or Delphi, with Reflector.

Steve Jones (UK)
Wednesday, July 21, 2004

Agreed. I also find it useful for finding all those undocumented exceptions in the FCL :)

Wednesday, July 21, 2004

Yes, Reflector is the coolest thing I've ever seen.

Thursday, July 22, 2004

I think the only thing I'd ask to be added to it is the ability to disassemble a complete class in one go, although you can get an outline view.  More in keeping with how I read source code than looking at one type at a time.

The documentor is useful too.

Thursday, July 22, 2004

I guess being able to disassemble a whole class at a time, or even a whole assembly, would make it too easy to rip off other people's code.

I know you can do it anyway, but making it a bit tedious is a good thing.

Excellent tool though, I use it all the time (mostly to dig around in the .NET framework. There's gold in there).

Thursday, July 22, 2004

There is a plugin called "Reflector.FileDisassembler" I found that will disassemble a .Net dll file in one go.

Thursday, July 22, 2004

Big DITTO regarding those undocumented FCL exceptions!

Coming from a Java world, that's one of the things I find supremely infuriating and disappointing in .NET: how do you guarantee that you catch the right exceptions in the right places if they are not documented anywhere, and hardly any inheritance is used?

I wish everybody who realizes this would complain to your favorite MS blogger (politely) or directly to the MS wish list.

Maybe it's not too late for whidbey...

Had anybody noticed that in Whidbey they "fix" .NET providers to have common base classes for everything _except_ database exceptions?

That's one of the most pervasive benefits of ODBC, that they normalized error information across providers, and even invented the SQLCODE to detect some error cases independent of understanding any vendor-specific error codes.

I can only dream of getting that back in .NET... *sigh*

Thursday, July 22, 2004


I understand how you feel. I personally prefer the .NET way of dealing with this but I supose that being used to the checked exceptions mechanism makes unconfortable working with .NET.

Here is the reason explained by the man himself about why .NET lacks checked exceptions:

The Trouble with Checked Exceptions
A Conversation with Anders Hejlsberg, Part II
by Bill Venners with Bruce Eckel

.NET Developer
Wednesday, July 28, 2004

*  Recent Topics

*  Fog Creek Home