Lutz Roeder's Reflector, that is.
Its obfuscated.
I still don't understand this. Can somebody please explain?
I'll accept Keith's answer, but he's 180 degrees off. Its ironic that the tool used to peer at the source of assemblies is obfuscated.
Also, I'm suprised how serious some of you are. Lighten up! What are you, cobol programmers?
<-- (edit: Maybe some of you are!)
It would have been kind of ironic if it weren't ;-)
I'm curious what product he uses to obfuscate Reflector. Or maybe it's his custom solution - he obviously knows tons about IL.
Of course, I did. For example to find out that .NET Reflector is obfuscated with Dotfuscator.
It's always been the case that its been obfuscated. It was one of the first things I tried with it years ago ;).
What needs explaining, Reflector isn't open source, Lutz decided to obfuscate to protect his IP. Fair game.
It may have been obfuscated by tools such as Xenocode or Dotfuscator. Or as someone said, Lutz may know a lot about IL.
Are you allowed to reflect it according to the EULA (if any) ? I would guess not, and not surprised that you can't.
I think you have your answer right here: Reflector sold to Red Gate