May 23, 2013 at 11:08 AM
Edited May 23, 2013 at 11:09 AM
we have encountered different update behaviour between Package Console Manager in VS and nuget.exe . I was wondering whether somebody could advice whether this is a correct behaviour on both sides or it is a bug. I'm using nuget 2.5.40416.9020
My network share repo contains the following packages
packages.config for my project contains the following reference
<package id="Core.Logging" version="3.2.0-development-1000" targetFramework="net20" />
In VS (Package Manager Console Host Version 2.5.40416.9020)
If I run: update-package Core.Logging -safe
Then packages.config will be updated to Core.Logging version 18.104.22.1680
I find this expected behaviour as I do not specify -includePrerelease option and I asked for safe update (keeping major&minor versions the same)
However using nuget.exe (NuGet Version: 2.5.40416.9020)
If I run: nuget update mysolution -Safe -id Core.Logging
Then packages.config will be updated to Core.Logging version 3.3.0-development-1001
Not only the update is not "safe" but also a pre-release version of the package is installed.
Is there a way how to get the same behaviour as in the VS console?
Many thanks for your help,