1. Open a solution with multiple projects, exactly one of which references the jQuery NuGet package. Ensure it references jQuery 1.9.1.
2. On the project that includes the jQuery package, open packages.config and add __allowedVersions="[1.9.1,2)"__ to the jQuery line ([why?](http://stackoverflow.com/a/16151570/145173)).
3. From the main menu, click "Manage NuGet Packages for Solution".
Notice that the package manager window displays an update for jQuery 2.0.0. This should not be displayed because the update is not allowed.
Comments: Are the projects' allowedVersions not checked until later for performance reasons? Especially with the recent addition of the "Update All" button, it would simplify the user experience to omit non-updatable packages or display them with an indication that they won't be updated (in lieu of their Update button). With the jQuery 2.0 release, this may be a common use case for a good while until IE8 market share dies down a bit more.
2. On the project that includes the jQuery package, open packages.config and add __allowedVersions="[1.9.1,2)"__ to the jQuery line ([why?](http://stackoverflow.com/a/16151570/145173)).
3. From the main menu, click "Manage NuGet Packages for Solution".
Notice that the package manager window displays an update for jQuery 2.0.0. This should not be displayed because the update is not allowed.
Comments: Are the projects' allowedVersions not checked until later for performance reasons? Especially with the recent addition of the "Update All" button, it would simplify the user experience to omit non-updatable packages or display them with an indication that they won't be updated (in lieu of their Update button). With the jQuery 2.0 release, this may be a common use case for a good while until IE8 market share dies down a bit more.
