Closed kdcllc closed 4 years ago
I've done a bit more reading, and there's the (ms-recommended) option of generating a separate .snupkg
file stored on nuget's symbol server, which can cut down on restore times for regular .nupkg
files. Thoughts?
I've done a bit more reading, and there's the (ms-recommended) option of generating a separate
.snupkg
file stored on nuget's symbol server, which can cut down on restore times for regular.nupkg
files. Thoughts?
This is true. This is the preferred way is to deploy to nuget symbol server. As a library developer if you would like to make debugging available through different tools then this solution won't work. Thus including code and debug info in the nuget package provides the needed coverage.
The fix to embedded the pdb which will allow for sourcelink to work again.