9

Closed

Be able to update package references from outside visual studio via cmd prompt or powershell

description

In a CI situation, it is very desirable to be able to script and automate the updating of a solution / project's package references to the 'latest'.

Latest could mean the highest package version, with respect simver. i.e. "Latest 1.4." or "Latest "

The user story is that in a large high flowing project, generating lots of assemblies and packages, it is requirement to know as soon as possible of potential compilation breaks using a CI server. Particularly with long and potentially complex dependency chains.

In order to do this NuGet will need to be able to update the references without relying on Visual Studio automation. Altering code is not required or expected.

Related:
Closed May 17, 2011 at 9:49 PM by Haacked
According to the person who opened it (thanks!), this is a dupe of http://nuget.codeplex.com/workitem/818

comments

Haacked wrote Mar 31, 2011 at 4:47 PM

Isn't this a dupe of 818? It's not a trivial matter so it may be low on our priority list because of concern over maintaining two different ways to accomplish the same tasks (modifying csproj in and out of VS).

What would help us would be to flesh out what the user experience would look like. For example, what commands would you want to run, etc?

LeRoyAtCodePlex wrote Apr 7, 2011 at 11:01 AM

++ that would be really nice to have.

damianh wrote Apr 11, 2011 at 12:41 PM

Phil, this could be considered a dupe of 818. Had a discussion David Fowler on twitter where he said I should file the issue as it's a specific use case.

I will get back to you on specfically what I'd like to be able to do and how it may look.

mmisztal1980 wrote Apr 12, 2011 at 7:20 PM

this is would be extremely beneficial.