How not to change a package's folder name during update

Topics: General
Jul 12, 2012 at 2:12 PM

I asked something similar here, but as nobody answered I'll try to be more concrete.

I have a project with some package as a dependency. Then I go into "Manage NuGet Packages" dialog and do update (from Updates tab). Nuget downloads a new version of the package and put it under "packages" folder into folder with package full name. That name consists of package's Id and version.

As the version changes folder name also changes.

I.e. it was "packages\Newtonsoft.Json.4.5.6" and becomes "packages\Newtonsoft.Json.4.5.7"

That leads to the fact that all project references should be retargeted to new assemblies. NuGet actually does this for me.

I'd like to have static packages name, like "packages\Newtonsoft.Json" without version.

"NuGet.exe Install" allows this via -ExcludeVersion option. But how to do this via VS (UI and PowerShell) during updating?

I have many dev-build with versions like "1.0.0-dev-100", "1.0.0-dev-101" and so on. I don't want that "dev"-versions to be in project referemces paths.


Jul 13, 2012 at 6:24 AM

Unfortunately, that's not possible within VS. We have received many similar requests for version-less folders.

Feel free to vote up this work item:

Sep 10, 2012 at 11:02 AM


I've tried to submit a pull request where you can turn on/off versioned packages in VS but got rejected because it required a discussion. Here is the discussion I've started:

If you would you like to take a look to see if this fills your needs, please vote it up :)