Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I followed these steps to be able to debug in the .Net framework code. This work well for some parts of the framework (for example for System.Drawing.dll), but not for other parts (clr.dll, mscoree.dll, …).
This seems a bit strange to me since the code in these dlls was released by Microsoft (at least the parts I see in the call stack).
I am using VS2010 & .Net 4.
Did I do something wrong, or are the correct pdb files not released by Microsoft?
Microsoft released a shared-source implementation of the whole common language runtime, including mscoree.dll, but this isn’t the source code that goes into the real .NET framework.
On the other hand, the source code you’ve obtained for System.Drawing.dll etc. is the real source code to the .NET framework, but you can’t get at the runtime code this way.
Here’s the download for SSCLI, otherwise known as Rotor: http://www.microsoft.com/downloads/details.aspx?FamilyId=8C09FD61-3F26-4555-AE17-3121B4F51D4D&displaylang=en
More explanation on the differences: What is the difference between SSCLI 2.0 (ROTOR) and .NET?