Install and manage NuGet packages using the console in Visual Studio
Instructions for using the NuGet Package Manager Console in Visual Studio for working with packages.
The Package Manager Console is a PowerShell console within Visual Studio used to interact with NuGet and automate Visual Studio. You can access the Package Manager Console from within Visual Studio by going to Tools - Library Package Manager - Package Manager Console. Visual Studio provides the Package Manager UI and the Package Manager Console, through which you can run most NuGet operations. Visual Studio On Mac, certain NuGet capabilities are built-in directly.
The NuGet Package Manager Console lets you use NuGet PowerShell commands to find, install, uninstall, and update NuGet packages. Using the console is necessary in cases where the Package Manager UI does not provide a way to perform an operation. To use
nuget.exe CLI commands in the console, see Using the nuget.exe CLI in the console.
The console is built into Visual Studio on Windows. It is not included with Visual Studio for Mac or Visual Studio Code.
For example, finding and installing a package is done with three easy steps:
Open the project/solution in Visual Studio, and open the console using the Tools > NuGet Package Manager > Package Manager Console command.
Cobalt offline for mac. Find the package you want to install. If you already know this, skip to step 3.
Run the install command:
[!Important]All operations that are available in the console can also be done with the NuGet CLI. However, console commands operate within the context of Visual Studio and a saved project/solution and often accomplish more than their equivalent CLI commands. For example, installing a package through the console adds a reference to the project whereas the CLI command does not. For this reason, developers working in Visual Studio typically prefer using the console to the CLI.
[!Tip]Many console operations depend on having a solution opened in Visual Studio with a known path name. If you have an unsaved solution, or no solution, you can see the error, 'Solution is not opened or not saved. Please ensure you have an open and saved solution.' This indicates that the console cannot determine the solution folder. Saving an unsaved solution, or creating and saving a solution if you don't have one open, should correct the error.
Open the console in Visual Studio using the Tools > NuGet Package Manager > Package Manager Console command. The console is a Visual Studio window that can be arranged and positioned however you like (see Customize window layouts in Visual Studio).
By default, console commands operate against a specific package source and project as set in the control at the top of the window:
Selecting a different package source and/or project changes those defaults for subsequent commands. To overrride these settings without changing the defaults, most commands support
To manage package sources, select the gear icon. This is a shortcut to the Tools > Options > NuGet Package Manager > Package Sources dialog box as described on the Package Manager UI page. Also, the control to the right of the project selector clears the console's contents:
The rightmost button interrupts a long-running command. For example, running
Get-Package -ListAvailable -PageSize 500 lists the top 500 packages on the default source (such as nuget.org), which could take several minutes to run.
Installing a package in the console performs the same steps as described on What happens when a package is installed, with the following additions:
Universal gamepad driver for mac. See Uninstall-Package. Use Get-Package to see all packages currently installed in the default project if you need to find an identifier.
Uninstalling a package performs the following actions:
web.configwhen the package was installed.
See Get-Package and Update-Package
See Find-Package. In Visual Studio 2013 and earlier, use Get-Package instead.
Starting in Visual Studio 2017, NuGet and the NuGet Package Manager are automatically installed when you select any .NET-related workloads; you can also install it individually by checking the Individual components > Code tools > NuGet package manager option in the Visual Studio installer.
Also, if you're missing the NuGet Package Manager in Visual Studio 2015 and earlier, check Tools > Extensions and Updates.. and search for the NuGet Package Manager extension. If you're unable to use the extensions installer in Visual Studio, you can download the extension directly from https://dist.nuget.org/index.html.
The Package Manager Console is not presently available with Visual Studio for Mac. The equivalent commands, however, are available through the NuGet CLI. Visual Studio for Mac does have a UI for managing NuGet packages. See Including a NuGet package in your project.
The Package Manager Console is not included with Visual Studio Code.
Some packages install new commands for the console. For example,
MvcScaffolding creates commands like
Scaffold shown below, which generates ASP.NET MVC controllers and views:
A PowerShell profile lets you make commonly-used commands available wherever you use PowerShell. NuGet supports a NuGet-specific profile typically found at the following location:
To find the profile, type
$profile in the console:
For more details, refer to Windows PowerShell Profiles.
To make the
nuget.exe CLI available in the Package Manager Console, install the NuGet.CommandLine package from the console: