Packages.conf versioning

Nov 21, 2011 at 5:13 PM
We are building our Nuget packages on our CI server and deploying them to our internal NuGet. We now use NuGetPowertools to retrieve the dependent NuGet packages before each build. I very much this way of deploying packages but I wonder if it is possible to define only a MAJOR.MINOR.REVISION in projects.conf and it gets the latest build when fetching the packages without having to update project.conf.
Nov 21, 2011 at 5:45 PM

We don't have any support for that today. One of the problems we need to solve with that approach is that restoring packages works without Visual Studio being there. But some package upgrades may require Visual Studio. For example, what if the newer version of the package has new content files, or a new assembly, or Install.ps1 scripts.

The upgrade wouldn't work correctly because we use Visual Studio (more specifically, it's Design Time Environment, aka the DTE) to update project assembly references, add content files, and run the PS scripts.