Nuget install support for not specifying a version

Oct 27, 2011 at 12:27 AM

We are publishing a few internal nuget packages to a fileshare and pulling them down into our projects that way, however we would like to be able to leave the version off in the packages.config and let it always default to the latest published version of our package. The nuget install command currently enforces the presence of a version attribute in the package config entries, and the update command doesn't work against a single packages.config that isn't side by side a .csproj file. It would be nice if we could support our scenario using the actual nuget.exe but due to its current behavior we had to roll our own PackageUpdater.exe that uses the Nuget.Core api to allow us to leave off the version attribute and have it default to just trying to pull the latest version it can find.