How to set up 'Sources from Symbol Files'? Follow

Hello,

What's written in View -> Output -> Show output from: ReSharper after unsuccessful navigation?

Hi!

I found the following two lines:

PdbNavigator: Downloader: http://referencesource.microsoft.com/symbols/mscorlib.pdb/A21F40D38EAB4B64B449E50DE8F5A3431/mscorlib.pdb -> ok, 9,57 MB
PdbNavigator: No debugging information found on symbol servers for mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089

Thanks,

Malte

Hmm, could you send me (Leonid.Shalupov@jetbrains.com) the log from ReSharper -> Options -> External sources -> Sources from symbol files -> Advanced -> Show current path settings and pdb files binding?

Did you guys figure this out?  I am having a similar problem that's stopping me from seeing the sources.  Here's the info from View->Output->Resharper:

PdbNavigator: Searching for 'System.DateTime' type sources in c:\projects\MyProduct\bin\Release\mscorlib.pdb\E47AF49130474776AF6C5994C50088421\mscorlib.pdb
PdbNavigator: Downloader: http://referencesource.microsoft.com/source/dotnetfx35sp1_3053/1.3/DEVDIV/depot/DevDiv/releases/whidbey/netfxsp/ndp/clr/src/BCL/System/DateTime.cs/1/DateTime.cs -> The remote server returned an error: (400) Bad Request.
PdbNavigator: No sources found in debugging information for 'System.DateTime' in assembly 'mscorlib, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089'

You don't have mentioned problem. That's just referencesource site is down (this part).

Yep, got the same thing with R# 5.1

I cannot see the source if the project is targetting .NET 4

However, NET 3.5 works fine on the same installation

Other mentions of the prob :

http://stackoverflow.com/questions/2840327/resharper-5-external-sources-in-a-net-4-0-project
http://stackoverflow.com/questions/2925149/how-to-see-net-library-source-code-with-resharper-5-and-visual-studio-2010

Regards, Tom Pester

The issue was resolved by registering COM library msdia90.dll on target machine. Unfortunately Microsoft changed DIA SDK API in Visual Studio 2010 which R# uses, so navigation into sources from symbol files won't work on machines with just VS2010, if VS2008 installed it works fine.

So, please regsvr32 msdia90.dll in such cases. Not sure whether Microsoft allows to distribute msdia90.dll, so no link here...

I believe it's a different case. I commented those questions on stackoverflow:

Microsoft released sources for .NET 4 release, so R# have to work just fine. Some debugging information may be found in View -> Output -> ReSharper after unsuccessful navigation. Sometimes R# can't download sources or symbols files because of server errors on referencesource.microsoft.com side.

I found that if I switched my project to 4.0, I could download and view the sources.  I switched back to 3.5 and was back to the errors I posted above.  Basically, the opposite of what Tom experienced.

Tom, do your working urls for 3.5 (from View->Output->Resharper) match my non-working urls (see above)?  If so, then I guess the referencesource server just sucks sometimes.

Strangly enough it doesn't show it it attempted to contact the source server :

PdbNavigator: Searching for 'System.Web.HttpResponse' type sources in C:\Users\Tom\AppData\Local\Temp\SymbolCache\MicrosoftPublicSymbols\System.Web.pdb\59FA2087AC2D4BB2935A02D70EB1C5971\System.Web.pdb
PdbNavigator: No sources found in debugging information for 'System.Web.HttpResponse' in assembly 'System.Web, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'

It assumes its already in the cache? This is just a tought because I don't have to insight to diagnose a possible cause just yet.

Still no luck in navigating to the source when targetting 4.0

As it happens I have vs2008 and vs2010 on the this machine.

