We have TeamCity setup to create a NuGet package and a symbol source package for an internal component. The symbol source packages correctly contains the dll's, pdb's and source code.
Once TeamCity has created the packages, they are published to our NuGet / SymbolSource server.
In ReSharper I have configured 'External Sources' to be 'Navigation to Sources'. The NuGet package has been added to a project, but when navigating to sources, the ReSharper output shows this error:
PdbNavigator: Downloader:
http://symbolserver/SymbolSource/WinDbg/pdb
::MyLib.dll::3A9F94B78ED243228DC8CB98D71483D615 -> Ok (cached) PdbNavigator: No debugging information found on symbol servers for MyLib, Version=3.2.5123.12213, Culture=neutral, PublicKeyToken=3111e51d1da2afdf
The PDB is being successfully pulled down, but ReSharper is unable to step into the sources. When a debugger is attached, source files can be correctly stepped into so I assume this is a ReSharper configuration issue. How can I get 'Navigate to > Sources from symbol files' to work in ReSharper?
There is a bug in ReSharper 8 that can cause it to download the pdb, but then not process it, so it doesn't see the symbols and so can't navigate to the source. This mostly manifests in a new project (or at least, the easiest way to recreate it is with a new project). Closing and reopening the solution uses causes the navigation to succeed, because ReSharper now knows about the pdb file, can find the symbols and load the source.
Here's the bug details: http://youtrack.jetbrains.com/issue/RSRP-406276. It's just been fixed and will be included in the next 8.2 EAP and will be part of the 8.2 release.