If you're unable to use the extensions installer in Visual Studio, you can download the extension directly from. and search for the NuGet Package Manager extension.
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.Īlso, if you're missing the NuGet Package Manager in Visual Studio 2015 and earlier, check Tools > Extensions and Updates. Starting in Visual Studio 2017, NuGet and the NuGet Package Manager are automatically installed when you select any. In Visual Studio 2013 and earlier, use Get-Package instead. # Find packages containing keywords Find-Package elmah Find-Package logging # List packages whose ID begins with Elmah Find-Package Elmah -StartWith # By default, Get-Package returns a list of 20 packages use -First to show more Find-Package logging -First 100 # List all versions of the package with the ID of "jquery" Find-Package jquery -AllVersions -ExactMatch For example, running Get-Package -ListAvailable -PageSize 500 lists the top 500 packages on the default source (such as ), which could take several minutes to run. The rightmost button interrupts a long-running command. Also, the control to the right of the project selector clears the console's contents: This is a shortcut to the Tools > Options > NuGet Package Manager > Package Sources dialog box as described on the Package Manager UI page. To manage package sources, select the gear icon. To overrride these settings without changing the defaults, most commands support -Source and -ProjectName options. Selecting a different package source and/or project changes those defaults for subsequent commands. The console is a Visual Studio window that can be arranged and positioned however you like (see Customize window layouts in Visual Studio).īy default, console commands operate against a specific package source and project as set in the control at the top of the window: Open the console in Visual Studio using the Tools > NuGet Package Manager > Package Manager Console command. Saving an unsaved solution, or creating and saving a solution if you don't have one open, should correct the error. Please ensure you have an open and saved solution." This indicates that the console cannot determine the solution folder. If you have an unsaved solution, or no solution, you can see the error, "Solution is not opened or not saved. Many console operations depend on having a solution opened in Visual Studio with a known path name. For this reason, developers working in Visual Studio typically prefer using the console to the CLI. For example, installing a package through the console adds a reference to the project whereas the CLI command does not. However, console commands operate within the context of Visual Studio and a saved project/solution and often accomplish more than their equivalent CLI commands. Install-Package Elmah -ProjectName MyProjectĪll operations that are available in the console can also be done with the NuGet CLI. # Install the Elmah package to the project named MyProject.
If you already know this, skip to step 3. Open the project/solution in Visual Studio, and open the console using the Tools > NuGet Package Manager > Package Manager Console command.įind the package you want to install. Find and install a packageįor example, finding and installing a package is done with three easy steps: When using the Package Management Console in Visual Studio, the commands and arguments documented in this present topic apply. Specifically, each environment has commands that are not available in the other, and commands with the same name may also differ in their specific arguments. The commands listed here are specific to the Package Manager Console in Visual Studio, and differ from the Package Management module commands that are available in a general PowerShell environment.
It is not included with Visual Studio for Mac or Visual Studio Code. The console is built into Visual Studio on Windows.
To use nuget.exe CLI commands in the console, see Using the nuget.exe CLI in the console. Using the console is necessary in cases where the Package Manager UI does not provide a way to perform an operation.
The NuGet Package Manager Console lets you use NuGet PowerShell commands to find, install, uninstall, and update NuGet packages. Install and manage packages with the Package Manager Console in Visual Studio (PowerShell)