You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The readme was recently changed to use the new NuGet symbol packages (.snupkg) instead of embedding the PDB in the main NuGet package. While this new symbol server is nice, it has a few disadvantages:
It only supports portable PDBs (SourceLink itself supports all PDB formats)
It requires VS 2017 15.9 to build or to consume the symbol packages (SourceLink only requires 15.3)
It requires the user to manually add the NuGet symbol server in the VS settings (embedded symbols don't require any settings)
In my opinion these requirements should be listed in the readme, otherwise users (both library authors and consumers) might wonder why SourceLink isn't working for them.
Maybe even mention both ways - embedded PDB files and the NuGet symbol server - to give the library author the choice.
The readme was recently changed to use the new NuGet symbol packages (.snupkg) instead of embedding the PDB in the main NuGet package. While this new symbol server is nice, it has a few disadvantages:
In my opinion these requirements should be listed in the readme, otherwise users (both library authors and consumers) might wonder why SourceLink isn't working for them.
Maybe even mention both ways - embedded PDB files and the NuGet symbol server - to give the library author the choice.
Note that the official open source library-guidance also still recommends embedded PDB files over the new NuGet symbol server.
The text was updated successfully, but these errors were encountered: