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

Feature Request: CLI feature update NuGet packages on solution, project, and/or folder level. #6193

Closed
livarcocc opened this issue Nov 17, 2017 · 1 comment
Labels
Functionality:Update The update package feature/command/experience Product:dotnet.exe Resolution:Duplicate This issue appears to be a Duplicate of another issue
Milestone

Comments

@livarcocc
Copy link

From @Kritner on October 23, 2017 18:11

It could potentially be beneficial to have a CLI command that would allow for the updating of NuGet packages from the solution level.

As we add more projects to our solutions, the projects created more recently often (as expected) have more up to date versions of packages. In our case, we are creating several solutions, some of which depend on some library projects. We could go into each solution, and update the packages, but this is extremely time consuming.

Part of the way we were getting around this, was to have an "all" solution, that contained all projects. This would allow the use of the "Manage NuGet packages" dialogue to update all packages at once. At this point however, VS seems to crash based on the number of projects in the "all" solution (in the neighborhood of 100).

It would be extremely useful if a dotnet nuget update command or similar was made available, at either the solution, project, or folder (assuming it could traverse directories) level. I'm not sure if this is such a special potential use case or not, but thought I'd throw it out there.

I'd imagine certain options would be useful such as:

-consolidate (similar to the GUI, determine all packages used, and get them all updated to the same version
-update - updates all nuget packages to the latest version
-update-pre - updates all nuget packages to the latest version, can use pre-release packages rather than only stable.

  • when given a solution file, determine projects in solution, then nuget packages used across projects
  • when given a project file, update only packages pertaining to that project file
  • when given a folder, determine projects contained within folder, and nuget packages for each project.

Thoughts? I couldn't imagine I'm the only one where the "Solution manage nuget packages" from Visual Studio sort of bombs out.

Copied from original issue: dotnet/cli#7886

@nkolev92
Copy link
Member

Thanks reporting this issue @Kritner.

This is a dup of #4103.

Please follow that issue for further updates.

@nkolev92 nkolev92 added the Resolution:Duplicate This issue appears to be a Duplicate of another issue label Nov 17, 2017
@nkolev92 nkolev92 added this to the 4.6 milestone Nov 17, 2017
@nkolev92 nkolev92 added Product:dotnet.exe Functionality:Update The update package feature/command/experience labels Nov 17, 2017
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 Product:dotnet.exe Resolution:Duplicate This issue appears to be a Duplicate of another issue
Projects
None yet
Development

No branches or pull requests

2 participants