I have a folder on my server that hosts my nuget packages. These packages do not contain source code or symbols (PDBs). This works well.
Recently I have set up another folder on my local server to host the symbols files from the assemblies in my nuget packages.
I have added the path to the symbols folder to visual studio and when I place the PDB files in the folder they are loaded correctly in VS and I am able to step into the code when debugging. If I look at the symbol load information in VS I can see that the PDB was downloaded from the symbols folder on my server, confirming that everything is working correctly.
I believe the preferred way to do this sort of thing is to have nuget create a symbols package at the same time as creating the nuget package and I would like to move to this way of working.
Creating the symbols and nuget package is not an issue. The issue is that when I push (using nuget) the symbols package to my symbols folder VS is not able to use it. When I try to step into my nuget package VS tries to find the PDB and I can see that it looks in my symbols folder but it can not find the PDB, which makes sense because it is contained inside a nuget symbols package.
Can anyone explain what I am missing?