Allow developers to step through .NET Framework sources
Microsoft currently makes reference sources available for major .NET Framework releases. You can use this source in Visual Studio so that you can step through .NET Framework code, like List<T>. That’s very useful in some situations. Unfortunately, .NET Framework servicing updates and small changes to the .NET Framework (like via: Windows Update) break this experience. Let us know if you use this feature and if you want us to fix it such that you can count on it across the lifetime of a .NET Framework release.
Today, we’re happy to announce that we’ve fixed this issue. We’ve also added a few more features, such as an online browsing experience as well as an option to download and browse the entire reference source with Visual Studio.
Check out our blog post that announces the improved .NET Reference Source experience:
.NET Framework Team
The Reference Source update in Feb 2014 was nice, but it did not actually address Hanselman's request. Exact same problem as before, many programmers now have .NET Framework 4.5.2 or later on their machine and the current server doesn't supply PDBs or source for those versions.
You can vote for a new idea here: https://visualstudio.uservoice.com/forums/121579-visual-studio/suggestions/6886255-please-keep-the-reference-source-symbol-server-upd
Holyyyy ****! Thank you so much!!
fake voters ! only 56 comments and 3000 votes ?! ...
yes, I would like to use .net source debugging
Ok, so at least I was not dreaming about I used to be able to do .NET Famework source code debug stepping. Never thought installing update would break this feature.
I need framework 1.1 back on my computer PLEASE !
I need framework 1.1 PLEASE
Tom Potts commented
This would be great -- right now I'm struggling trying to get it working at all.
Additionally, it'd be great if you could use "Go To Definition" on framework calls.
Scott Brickey commented
Reflector can do this for a decent chunk of the code out there. Granted, the generated symbol files can be rather large.
Wolfgang Kinner commented
Карен Тазаян commented
+1 I want it!
Please fix it, it is a life saver!
Please fix it, it's never worked for me, and I'd love to use it
I've had very bad luck pointing VS to sources every time I've tried it. I followed the guide on symbolsource.org numerous times with different VS versions/editions, and invariably I end up with a broken debugging experience rather than attached sources. Worse still, when I reverse the guide the debugger is still broken. I've even reinstalled VS just to restore the debugger.
I'm DEFINITELY voting this up.
Pavel Brans commented
It will be very useful. Now .NET source stepping is work bad on my experience. On one my pc it works well, on other it don't(sources not available always) with same settings and updates.
Martin Cornelius commented
Eventually, having read 'Clean Code', many of us came to this belief: The very best documentation is and will always be - the code ! In this sense, you should definitely fix this !
Hui Lin commented
This capability is absolutely needed by us. After struggling for a couple of days, I gave up and switch to .NET reflector. However, working on dissembled code is not ideal, plus the fact that a lot of the variables we would like to see their values in debugger have been optimized away and not available.
Yes please! It is very frustrating that it works sometime and not at other times. Usually when I really need it to work...
.net reflector allows you decompile code on the fly.
But having latest source code available will make sense.