Wednesday, June 22, 2011 11:53 PM
Have downloaded the source code for .NET 4 from the referencesource.microsoft.com website and followed all the instructions from
However I can't step into the .NET 4 source code. Always get the "No Source Available" tab with "Browse to find source" option is disabled.
Thx - Manoj
==== Here is the output from "output" window
'QnDConsoleApp.exe' (Managed (v4.0.30319)): Loaded 'C:\WINDOWS\Microsoft.Net\assembly\GAC_64\mscorlib\v4.0_22.214.171.124__b77a5c561934e089\mscorlib.dll', Symbols loaded.
'QnDConsoleApp.exe' (Managed (v4.0.30319)): Loaded 'D:\Manoj\scratchpad\csharp\QnDConsoleApp\bin\x64\Debug\QnDConsoleApp.exe', Symbols loaded.
Step into: Stepping over method without symbols 'System.Console.WriteLine'
Thursday, July 07, 2011 6:00 PM
There have been problems with the service that are currently being stablized. Are you still experiencing problems?
Thursday, September 08, 2011 10:32 PM
Yes, this is still a problem.
I have tried using the downloaded symbols (http://referencesource.microsoft.com/netframework.aspx .Net 4.0) and the service (http://referencesource.microsoft.com/symbols). The downloaded symbols cause an error "A matching symbol file was not found in this folder" when I try to "Load Symbols... From Symbol Path" and the service just doesn't work.
Sunday, January 08, 2012 8:30 PMAny solution to this!?? Haivng the same issue - all across the net seems there is not asnwer or solution to the problem and MSFT is totally hidingfrom this one...
Friday, January 20, 2012 9:59 AM
I have the same problem. I cleared my symbol cache, I tried to download through http://referencesource.microsoft.com/symbols, I tried to manually download. All to no avail.
Also using VS 2010 (10.0.30319.1).
It's worth mentioning that Jetbrains Resharper 5.1.3000.12 is also unable to navigate into the source code.
Though I've happily been debugging framework code in the past, at one moment, this has stopped. I can't remember when, but at least for several months now.
- Edited by Grimace of Despair Friday, January 20, 2012 9:59 AM
Monday, February 06, 2012 7:11 AMHello, any update so far? It doesnt work for System.Web in my case. I have 3 subfolders under system.web.pdb with the symbol files, but non of the matching my System.Web.dll
Monday, February 06, 2012 8:30 AM
Microsoft doesn't bother. If you search for this problem, you'll find countless incidents of debugging issues with recent framework assemblies, but no comments from MS.
This sucks big time!
Monday, February 06, 2012 2:16 PM
This is quite a shame and to bad to hear; we experienced the same problem today and would realy need to know when this would work again! One would think that this is an anti movement towards an open source minded org. I hope that this will be fixed soon as this is an unacceptable situation; could someone from Microsoft please give an update on the situation here?
Monday, February 27, 2012 7:41 AMIt still doesn't work untill today
Monday, February 27, 2012 8:40 AMAbout two weeks ago, I asked Scott Guthrie about this on TechDays Belgium. He told me to send an e-mail with details, which he then forwarded to the team that appearantly should be handling this, with me in CC. Haven't heard of it since then.
Thursday, April 12, 2012 11:52 AM
VS2010 SP1Rel V: 4.0.30319:
Gone trough all the hoops as pr instructions: tried both the symbols server and downloaded src -
April 12th - still no cigar on this.... what gives?
- Edited by gsdev Thursday, April 12, 2012 11:59 AM
Wednesday, June 20, 2012 8:42 AM
really, no one from ms??
if this is a joke, it is a bad one..
Friday, August 24, 2012 5:45 PMSeriously guys, this is your flagship product for developers, costs us a fortune, and has mysterious behaviors that we need SOURCE in order to meaningfully debug. The source home page at http://referencesource.microsoft.com/netframework.aspx is uninformative and doesn't even work in visual studio 2010 sp1. FIX THIS and TALK TO US ABOUT IT.
Friday, March 08, 2013 9:42 PM
Sorry for the inconvenience. I sympathize because I also debug through .Net code frequently and have encountered the same issues.
Please refer to http://social.msdn.microsoft.com/Forums/en-US/refsourceserver/thread/41388c7b-582b-4e3f-8178-3d38a3c99639 for the source of the problem and a potential debugging alternative.
Ron Cain [MSFT]