Nuget installs old versions of package dependencies by default.
This requires an "update-package" right after "install-package".
Examples:
Create a new empty asp.net mvc application and:
Install-Package Microsoft.AspNet.Web.Optimization
- Installs WebGrease 1.3.0, although 1.5.2 is available
Install-Package Backbone.js
- Installs jquery 1.7.2, although 2.0.3 is avalable
- Installs underscore 1.3.3, although 1.5.1 is available
In both cases, doing an "update-package" upgrades the packages to the latest version after install.
If versions are not specified, the default should always be installing the latest version.
VS 2012 Professional, Nuget 2.6.40627.9000
Comments: So, the issue seems to be with every package in the nuget directory? Seems quite strange that you say "I work with any version abode 2.0" and even though hundreds of security packages have been released after I created the package, I'll keep installing the first one from five years ago. Also, this makes the default behavior very inconsistent, as I said in the previous post. If you just install another package that depends on the same library, it will upgrade versions without asking any questions. If the intention was to avoid breaking stuff, some warning should be shown. There is really something wrong here if that is the default. This is not how any package manager works.
This requires an "update-package" right after "install-package".
Examples:
Create a new empty asp.net mvc application and:
Install-Package Microsoft.AspNet.Web.Optimization
- Installs WebGrease 1.3.0, although 1.5.2 is available
Install-Package Backbone.js
- Installs jquery 1.7.2, although 2.0.3 is avalable
- Installs underscore 1.3.3, although 1.5.1 is available
In both cases, doing an "update-package" upgrades the packages to the latest version after install.
If versions are not specified, the default should always be installing the latest version.
VS 2012 Professional, Nuget 2.6.40627.9000
Comments: So, the issue seems to be with every package in the nuget directory? Seems quite strange that you say "I work with any version abode 2.0" and even though hundreds of security packages have been released after I created the package, I'll keep installing the first one from five years ago. Also, this makes the default behavior very inconsistent, as I said in the previous post. If you just install another package that depends on the same library, it will upgrade versions without asking any questions. If the intention was to avoid breaking stuff, some warning should be shown. There is really something wrong here if that is the default. This is not how any package manager works.