Replies: 1 comment
-
|
I totally agree. It would be nice to have this at the solution level (stored in the solution's nuget.config) rather than defined purely in Visual Studio. It'd certainly be one less step to perform when onboarding a new team member. Perhaps this should be suggested via Visual Studio feedback rather than here on the NuGet github Q&A for more attention. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I love how the nuget.config has
packageSourcesandpackageSourceMapping. 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