tags:

views:

824

answers:

9
+2  A: 

What needs explaining, Reflector isn't open source, Lutz decided to obfuscate to protect his IP. Fair game.

Kev
+9  A: 

It would have been kind of ironic if it weren't ;-)

Keith
+6  A: 

I'm curious what product he uses to obfuscate Reflector. Or maybe it's his custom solution - he obviously knows tons about IL.

kokos
A: 

Are you allowed to reflect it according to the EULA (if any) ? I would guess not, and not surprised that you can't.

Peteter
+3  A: 

It's always been the case that its been obfuscated. It was one of the first things I tried with it years ago ;).

Campbell
+8  A: 

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!)

Will
I'm laughing so hard right now...
Maxim Zaslavsky
+1  A: 

It may have been obfuscated by tools such as Xenocode or Dotfuscator. Or as someone said, Lutz may know a lot about IL.

Vincent
A: 

I think you have your answer right here: Reflector sold to Red Gate

Yaakov Ellis
no, actually Reflector was obfuscated like that from the beginning. It has nothing to do with red gate.
Marek
Well, it might: Lutz Loeder might have thought since the beginning he would try to make some money off Reflector, and therefore kept the code secret.
Qwertie
+4  A: 

Of course, I did. For example to find out that .NET Reflector is obfuscated with Dotfuscator.

DotfuscatorAttribute in Reflector.exe (version 5.1.6.0)

Christian
Interesting. I wonder if this is RedGate's doing. I mean, Dotfuscator. I don't remember seeing this way back in the olden days when I first reflected reflector.
Will
@Will: I just checked out Lutz Roeder's .NET Reflector 5.0.25.0 (still available from Softpedia) from the beginning for 2007, and it was already obfuscated with Dotfuscator.It's especially interesting that RedGate's still using Dotfuscator for .NET Reflector, although they have their own .NET obfuscator {smartassembly} (http://www.smartassembly.com/).
Christian