install nuget package visual studio 2008

all you want is to bring down nhibernate.dll so you can write some code against it, and compile it manually using ‘csc /r:nhibernate.dll M圜ode.cs’. But suppose you want to work much more ‘manually’, and not deal with VS or even with a. # Why would you want to use this instead of the Visual Studio integration?įor most users, the Visual Studio integration will be the right choices. Successfully installed 'Castle.Core 2.5.2'. Successfully installed 'Iesi.Collections 1.0.1'. Attempting to retrieve dependency from source. 'Iesi.Collections (≥ 1.0.1)' not installed. The best way to demonstrate it is to just show a sample session. You can also obtain it via NuGet itself by installing the package name NuGet.CommandLine (using Visual Studio). The easiest way to get it is to download it from. This is the same tool that package authors have been using to create packages and upload them to the gallery. Using it couldn’t be any easier, and I’ll walk you through an example. So I’m happy to say that we have now filled this little hole by implementing a new ‘install’ command in our NuGet.exe command line tool. This was unfortunate, because we already had all the plumbing to make it happen, and all it needed was about 10 lines of code to expose this! While we have been planning all along to provide the same experience with NuGet (in addition to the VS experience of course), it’s something that had somewhat fallen off the radar, and it just had not been done. Take a look at Rob Reynolds’s original screencast to see what the Nu experience was about.

In their case, it was based on Ruby Gems, but that is an implementation details. What Nu had was a solid command line driven experience to bring down. If we look back at the early days of NuGet, it was in many ways inspired by the ‘Nu’ project (which members have since joined NuGet). While this is indeed a key scenario, it is important to note that the core of NuGet is completely decoupled from Visual Studio, and was designed with that goal from day 1. Most of the coverage around NuGet revolves against its clean integration to Visual Studio, which makes adding references to packages as easy as adding references to local assemblies.

Install nuget package visual studio 2008