Comments
4 comments
-
This is the effect you see if you are looking at the "Reference Assemblies" (which are used by the compiler and contain no IL) instead of the real assemblies.
File/Open Cache is useful for finding the real assemblies in order to see the decompiled code. -
I tried that when I read it in another forum post. I get the same results.
I don't know nearly as much about assemblies as I should. How can you tell the difference between a reference assembly and the real one? By using File/Open Cache, does this only let you open a real one? -
It looks to me that you have hit the gateway to the unmanaged code ... meaning that property calls into unmanaged code - so there is no IL to decompile from that point. Reflector won't jump into the unmanaged code and decompile it.
Could be a few reasons that I can think of:
1. the assembly that holds the implementation has been NGen'd
2. the code is calling into the CLR (which is unmanaged)
3. the code is a RCW (runtime callable wrapper) which is a proxy for a COM object (which is unmanaged) -
That is what I was afraid of. It's got to be #3. I don't understand COM as much as I should either so I wasn't sure what limitations there were. Thanks for the explanation!
Add comment
Please sign in to leave a comment.
There is no option to expand methods. Everything seems to be working as expected for some assemblies, but not others.
Thanks for your help! I love the potential this product has in helping me debug some difficult situations!