Update --no-cache to --no-http-cache (#3163)

Author: Nigusu-Allehu

docs/concepts/package-installation-process.md

@@ -20,7 +20,7 @@ The general process is as follows:
 2. Acquire the package:
    - Check if the package (by exact identifer and version number) is already installed in the *global-packages* folder as described on [Managing the global packages and cache folders](../consume-packages/managing-the-global-packages-and-cache-folders.md).
 
-   - If the package is not in the *global-packages* folder, attempt to retrieve it from the sources listed in the [configuration files](../consume-packages/Configuring-NuGet-Behavior.md). [Package Source Mapping](../consume-packages/package-source-mapping.md) configurations are applied at this point. For online sources, attempt first to retrieve the package from the HTTP cache unless `-NoCache` is specified with `nuget.exe` commands or `--no-cache` is specified with `dotnet restore`. (Visual Studio and `dotnet add package` always use the cache.) If a package is used from the cache, "CACHE" appears in the output. The cache has an expiration time of 30 minutes.
+   - If the package is not in the *global-packages* folder, attempt to retrieve it from the sources listed in the [configuration files](../consume-packages/Configuring-NuGet-Behavior.md). [Package Source Mapping](../consume-packages/package-source-mapping.md) configurations are applied at this point. For online sources, attempt first to retrieve the package from the HTTP cache unless `-NoHttpCache` is specified with `nuget.exe` commands or `--no-http-cache` is specified with `dotnet restore`. (Visual Studio and `dotnet add package` always use the cache.) If a package is used from the cache, "CACHE" appears in the output. The cache has an expiration time of 30 minutes.
 
    - If the package has been specified using a [floating version](../consume-packages/Package-References-in-Project-Files.md#floating-versions), or without a minimum version, NuGet *will* contact all sources to figure out the best match.
    Example: `1.*`, `(, 2.0.0]`.

docs/consume-packages/Package-Restore.md

@@ -189,7 +189,7 @@ To avoid using packages in the HTTP cache:
 
 - Clear the cache by using `nuget locals http-cache -clear` or `dotnet nuget locals http-cache --clear`.
 - Temporarily set the **NUGET_HTTP_CACHE_PATH** environment variable to a different folder.
-- For `nuget restore`, use the `-NoCache` option, or for `dotnet restore`, use the `--no-cache` option. These options don't affect restore operations through the Visual Studio Package Manager or Console.
+- For `nuget restore`, use the `-NoHttpCache` option, or for `dotnet restore`, use the `--no-http-cache` option. These options don't affect restore operations through the Visual Studio Package Manager or Console.
 
 <a name="migrate-to-automatic-package-restore-visual-studio"></a>
 ## Migrate to automatic package restore

docs/consume-packages/managing-the-global-packages-and-cache-folders.md

@@ -23,7 +23,7 @@ Whenever you install, update, or restore a package, NuGet manages packages and p
 
 By using the cache and *global-packages* folders, NuGet generally avoids downloading packages that already exist on the computer, improving the performance of install, update, and restore operations. When using PackageReference, the *global-packages* folder also avoids keeping downloaded packages inside project folders, where they might be inadvertently added to source control, and reduces NuGet's overall impact on computer storage.
 
-When asked to retrieve a package, NuGet first looks in the *global-packages* folder. If the exact version of package is not there, then NuGet checks all non-HTTP package sources. If the package is still not found, NuGet looks for the package in the *http-cache* unless you specify `--no-cache` with `dotnet.exe` commands or `-NoCache` with `nuget.exe` commands. If the package is not in the cache, or the cache isn't used, NuGet then retrieves the package over HTTP .
+When asked to retrieve a package, NuGet first looks in the *global-packages* folder. If the exact version of package is not there, then NuGet checks all non-HTTP package sources. If the package is still not found, NuGet looks for the package in the *http-cache* unless you specify `--no-http-cache` with `dotnet.exe` commands or `-NoHttpCache` with `nuget.exe` commands. If the package is not in the cache, or the cache isn't used, NuGet then retrieves the package over HTTP .
 
 For more information, see [What happens when a package is installed?](../concepts/package-installation-process.md).
 

docs/reference/cli-reference/cli-ref-install.md

@@ -70,9 +70,9 @@ where `<packageID>` names the package to install (using the latest version), or
 
   Displays help information for the command.
 
-- **`-NoCache`**
+- **`-NoHttpCache`**
 
-  Prevents NuGet from using cached packages. See [Managing the global packages and cache folders](../../consume-packages/managing-the-global-packages-and-cache-folders.md).
+  Prevents NuGet from using http cached packages. See [Managing the global packages and cache folders](../../consume-packages/managing-the-global-packages-and-cache-folders.md).
 
 - **`-NonInteractive`**
 

docs/reference/cli-reference/cli-ref-mirror.md

@@ -38,9 +38,9 @@ If your target repository is on `https://machine/repo` that's running [NuGet.Ser
 
   Displays help information for the command.
 
-- **`-NoCache`**
+- **`-NoHttpCache`**
 
-  Prevents NuGet from using cached packages. See [Managing the global packages and cache folders](../../consume-packages/managing-the-global-packages-and-cache-folders.md).
+  Prevents NuGet from using http cached packages. See [Managing the global packages and cache folders](../../consume-packages/managing-the-global-packages-and-cache-folders.md).
 
 - **`-Noop`**
 
@@ -67,7 +67,7 @@ Also see [Environment variables](cli-ref-environment-variables.md)
 ## Examples
 
 ```cli
-nuget mirror packages.config  https://MyRepo/nuget https://MyRepo/api/v2/package -source https://nuget.org/api/v2 -apikey myApiKey -nocache
+nuget mirror packages.config  https://MyRepo/nuget https://MyRepo/api/v2/package -source https://nuget.org/api/v2 -apikey myApiKey -nohttpcache
 
 nuget mirror Microsoft.AspNet.Mvc https://MyRepo/nuget https://MyRepo/api/v2/package -version 4.0.20505.0
 

docs/reference/cli-reference/cli-ref-restore.md

@@ -73,9 +73,9 @@ where `<projectPath>` specifies the location of a solution or a `packages.config
 
   *(3.2+)* Specifies the version of MSBuild to be used with this command. Supported values are 4, 12, 14, 15.1, 15.3, 15.4, 15.5, 15.6, 15.7, 15.8, 15.9. By default the MSBuild in your path is picked, otherwise it defaults to the highest installed version of MSBuild.
 
-- **`-NoCache`**
+- **`-NoHttpCache`**
 
-  Prevents NuGet from using cached packages. See [Managing the global packages and cache folders](../../consume-packages/managing-the-global-packages-and-cache-folders.md).
+  Prevents NuGet from using http cached packages. See [Managing the global packages and cache folders](../../consume-packages/managing-the-global-packages-and-cache-folders.md).
 
 - **`-NonInteractive`**
 

docs/reference/msbuild-targets.md

@@ -426,7 +426,7 @@ Additional restore settings may come from MSBuild properties in the project file
 | `RestorePackagesPath` | User packages folder path. |
 | `RestoreDisableParallel` | Limit downloads to one at a time. |
 | `RestoreConfigFile` | Path to a `Nuget.Config` file to apply. |
-| `RestoreNoCache` | If true, avoids using cached packages. See [Managing the global packages and cache folders](../consume-packages/managing-the-global-packages-and-cache-folders.md). |
+| `RestoreNoHttpCache` | If true, avoids using http cached packages. See [Managing the global packages and cache folders](../consume-packages/managing-the-global-packages-and-cache-folders.md). |
 | `RestoreIgnoreFailedSources` | If true, ignores failing or missing package sources. |
 | `RestoreFallbackFolders` | Fallback folders, used in the same way the user packages folder is used. |
 | `RestoreAdditionalProjectSources` | Additional sources to use during restore. |