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
I love how the nuget.config has packageSources and packageSourceMapping. That really simplifies people getting started with my projects without having to do custom setups in their GUI of choice.
But .. what about symbol file locations? Sure, Visual Studio (not sure about Rider, etc) auto checks nuget.org for symbols if the nuget package has snupkg's up on nuget.
But it all breaks down terribly if we are using private nuget repositories to store out nuget packages.
We now have to manually add in the Symbol Server to our GUI, like this:
So ... would be really awesome if we could have the ability to define where the symbol packages also exist . We already tell the program where our private nuget repo is. Why not where the private symbol server, is?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I love how the nuget.config has
packageSources
andpackageSourceMapping
. That really simplifies people getting started with my projects without having to do custom setups in their GUI of choice.But .. what about symbol file locations? Sure, Visual Studio (not sure about Rider, etc) auto checks nuget.org for symbols if the nuget package has snupkg's up on nuget.
But it all breaks down terribly if we are using private nuget repositories to store out nuget packages.
We now have to manually add in the Symbol Server to our GUI, like this:
So ... would be really awesome if we could have the ability to define where the symbol packages also exist . We already tell the program where our private nuget repo is. Why not where the private symbol server, is?
Beta Was this translation helpful? Give feedback.
All reactions