Source Server not working when "Strip symbol files" option is turned off

We're building our libraries using TeamCity, and publish nuget packages together with the symbols and source files to ProGet.
When downloading a package from ProGet (both manually and via Visual Studio), the package folder contains the .pdb files as well as the source files.

I've followed all the articles I found on the topic and configured Visual Studio to support source server from ProGet, but it seems that as long as the feed is defined to not strip Symbols on download, Visual Studio doesn't load the sources correctly and I can't debug into the code.
As soon as I turn that feature off, everything works fine.

My issues is that I want the .pdb files to be downloaded so that I can include them in the released version (when deploying to a production server). we find that it's much easier to debug when the .pdb files are deployed together with the application.

Is there any way to achieve source server debugging when "Strip Symbols on download" is turned off?

Thanks

Product: ProGet
Version: 3.6.1

If you want to ship .pdb files in your NuGet packages, then you will need two separate feeds (one for symbols/source, one for packages).

A .pdb file is a symbol file, so if you include it your package, then Visual Studio will use that file instead of using an external symbol server (i.e. ProGet) to find those symbols.

Symbol files contain a pointer to a source server, so if you aren't using ProGet's symbol server to get that symbol file, then Visual Studio won't be able to go to ProGet's source server to get your source.

This is why these files are stripped from packages by default.

Thanks for the quick answer Alana,

I'm not that sure how to accomplish what you suggested, assuming I have a separate feed for symbols and a separate one for packages, how would I get the .pdb files into my release build?

Create a debug/symbols feed that has the feature enabled and strips the symbols, and a release feed that doesn't strip the symbols.

OK, but that means I'll have to either manually change the feed when building for deployment, or use a separate build server that is always configured for the release feed.
Correct?

Just push the same package twice, to two different feeds; one used by developers for Visual Studio debugging, and the other used on your build server when integrating NuGet packages.

I see, while that works for some projects, not all of our projects uses a build server which complicates the process of deployment.

Thanks