Is this post (http://blogs.msdn.com/sburke/archive/2008/01/16/configuring-visual-studio-to-debug-net-framework-source-code.aspx) still the preferred method for debugging framework code from visual studio? Or has anything changed?
2
votes
The article you posted is exactly how I debug framework source.
– kenwarner
This does not work for me now. I am able to debug .NET 4.0 source code, but not .NET 3.5 SP1 source code. And in order to do so, I download .NET 4.0 symbols and source code from referencesource.microsoft.com/netframework.aspx and point my Tools->Options->Debugging options to point at the symbols from that install (which install to a location on my local hard drive ... I am not pointing it at Microsoft's symbol servers).
– cplotts
2 Answers
3
votes
This is one way. The other way is using the upcoming .NET Reflector Pro that allows decompiling the framework and debugging through it. A free beta is available.
The first way has the advantage that you get the actual source code with comments. The second way has the advantage that you can debug framework code even if Microsoft does not provide the source for the part you are interested in.