Debugging the ms source in 3.5 works, in 4.0 it fails (I just posted the R# message above in this thread)

I have msdia90.dll on 2 locations :
C:\Program Files (x86)\Microsoft Visual Studio 9.0\Common7\Packages\Debugger\msdia90.dll
C:\Program Files (x86)\Common Files\microsoft shared\VC\msdia90.dll

The first is VS2008 as I understand it.

Do you suggest that I register msdia90.dll (regsvr32) again?

Can I send you a log that is more meaningful?

Regards, Tom

Just to be clear. This is something that the team at R# can fix or should we end users do anything to resolve the issue? I prefer to wait for a fix/new release of R#. I have messed up enough dev boxes in my life ;)

I found and fixed one bug in .NET 4 symbols support. It'll be available in ReSharper 5.1.1 maintenance release soon

Just to be clear this thread is a mix of three different issues:

• Temporary unavailability of referencesource.microsoft.com
  It just happens from time to time.
  Can be diagnosed in View -> Output -> ReSharper window as non-200 HTTP error codes as result of pdb downloading.
  
• Broken navigation into .NET 4 sources, NET 3.5 works
  R# bug, Will be fixed in 5.1.1 maintenance release
• Unavailability of msdia90.dll on clean VS2010 installs
  Diagnostics: VS2010-only machine and no navigation to .NET 4 and 3.5 sources.
  No fix in 5.1.1. Stay tuned.
  Workaround: regsvr32 msdia90.dll, where msdia90.dll from VS2008 install

All: thanks for the feedback!

"Broken navigation into .NET 4 sources" and "Unavailability of msdia90.dll on clean VS2010 installs": has been fixed in ReSharper 5.1.1, see http://www.jetbrains.com/resharper/download/index.html for download

I'm running 5.1.1 (5.1.3000.12) on VS.NET 2010 (10.0.31118.1) and am still having this issue.

I am also running Reflector.NET, and found that there were conflicts with it and the R# source discovery process, so I had turned off the Metadata Viewer... however, when I disable the External Sources functionality on R# completely, Reflector.NET has no problem disassembling.

Should I attach my current path settings and pdb files bindings?

Edit: Reflector.NET does NOT disassemble the .NET 4.0 objects either.

Hello Richard,

This is a known compatibility problem, but we won't be able to fix it in
the nearest future. Thank you!

Andrey Serebryansky
Senior Support Engineer
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"

I'm running 5.1.1 (5.1.3000.12) on VS.NET 2010 (10.0.31118.1) and am
still having this issue.

I am also running Reflector.NET, and found that there were conflicts
with it and the R# source discovery process, so I had turned off the
Metadata Viewer... however, when I disable the External Sources
functionality on R# completely, Reflector.NET has no problem
disassembling.

Should I attach my current path settings and pdb files bindings?

---
Original message URL:
http://devnet.jetbrains.net/message/5291710#5291710

Um... the compatability issue is?

I mentioned Reflector.NET because I thought it was able to disassemble the files. Turns out not. I already know about the fact that R#/Reflector don't play well together... however, my comment was mostly to indicate that though I've got the supposedly fixed version of R#, I still can't make R#-only disassembly, or Reflector.NET-only disassembly, work.

So, let's say I remove Reflector.NET from the equation, and state: I'm still having this problem with 5.1.1 (5.1.3000.12). Suggestions?

I have the same issue - for me, the site is always down. I don't know what changed, but I used to be able to access the symbol sources.

Here's my info:

JetBrains ReSharper 5.1 C# Edition
Build 5.1.3000.12 on 2011-01-28T05:05:56

Licensed to: *****
Plugins: 3
#1. “StyleCop for ReSharper 5.1” v5.1.14810.3 by “StyleCop for ReSharper Development Team - http://StyleCop.ForReSharper.org”
#2. “Gallio Test Runner” v3.2.0.0 by Gallio
#3. “Settings Manager” v2.2.0.0 by “Roman "4ux-nbIx" Novitsky”
Visual Studio 10.0.31118.1.

PdbNavigator: Downloader: http://referencesource.microsoft.com/symbols/System.pdb/228FF0435DAA43B38332124B59E526641/System.pdb -> The remote server returned an error: (400) Bad Request.
PdbNavigator: Searching for 'System.Net.IPAddress' type sources in C:\DotNetSymbolCache\System.pdb\228FF0435DAA43B38332124B59E526641\System.pdb
PdbNavigator: No sources found in debugging information for 'System.Net.IPAddress' in assembly 'System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089'