Home Dashboard Directory Help
Search

.NET Framework 4 Reference Sources fail since out-of-date by petrula


Status: 

Active


181
0
Sign in
to vote
Type: Bug
ID: 697947
Opened: 10/29/2011 10:46:39 AM
Access Restriction: Public
2
Workaround(s)
view
69
User(s) can reproduce this bug

Description

The .NET 4 source does not work with the current .NET 4 Framework library.

For source see
http://referencesource.microsoft.com/netframework.aspx

For installation instructions see
Configuring Microsoft Visual Studio for local debugging of Reference Source
http://referencesource.microsoft.com/downloadsetup.aspx

The .NET 4 source fails with a No Source Available error since the source is out of date.
The .NET 4 version for this source is 4.0.30319.1.
Recent Microsoft updates changed some DLLs to 4.0.30319.233.
The 4.0.30319.1 source does not debug with the current 4.0.30319.233 DLLs.

We urgently need Microsoft to update the .NET Framework 4 Reference source to the current update 4.0.30319.233.

Moreover, the sources should be updated along with .NET 4 updates on a continuing basis.
Thanks
Details
Sign in to post a comment.
Posted by stec00 on 4/11/2013 at 6:26 AM
Follow-up: To be more specific, here are the modules where symbols didn't load:

    mscorlib.dll    C:\Windows\Microsoft.Net\assembly\GAC_32\mscorlib\v4.0_4.0.0.0__b77a5c561934e089\mscorlib.dll    Yes    N/A    Cannot find or open the PDB file.        1    4.0.30319.17929 built by: FX45RTMREL    09/07/2012 04:55    6C690000-6D64F000    [8980] vstest.executionengine.x86.exe: Managed (v4.0.30319)        
    System.dll    C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System\v4.0_4.0.0.0__b77a5c561934e089\System.dll    Yes    N/A    Cannot find or open the PDB file.        4    4.0.30319.17929 built by: FX45RTMREL    09/07/2012 05:22    6BD10000-6C689000    [8980] vstest.executionengine.x86.exe: Managed (v4.0.30319)        
    System.Web.dll    C:\Windows\Microsoft.Net\assembly\GAC_32\System.Web\v4.0_4.0.0.0__b03f5f7f11d50a3a\System.Web.dll    Yes    N/A    Cannot find or open the PDB file.        45    4.0.30319.17929 built by: FX45RTMREL    09/07/2012 05:20    659C0000-66677000    [8980] vstest.executionengine.x86.exe: Managed (v4.0.30319)        
    System.Web.Mvc.dll    C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.Web.Mvc\v4.0_4.0.0.0__31bf3856ad364e35\System.Web.Mvc.dll    Yes    N/A    Cannot find or open the PDB file.        40    4.0.20710.0    11/07/2012 05:47    5F8B0000-5FA7E000    [8980] vstest.executionengine.x86.exe: Managed (v4.0.30319)        
Posted by stec00 on 4/11/2013 at 6:14 AM
@Microsoft - the issue is not fixed for me. If this is claimed to be working please could exact instructions be provided in a clear way as following the instructions on the Microsoft pages is not yielding results.
Posted by NetDev32 on 2/27/2013 at 8:29 AM
Which actual Source Components have you updated? And what steps have you taken to keep this updated?

Following the same guide provided on the reference site this issue is still occurring.
Posted by Microsoft on 2/12/2013 at 10:40 AM
This issue should now be fixed. We published an update to reference sources.
Please let us know in case your issue is still not fixed.
thanks
-alok shriram
Program Manager
Base Class Libraries
.Net Framework
Posted by Fuad Bagus on 11/15/2012 at 6:37 PM
Any updates yet ??
Posted by JohnCz on 8/28/2012 at 5:35 AM
Well, September is almost here, can you work on this update any slower?
The problem was reported on 10/29/2011 I think. Is the update going to be available in this century?
Why this problem is completely ignored?
Are you aware that VS 2012 and .NET framework 4.5 is already released?
Posted by Pete_O on 7/10/2012 at 3:07 PM
Any news? Pretty ridiculous how long this is taking. Just upload the source - how difficult can it be?
Posted by sugargem on 7/6/2012 at 5:53 AM
Can we assume that after a year of silence that there is no one at Microsoft that knows what the problem is or cares about this functionality?

It would be extremely helpful to me right now.

Could we get any updates on progress? Could we get an intern to fix up referencesource.microsoft.com for information on VS2010!
Posted by Dave Wheeler on 7/5/2012 at 2:50 AM
This is a serious issue for a lot of developers. It was originally highlighted in the MSDN forums over 1 year ago (March 31, 2011).

Could Microsoft please have the courtesy to at least provide us with a progress update from the Visual Studio Product Team and some idea of timescales for getting this fixed?
Posted by Kevin Dance on 5/28/2012 at 6:25 AM
Please fix this. We need to debug!
Posted by Microsoft on 5/9/2012 at 2:01 AM
Thanks for your feedback.

We are rerouting this issue to the appropriate group within the Visual Studio Product Team for triage and resolution. These specialized experts will follow-up with your issue.
Posted by HelgeKlein on 2/8/2012 at 3:25 PM
Please fix this. We need to debug!

More information on this problem:

http://social.msdn.microsoft.com/Forums/en-US/vsdebug/thread/4a5fc801-bc83-4f8a-8623-17ec98418685
and
http://social.msdn.microsoft.com/Forums/en-US/vsdebug/thread/6f22759b-1c64-4025-96c8-b169cb98eba6
Posted by Laurents C. R. Meyer on 11/18/2011 at 11:39 AM
This issue has been reported over six month ago in the appropriate forum:
http://social.msdn.microsoft.com/Forums/en-US/refsourceserver/thread/41388c7b-582b-4e3f-8178-3d38a3c99639

The reference source website is not much, the information on it is adressing visual studio 2008. The entry on the official blog was one year ago and was quite quite late. Is there anyone still responsible for the reference source server, or was the team dismissed due to budget cuts?
Posted by OffTopic on 11/18/2011 at 2:31 AM
This is a also a big issue for us. Currently we use Reflector Pro for debugging, but this solution is not perfect. I really would appreciate if .NET sources are updated to 4.0.30319.233.

thanks
Posted by MS-Moderator08 on 10/31/2011 at 1:55 AM
Thank you for reporting this issue. Could you please attach some screenshots about this issue?
Posted by MS-Moderator01 on 10/29/2011 at 11:45 AM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(http://support.microsoft.com)
Sign in to post a workaround.
Posted by trytryrtyrtyrtytyty on 11/22/2012 at 7:45 AM
Do NOT use Microsoft products
Posted by midspace on 11/21/2011 at 4:53 PM
How about uninstalling the updates?

I was just having this exact issue, except with the WPF 3.5. Trying to debug an low level issue through some textboxes, except I wasn't getting any .PDBs with source files.

My PresentationCore was version 3.0.6920.4016
A quick google on "3.0.6920.4016 KB" linked me to two articles.
Ended up uninstalling update "Update for Microsoft Windows(KB979899)".
A reboot later, PresentationCore was now version 3.0.6920.4000.

Now running Visual Studio, it has downloaded a .PDB with source files.

Whilst these security updates are essential, they certainly put us developers in a bind if they in turn remove our ability to debug necessary code.