VS 2017 not finding symbol server

[Guest]

Navigated to the symbol server URL in a browser and confirmed / followed all of the steps on your custom 404 page. I've configured all the VS settings specifically as mentioned on the custom 404 page. Still having no luck loading symbols. When I browse to the package in the feed, it shows that source and symbols are available and I can click "view" and see the indexed pdb file. Both src files and .pdg are downloaded when I click Download from that same page.

VS is showing the following symbol load information:

SYMSRV: C:\Users\redacted\AppData\Local\Temp\SymbolCache\redacted.pdb\8AA07D8A44496EE83C864487609F24C31\redacted.pdb - file not found
SYMSRV: C:\Users\redacted\AppData\Local\Temp\SymbolCache\redacted.pdb\8AA07D8A44496EE83C864487609F24C31\redacted.pdb not found
SYMSRV: http://nuget.redacted.com/symbols/redacted: not available
http://nuget.redacted.com/symbols/redacted: Symbols not found on symbol server.

Product: ProGet
Version: 4.7.11

[Guest]

If you followed all of the steps, and you're able to download symbol and source files from ProGet, then it sounds like ProGet is functioning as expected.... which means the problem is a VS configuration, or maybe using a cached package, or something to that

Do note that configuring VS can be tricky, so make sure to very closely check and double-check that every box in the tutorial is followed.

[Guest]

I doubt it's a caching problem as you can see that it failed to find any symbols in the cache, and then failed to find the symbol server. Will look for another package manager to try so that I can verify whether it's ProGet or VS causing the problem.

[Guest]

Hello Richard,

Does this visiting this URL directly in your browser (presumably replacing redacted with the actual names) return a "not found" error or some other error?

http://nuget.redacted.com/symbols/redacted/redacted.dll/8AA07D8A44496EE83C864487609F24C31/redacted.pdb

[Guest]

It returns a 404 with body "The requested file was not found."

[Guest]

Do note that, the newer PDB format (used primarily by DNC packages) is not supported yet. We are still trying to figure out a way to rewrite the SRCSRV entries in it but it doesn't appear to be easily-doable :(

[Guest]

Are you referring to the "Debugging information: portable" option under "Build -> Advanced Build Settings -> Output" in project settings?

[Guest]

Hello Rich,

Yes, the new format is "portable PDB", and it is not yet supported by ProGet's symbol or source server.

[Guest]

Ya, I'm not using that format. I'm using "full" format.

[Guest]

Unfortunately we're not sure of any further debugging/diagnosing steps within ProGet software. If ProGet indexes the symbol, then you will see it listed on the package page and it will be transmitted as a file when requested via URL.

If the symbol cannot be downloaded by visual studio, it most likely is configured incorrectly, the symbol is not referenced in your DLL properly, or there is something else inbetween that is preventing the request from being fulfilled.

There are a whole bunch of symbol serving troubleshooting posts, so I would suggest to try reading through those. Sometimes it's a particular build configuration, or local caching of a dll. You can try to attach fiddler, use different symbol packages, etc.

Please post what the problem was once you discovered it, so other folks can find it

[Guest]

I was having a similar issue until I checked "Enable .NET Framework source stepping" in the Debugging->General options. When I checked that setting, VS immediately began downloading symbols, not just for the .NET Framework, but for all the packages in my solution. Afterward, I was able to debug into the package source as expected.

[Guest]

Surfing Pikachu,

That was one of the steps I mentioned in my original post. Did not work for this issue.

Alana,

Already attached Fiddler before original post. Just showed 404's for symbol requests. Downloading the package locally allows the symbols to be found; but using ProGet's symbol server doesn't work.