Symbian VS Studio 2010 server does not include source code

Question

I have installed VS Studio 2010 SP1, and there was a time when the initial step worked perfectly. Something has changed, and now that pdb files are loaded, this is the version in which the source code is stripped.

I can't figure out how to get VS to load pdb files that have source code in them. I have the same setup on 2 different machines, and 1 machine loads pdb with the source, and the other one doesn't.

I struggled for hours trying to get it to load the correct pdb files. I can easily check if the files are correct, because the file size is much smaller when there is no source.

A machine loaded with System.Web.pdb source code is 10.860 KB. A machine that boots without a source. The size of System.Web.pdb is 843 KB.

Your help in solving this problem is greatly appreciated.

In addition, please, I did not clear the cache, configure and reset character settings, etc. Files are uploaded and uploaded as characters, not NO source.

C:\Windows\Microsoft.Net\assembly\GAC_32\System.Web\v4.0_4.0.0.0__b03f5f7f11d50a3a\System.Web.pdb: Cannot find or open the PDB file. C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\System.Web.pdb: Cannot find or open the PDB file. C:\SymbolCache\MicrosoftPublicSymbols\System.Web.pdb\46C6DCE3C79A4E65A2B1CEF3033C95931\System.Web.pdb: Symbols loaded. 

Answer 1

This behavior often occurs due to the publication of Microsoft updates in the .NET Framework.

When you use Visual Studio 2010's built-in character configuration (using the "Enable .NET Framework Source Code Stacking" check), you effectively request these two servers:

• http://referencesource.microsoft.com/symbols
• http://msdl.microsoft.com/download/symbols

Not. 1 contains source-supported characters for the .NET Framework (at least parts) and not. 2 contains the source characters for all Windows.

The problem is no. 1 is not updated as fast as not. 2, so when the update comes through Windows Update, you start receiving characters from no. 2 until someone from Microsoft updates. 1. This is pain, but how is it.

You can sort the work around it by unchecking the "Enable the initial step in the .NET Framework" checkbox and configure these paths manually - then you can simply disable (or not add at all). 2, and at least be informed that sources are not yet available.

Or you can disable Windows Update ...