How can I use NuGet with Visual C# Express?

Question

How can I use NuGet to add a library package reference, when I have Visual C# 2010 Express?

NuGet doesn\'t come up when I search for it in Tools > Extension Manager.

Answer 1

To install a package in visual studio c# express 2010 use the command line tool nuget.exe. Download nuget.exe from the nuget website add the path to the executable to the windows path environment variable, cd to a place you want you library to be then run it with the library name as an argument.

C:\Code\myprojectdir\myproject>nuget install CommandLineParser
Installing 'CommandLineParser 1.9.71'.
Successfully installed 'CommandLineParser 1.9.71'.

Then just add a reference to the appropriate version of the dll (ie 4.0), in visual studio c# 2010 using project->add reference->browse. Then build the project.

Answer 2

If you have VWD Express installed you can work around this as follows:

1. Save and close your project in c# Express

2. Open the project in VWD Express and use Nuget from there to add your packages

3. Save your project and go back to c# Express

Answer 3

Visit this video: https://youtu.be/8DcANVHLE0o The way is: Download .exe file from nuget.org, and make a folder in %appdata% "NuGet", paste the exe file in the folder, after that open cmd, type cd (the folder adress), and type nuget install (package), the go in the package folder, lib, copy the dll file, and put it as Reference in visual basic

Answer 4

Update (9/12/2012): Good news: Visual Studio Express 2012 for Windows Desktop is now available (here), and it supports NuGet out of the box. Generally speaking, every edition of VS2012 now supports NuGet, so this limitation should be a thing of the past!

---

Original answer:

Microsoft signs NuGet in a way that allows it to work with VWD Express. Ideally, it would also be signed in a way that it works with C# Express (it may have to be a separate build). Unfortunately, we were not able to do this for the initial release (it's more of a challenge than you might think).

Going forward, we will try to enable this scenario. Feel free to file a bug on the NuGet site just to let others who are affected a chance to vote it up!