The build of the .NET Framework that we recently released source for was 2.0.50727.1433, which was the VS2008/.NET 3.5 RTM build. A small change was made to the Framework after that, and this new version, 2.0.50727.1434, was then delivered to Windows Server 2008 and Windows Vista SP1.
Since the source and symbols have to exactly match what's running on a developer's machine, this meant that customers running these new OS releases lost the ability to access the Reference Source for the parts of the .NET Framework that we've released. The new symbols and source have now been deployed for the following:
The rest of the released source/symbols weren't updated.
PingBack from http://www.biosensorab.org/2008/02/15/net-framework-source-symbols-available-for-windows-server-2008-windows-vista-sp1/
Hmm, I just installed Windows Server 2008 and VS 2008, and I cannot load the symbols (this worked just fine on Win 2003). When try to load the symbols (for mscorlib), VS just hangs for a while, and then eventually it comes back and asks for the path to the symbol file.
It seems that it cannot find the 1434 version of the symbol files.
Is the source server broken today? I'm having a whole heap of problems I haven't had before...
Hey guys - just saw this -- are you still having problems? I note that you posted within minutes of each other so I suspect there was a server hiccup. Sorry for the inconvenience, on my end the servers look okay now (a week later :-/ )
In mid January the first release of the .NET Framework 3.5 reference sources occurred. In mid February
[update 5/11/8 added .NET 3.5 SP1, various hotfixes and additional note about "what is the CLR"]