3
Vote

Enable solution-wide package install for a specific package version

description

It is currently not possible to update the entire VS solution to a specific version of a NuGet package.

This is particularly painful in light of jQuery decision to develop two "current" versions, 1.x and 2.x, in parallel. The 2.x line of jQuery only works with modern browsers and so is not appropriate for most web sites, however, that is the only version showing up as upgrade target in NuGet.

One can update to a specific package version one individual project at a time, but it is not possible to update all projects in a solution, making the process much more cumbersome and error prone that it should be.

Please consider addressing this scenario as a priority, especially given that jQuery is not part of standard VS templates.

comments

danbolger wrote Jun 22, 2013 at 12:04 AM

Another slightly less painful workaround is to put the previous version of the package in a local package source (you can register a new package source via the settings button in the lower left of the package manager dialog), and then select that package source in the package manager dialog when searching.