Welcome to the Inedo Forums! Check out the Forums Guide for help getting started.
If you are experiencing any issues with the forum software, please visit the Contact Form on our website and let us know!
VS 2017 not finding symbol server
-
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.
-
Hello Richard,
Does this visiting this URL directly in your browser (presumably replacing
redactedwith the actual names) return a "not found" error or some other error?http://nuget.redacted.com/symbols/redacted/redacted.dll/8AA07D8A44496EE83C864487609F24C31/redacted.pdb -
It returns a 404 with body "The requested file was not found."
-
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 :(
-
Are you referring to the "Debugging information: portable" option under "Build -> Advanced Build Settings -> Output" in project settings?
-
Hello Rich,
Yes, the new format is "portable PDB", and it is not yet supported by ProGet's symbol or source server.
-
Ya, I'm not using that format. I'm using "full" format.
-
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
-
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.
-
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.
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login