The end scenario I am trying to tackle is debugging a NuGet package we develop and publish to our feed in Azure DevOps, when referenced from a different package. E.g. package A
is released via a pipeline to an Azure DevOps NuGet feed. I am using it from package B
, and want to be able to debug code inside A
using Visual Studio.
Problem is dotnet pack --include-symbols
does not include A
's symbols into the .nupkg. Instead, it puts them into .symbols.nupkg, which are not getting pushed by dotnet push
to our DevOps feed. There's a conflict unless I explicitly exclude .symbols.nupkg:
Response status code does not indicate success: 409 (Conflict - The feed already contains 'A 0.0.0-REDACTED'. (DevOps Activity ID: A7965FB9-B458-43F9-8973-FD0B6E7F1138)).
The question is twofold:
- Is there a supported and well documented way to get debug symbols (and, preferably sources) automatically loaded in Visual Studio for a NuGet package build by CI in Azure DevOps?
- If what I am trying to do is the correct way, how do I deal with .symbols.nupkg?