8 Answers, 1 is accepted
You've probably opened a reference assembly. Reference assemblies are hollow assemblies, containing only the signatures of the types and all their members of the real assemblies they "reference". They're used by various tools in the development process to represent their "full" equivalents. Thus, the "real" assembly and the "hollow" one have the same strong names and can be easily mistaken. If you want to see the code in the methods, you need to open the "real" assembly. Since the example you've given is essentially the Silverlight's mscorlib, the path to the "real" Silverlight assembly is %Program Files%\ Microsoft Silverlight\ <Version>.
I hope this will solve your problem.
Greetings,
Yordan Dikov
the Telerik team
Explore the entire Telerik portfolio by downloading Telerik DevCraft Ultimate.


Also, a small question, probably linked to the current one. I have my own assembly, i moved it to my real project, i also moved *.pdb file. However, when i'm trying to open it in Studio (just GoToDefinition), it shows empty method names.
If to open assembly via JustDecompile standalone, it shows methods, but it usually takes much more time (to find file, open it, find class, method, etc).
JustCode decompiles your dll if you have this setting enabled.
Another way is to navigate to the method and set a break point. Then you will be asked whether you want to decompile the dll.
As last solution you can open the dll in the Assembly browser and decompile it manually.
Thanks.
Please, do not hesitate to contact us if you have any further questions or need of assistance.
Zdravko
Telerik

Thanks for your answer.
Lookign like, for all cases i'd need to have JustCode?
I'm using Resharper, not sure that i want to switch to JustCode now.
Dont you have any plans to implement some kind of non-free "JustDecompile Studio Plugin", which would enable those features without JustCode?
Its okay for me to pay for tools which improves my speed of development, but i really don't want to buy whole JustCode and use only one feature of it.
From the last Q3 2013 release, we've introduced a Visual Studio extension in JustDecompile. You'll be able to decompile a referenced assembly from your project using a Solution Explorer context command. It will decompile the assembly for you straight in the JustDecompile UI. Some more info: http://www.telerik.com/products/decompiler/whats-new.aspx#vs-extension
Hope this helps.
Vladi
Telerik

Yees, but it is still a bit less user-friendly than just pressing F12 on requested word.
And they are still empty. I just opened some random reference: http://clip2net.com/s/6aTiKu
You're correct that it's much more user-friendly with F12. For now we offer it only through JustCode. I'm sorry.
As for the empty decompiled assembly, it seems like a bug on our (JustDecompile) side. I've logged it and we'll fix it. Please stay tuned for new versions of JustDecompile and update.
Vladi
Telerik