In the Nuget Packages Manager screen for solution, in the "Updates" list, when selecting a package to update, all the projects when the package is top-level AND transitive are automatically selected.
Clicking the Update button (underneath the Uninstall button) will update the package reference for the top-level registration, but also add a package reference in all the projects where the package is used as a transitive dependency. Which is not the intended use of transitive dependencies.
I would expect to only have the project where the dependency is a top-level one to be selected automatically.
The solution I'm working with a .NET Framework 4.8 solution, using PackageReference and with SDK-style projects.
PS: when updating multiple packages at once, by selecting them in the package list of the Update tab, and clicking the "Update" button located on top of that list, only the projects where the dependencies are top-level are updated, which is the intended behavior.
Original Comments
Feedback Bot on 28/10/2024, 00:10 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.
This issue has been moved from a ticket on Developer Community.
In the Nuget Packages Manager screen for solution, in the "Updates" list, when selecting a package to update, all the projects when the package is top-level AND transitive are automatically selected.
Clicking the Update button (underneath the Uninstall button) will update the package reference for the top-level registration, but also add a package reference in all the projects where the package is used as a transitive dependency. Which is not the intended use of transitive dependencies.
I would expect to only have the project where the dependency is a top-level one to be selected automatically.
The solution I'm working with a .NET Framework 4.8 solution, using PackageReference and with SDK-style projects.
PS: when updating multiple packages at once, by selecting them in the package list of the Update tab, and clicking the "Update" button located on top of that list, only the projects where the dependencies are top-level are updated, which is the intended behavior.
Original Comments
Feedback Bot on 28/10/2024, 00:10 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.