These are a small sample of the problems that I've solved with Reflector: Did my resource get correctly embedded into that DLL? What did the compiler decide to call it? Did that DLL get signed correctly? Gee, I wonder what kind of compiler magic is needed to implement iterators, IDisposable, locks, etc. Whoa. For whatever reason, I need to use reflection to call the internals of someone else's code, I wonder what that thing is called. I'm tracking down a bug in the .NET Framework, I wonder what on earth is going on in there... Ooooohh. Whoa. I wonder how to call this F# code from C#, or vice versa. I wonder how the F# compiler implements ____. Whoa. I'm getting corrupted memory exceptions, I wonder what IL the C# compiler is generating...oh it's wrong, Whoa. What's the difference between System.Byte[] and System.Byte[*]? etc.
Granted, some of the things are nightmares but the others are pure curiosity/learning. -Matt On Wed, Feb 2, 2011 at 9:02 AM, Justin Bozonier <[email protected]>wrote: > So a couple people now are surprised.. nay, shocked that I don't use > Reflector and I'm pretty sure that means I would have more ninjitsu if > I did. What problems are you guys solving with it? > > -- > You received this message because you are subscribed to the Google Groups > "Seattle area Alt.Net" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]<altnetseattle%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/altnetseattle?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Seattle area Alt.Net" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/altnetseattle?hl=en.
