You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/consume-packages/Reinstalling-and-Updating-Packages.md
+3Lines changed: 3 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -19,6 +19,9 @@ Updating and reinstalling packages is accomplished as follows:
19
19
| Package Manager UI | On the **Updates** tab, select one or more packages and select **Update**| On the **Installed** tab, select a package, record its name, then select **Uninstall**. Switch to the **Browse** tab, search for the package name, select it, then select **Install**). |
20
20
| nuget.exe CLI |`nuget update` command | For all packages, delete the package folder, then run `nuget install`. For a single package, delete the package folder and use `nuget install <id>` to reinstall the same one. |
21
21
22
+
> [!NOTE]
23
+
> For the dotnet CLI, the equivalent procedure is not required. In a similar scenario, you can [restore packages with the dotnet CLI](../consume-packages/install-use-packages-dotnet-cli.md#restore-packages).
24
+
22
25
In this article:
23
26
24
27
-[When to Reinstall a Package](#when-to-reinstall-a-package)
Copy file name to clipboardExpand all lines: docs/install-nuget-client-tools.md
+3-3Lines changed: 3 additions & 3 deletions
Original file line number
Diff line number
Diff line change
@@ -62,7 +62,7 @@ To learn how to use basic commands with the `nuget.exe` CLI, see [Install and us
62
62
- Visual Studio for Mac: certain NuGet capabilities are built in directly. See [Including a NuGet package in your project](/visualstudio/mac/nuget-walkthrough) for a walkthrough. For other capabilities, use the `dotnet.exe` or `nuget.exe` CLI tools.
63
63
64
64
- Visual Studio on Windows: The **NuGet Package Manager** is included with Visual Studio 2012 and later. Visual Studio provides the [Package Manager UI](tools/package-manager-ui.md) and the [Package Manager Console](tools/package-manager-console.md), through which you can run most NuGet operations.
65
-
-The Visual Studio 2017installer includes the NuGet Package Manager with any workload that employs .NET. To install separately, or to verify that the Package Manager is installed, run the Visual Studio 2017 installer and check the option under **Individual Components > Code tools > NuGet package manager**.
65
+
-Starting in Visual Studio 2017, the installer includes the NuGet Package Manager with any workload that employs .NET. To install separately, or to verify that the Package Manager is installed, run the Visual Studio installer and check the option under **Individual Components > Code tools > NuGet package manager**.
66
66
- The Package Manager UI and Console are unique to Visual Studio on Windows. They are not presently available on Visual Studio for Mac.
67
67
- A CLI tool is required to support NuGet features in the IDE. You can use either the `dotnet` CLI or the the `nuget.exe` CLI. The `dotnet` CLI is installed with some Visual Studio workloads, such as .NET Core. The `nuget.exe` CLI must be installed separately as described earlier.
68
68
- Package Manager Console commands work only within Visual Studio on Windows and do not work within other PowerShell environments.
@@ -97,10 +97,10 @@ To learn how to use basic commands with the `nuget.exe` CLI, see [Install and us
Copy file name to clipboardExpand all lines: docs/tools/Package-Manager-Console.md
+5-3Lines changed: 5 additions & 3 deletions
Original file line number
Diff line number
Diff line change
@@ -3,17 +3,19 @@ title: Install and manage NuGet packages using PowerShell in Visual Studio
3
3
description: Instructions for using the NuGet Package Manager Console in Visual Studio for working with packages.
4
4
author: karann-msft
5
5
ms.author: karann
6
-
ms.date: 01/23/2018
6
+
ms.date: 06/24/2019
7
7
ms.topic: conceptual
8
8
f1_keywords:
9
9
- "vs.nuget.packagemanager.console"
10
10
---
11
11
12
12
# Install and manage packages using PowerShell in Visual Studio
13
13
14
-
The NuGet Package Manager Console is built into Visual Studio on Windows version 2012 and later. (It is not included with Visual Studio for Mac or Visual Studio Code.)
14
+
The NuGet Package Manager Console lets you use [NuGet PowerShell commands](../tools/powershell-reference.md) 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](#using-the-nugetexe-cli-in-the-console).
15
15
16
-
The console lets you use [NuGet PowerShell commands](../tools/powershell-reference.md) 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` commands in the console, see [Using the nuget.exe CLI in the console](#using-the-nugetexe-cli-in-the-console).
16
+
The console is built into Visual Studio on Windows. It is not included with Visual Studio for Mac or Visual Studio Code.
17
+
18
+
## Find and install a package
17
19
18
20
For example, finding and installing a package is done with three easy steps:
Copy file name to clipboardExpand all lines: docs/tools/dotnet-Commands.md
+7-5Lines changed: 7 additions & 5 deletions
Original file line number
Diff line number
Diff line change
@@ -1,17 +1,19 @@
1
1
---
2
-
title: dotnet NuGet commands
2
+
title: dotnet CLI NuGet commands
3
3
description: A short reference for NuGet-related commands using the dotnet command-line interface.
4
4
author: karann-msft
5
5
ms.author: karann
6
-
ms.date: 01/23/2018
6
+
ms.date: 06/24/2019
7
7
ms.topic: conceptual
8
8
---
9
9
10
-
# dotnet commands
10
+
# dotnet CLI commands
11
11
12
-
The `dotnet` command-line interface, which runs on Windows, Mac OS X, and Linux, provides a number of essential nuget.exe commands as listed below. If dotnet satisfies your needs, it's not necessary to use `nuget.exe`.
12
+
The `dotnet` command-line interface (CLI), which runs on Windows, Mac OS X, and Linux, provides a number of essential commands such as installing, restoring, and publishing packages. If dotnet satisfies your needs, it's not necessary to use `nuget.exe`.
13
13
14
-
For complete information on `dotnet`, see [.NET Core command-line interface (CLI) tools](/dotnet/core/tools/?tabs=netcore2x).
14
+
For examples of using these commands to consume packages, see [Install and manage packages using the dotnet CLI](../consume-packages/install-use-packages-dotnet-cli.md). For examples of using these commands to create packages, see [Create and publish a package using the dotnet CLI]../quickstart/create-and-publish-a-package-using-the-dotnet-cli.md).
15
+
16
+
For the complete command reference on `dotnet` CLI, see [.NET Core command-line interface (CLI) tools](/dotnet/core/tools/?tabs=netcore2x).
Copy file name to clipboardExpand all lines: docs/tools/nuget-exe-CLI-Reference.md
+2Lines changed: 2 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -15,6 +15,8 @@ To use any command, open a command window or bash shell, then run `nuget` follow
15
15
16
16
This documentation reflects the latest version of the NuGet CLI. For exact details for any given version that you're using, run `nuget help` for the desired command.
17
17
18
+
To learn how to use basic commands with the `nuget.exe` CLI, see [Install and use packages using the nuget.exe CLI](../consume-packages/install-use-packages-nuget-cli.md).
0 commit comments