I've followed the steps outlined in http://blogs.msdn.com/sburke/archive/2008/01/16/configuring-visual-studio-to-debug-net-framework-source-code.aspx to enable source debugging of the .NET Framework, and I had it working in the past. Now that I'm using .NET 3.5 SP1, it seems to have stopped working. Beyond the steps in the blog entry I just mentioned, what special steps can I make to get source debugging working again?
+1
A:
You probably need to refresh your downloaded symbols. In the Symbol settings dialog you specify a cache directory where symbols are cached. Since you have upgraded your .NET framework, therefore, the symbols cached there are most probably the older ones which won't work with the newer dlls. Just clear your directory and then download symbols for .NET 3.5 SP1 again.
Aamir
2008-12-17 06:39:07
Didn't work for me.
Vilx-
2009-02-18 15:30:44
I have this problem and .NET 3.5 SP1 is the first version I've tried with.
Taylor Leese
2009-11-12 07:23:05
+3
A:
I had the same problem when I upgraded to .NET 3.5 sp1. It seems like it's very simplified with the sp1 release. Now you only have to check the "Enable .NET framework source stepping" (which automatically unchecks "Enable just my code"). You don't have to change anything in the "Symbols" settings anymore.
kaze
2009-05-09 07:47:29
+1
A:
Debugging didn't work for me when I first followed those steps. I deleted symbol directory and removed all settings from Options -> Debugging -> Symbols and it worked.
- Uncheck "Enable Just My Code"
- Check "Enable .NET Framework source stepping"
- Check "Enable source server support"
- Don't add anything to Debugging -> Symbols
Works just fine on Windows 7 x64 with Visual Studio 2008 SP1.
Nikola Smiljanić
2009-12-20 17:52:09
It didn't work when I had them. When there is nothing in there it downloads the correct ones.
Nikola Smiljanić
2010-05-10 10:32:45