Skip to content
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

Bulk package update to a specific version #2713

Open
Semax opened this issue May 4, 2016 · 4 comments
Open

Bulk package update to a specific version #2713

Semax opened this issue May 4, 2016 · 4 comments
Labels
Functionality:Update The update package feature/command/experience Priority:3 Issues under consideration. With enough upvotes, will be reconsidered to be added to the backlog. Type:Feature
Milestone

Comments

@Semax
Copy link

Semax commented May 4, 2016

Please consider a situation when a single solution provides a bunch of packages. All these packages have the same version and are used in other solutions in various combinations. More over, each solution may reference a specific version of packages different from the versions used by other solutions. So it would be a great improvement if NuGet UI provided a way to make bulk update of the packages to a specific version (not just to the highest one as it is now). Maybe it would be helpful to introduce a notion of package set so users could mark the desired packages as a set (specific to referencing solution) for subsequent atomical updates.
Thanks.

@rrelyea
Copy link
Contributor

rrelyea commented May 4, 2016

NuGet UI only works across a single solution.
We do have a way to do bulk updates in one solution: solution level package manager/consolidate tab.
We are considering a lineup feature #2572 that may cover some of these scenarios.
Follow that issue.

@rrelyea rrelyea added the Viewed label May 4, 2016
@harikmenon harikmenon mentioned this issue May 4, 2016
@Semax
Copy link
Author

Semax commented May 5, 2016

Ok, thanks. Actually, having a way to select the update mode in UI might also cover some of these cases. I mean those modes which are available for console with Package-Update options -Safe and -ToHighestMinor followed by "to highest" as default.

@fubar-coder
Copy link

Related to issue #1635

@jainaashish
Copy link

@rrelyea this might be related to multiple branches issue we discussed with nVentive the other day.

One good workaround for this is to have common props file which define the version for all the packages which shares similar pattern. And everytime you want to update to a specific version for all such packages, just update it at one place and run restore. it will make sure all the packages are updated to that version.

@jainaashish jainaashish reopened this Feb 2, 2018
@jainaashish jainaashish added this to the Backlog milestone Feb 2, 2018
@jainaashish jainaashish added Type:Feature Functionality:Update The update package feature/command/experience Triage:NeedsTriageDiscussion and removed Viewed labels Feb 2, 2018
@jeffkl jeffkl added Priority:3 Issues under consideration. With enough upvotes, will be reconsidered to be added to the backlog. and removed Pipeline:Icebox labels Apr 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Functionality:Update The update package feature/command/experience Priority:3 Issues under consideration. With enough upvotes, will be reconsidered to be added to the backlog. Type:Feature
Projects
None yet
Development

No branches or pull requests

8 participants