1

I'm quite new to Continous Integration and I'm trying to make some scripts for NuGet. It seems that the only way to make such scripts is the NuGet command line commands.

The NuGet command line doesn't offer so many functionality like the Package Manager Console in VS2010.

What is the usual way of do such scripting?

I need simple operations such as changing the version, updating the packages, etc...

Thanks!

Rafa
  • 2,328
  • 3
  • 27
  • 44
  • This question is very hard to answer as it is very broad and difficult to tell exactly what is being asked. Could you clarify it with maybe an example of what you tried in updating a package and the error you received? – Goyuix Aug 29 '13 at 19:40
  • 1
    @Goyuix: you're right, my english is also not so good. But basically, I try to use the powershell cmdlet "Update-Package" from the package manager console in a normal PowerShell console and it is not available. I've tried to find where are these commands and I cannot find them. – Rafa Aug 30 '13 at 07:25
  • 2
    You can import Powershell packages - `Import-Module -Name .` There is a similar question asked earlier. Please check the following link (might help) - http://stackoverflow.com/questions/12884282/use-nuget-powershell-commandlets-from-outside-visual-studio – Nikhil Gupta Aug 30 '13 at 12:55
  • If you don't like the command line reference, you can create a custom MSBuildTask. The Custom MSBuild Task is just a fancy way to call the command line.......you set properties on the Task....and then the internal code wires up all the command line stuff super nice. – granadaCoder Sep 03 '13 at 20:22

1 Answers1

0

Only for completion and to share my experiences, I will tell you what I did:

I used some of the command line tools, the functionality is quite limited, but for some easy tasks is ok.

For more complex tasks, the powershell snippets are the best option. They have to be integrated in Visual studio and can be only used within Visual Studio. It is possible to use tham also as a script, but it is necessary a lot of work to make it work.

At the very end, I'm not using nuget anymore, it doesn't really fits the needs of a software development team for internal work. It is quite good for releasing new version of your software to the internet but this is all. It cannot really be compared with MAVEN.

Rafa
  • 2,328
  • 3
  • 27
  • 44