-
Notifications
You must be signed in to change notification settings - Fork 258
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update NuGets included through Directory.Build.props #10850
Comments
fyi @JonDouglas - Something to be aware of. |
Example repo here https://github.com/f2calv/vs-nuget-issue |
You could give the user either the choice of updating the file in which the |
/cc @martinrrm @jeffkl to consider for 17.4+ |
Related to #9018 |
Its almost 2 years ... so any updates on this? |
Instead of Ref: https://learn.microsoft.com/en-us/nuget/consume-packages/central-package-management |
Updating Directory.Packages.props works today, so if you're using CPM, that should already work. |
This issue has been moved from a ticket on Developer Community.
[severity:It's more difficult to complete my work]
I have a
Directory.Build.props
file in solution folder that includes some NuGets in all of my projects. It works great, but when I'm updating said NuGets (by opening "Manage NuGet Packages for Solution"), VS just adds new version into all of the projects files and doesn't even update the original NuGet reference inDirectory.Build.props
.Expected behavior is that VS updates version of
PackageReference
where thatPackageReference
is defined instead of creating a new one.Some NuGets just needs to be added in all projects (like StyleCop or Xamarin.Forms), so it would be great if VS had a full support for such use case.
Currently I have to update version in
Directory.Build.props
manually.Original Comments
Feedback Bot on 5/9/2021, 11:00 PM:
We have directed your feedback to the appropriate engineering team for further evaluation. The team will review the feedback and notify you about the next steps.
Original Solutions
(no solutions)
The text was updated successfully, but these errors were encountered: