Merge pull request NuGet#651 from NuGet/master

Publish to live

Author: Kraig Brockschmidt

docs/API/package-publish-resource.md

@@ -146,5 +146,5 @@ X-NuGet-ApiKey | Header | string | yes      | For example, `X-NuGet-ApiKey: {USE
 
 Status Code | Meaning
 ----------- | -------
-204         | The package is now listed
+200         | The package is now listed
 404         | No package with the provided `ID` and `VERSION` exists

docs/Consume-Packages/Reinstalling-and-Updating-Packages.md

@@ -27,15 +27,16 @@ Updating and reinstalling packages is accomplished as follows:
 | 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**). |
 | 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. |
 
-In this topic:
+In this article:
+
 - [When to Reinstall a Package](#when-to-reinstall-a-package)
 - [Constraining upgrade versions](#constraining-upgrade-versions)
 
 ## When to Reinstall a Package
 
 1. **Broken references after package restore**: If you've opened a project and restored NuGet packages, but still see broken references, try reinstalling each of those packages.
 1. **Project is broken due to deleted files**: NuGet does not prevent you from removing items added from packages, so it's easy to inadvertently modify contents installed from a package and break your project. To restore the project, reinstall the affected packages.
-1. **Package update broke the project**: If an update to a package breaks a project, the failure is generally caused by a dependency package which may have also been. To restore the state of the dependency, reinstall that specific package.
+1. **Package update broke the project**: If an update to a package breaks a project, the failure is generally caused by a dependency package which may have also been updates. To restore the state of the dependency, reinstall that specific package.
 1. **Project retargeting or upgrade**: This can be useful when a project has been retargeted or upgraded and if the package requires reinstallation due to the change in target framework. NuGet 2.7 and later shows a build error in such cases immediately after project retargeting, and subsequent build warnings let you know that the package may need to be reinstalled. For project upgrade, NuGet shows an error in the Project Upgrade Log.
 1. **Reinstalling a package during its development**: Package authors often need to reinstall the same version of package they're developing to test the behavior. The `Install-Package` command does not provide an option to force a reinstall, so use `Update-Package -reinstall` instead.
 

docs/Quickstart/Create-and-Publish-a-Package.md

@@ -54,7 +54,7 @@ Every NuGet package needs a manifest—a `.nuspec` file—to describe it
     nuget spec
     ```
 
-1. Open the file in a text editor. The manifest looks something like the code below, where tokens in the form *$`<token>`$* are be replaced during the packaging process with values from the project's Properties/AssemblyInfo.cs file. For more details on tokens, see [Creating a .nuspec file](../create-packages/creating-a-package.md#creating-the-nuspec-file).
+1. Open the file in a text editor. The manifest looks something like the code below, where tokens in the form `<token>` (such as `$id$`) are be replaced during the packaging process with values from the project's Properties/AssemblyInfo.cs file. For more details on tokens, see [Creating a .nuspec file](../create-packages/creating-a-package.md#creating-the-nuspec-file).
 
     ```xml
     <?xml version="1.0"?>

docs/Quickstart/Use-a-Package.md

@@ -17,6 +17,8 @@ ms.reviewer:
 
 # Install and use a package
 
+NuGet packages are units of reusable code that other developers make available to you for use in your projects. See [What is NuGet?](../What-is-NuGet.md) for background.
+
 [!INCLUDE [install-methods](../includes/install-methods.md)]
 
 Once installed, refer to the package in code with `using <namespace>` where \<namespace\> is specific to the package you're using. Once the reference is made, you can call the package through its API.

docs/Schema/nuget-config-file.md

@@ -35,11 +35,11 @@ In this topic:
 - [packageRestore section](#packagerestore-section)
 - [solution section](#solution-section)
 - [Package source sections](#package-source-sections):
-    - [packageSources](#packagesources)
-    - [packageSourceCredentials](#packagesourcecredentials)
-    - [apikeys](#apikeys)
-    - [disabledPackageSources](#disabledpackagesources)
-    - [activePackageSource](#activepackagesource)
+  -[packageSources](#packagesources)
+  - [packageSourceCredentials](#packagesourcecredentials)
+  - [apikeys](#apikeys)
+  - [disabledPackageSources](#disabledpackagesources)
+  - [activePackageSource](#activepackagesource)
 - [Using environment variables](#using-environment-variables)
 - [Example config file](#example-config-file)
 
@@ -62,7 +62,6 @@ Note: `dependencyVersion` and `repositoryPath` apply only to projects using `pac
 | defaultPushSource | Identifies the URL or path of the package source that should be used as the default if no other package sources are found for an operation. |
 | http_proxy http_proxy.user http_proxy.password no_proxy | Proxy settings to use when connecting to package sources; `http_proxy` should be in the format `http://<username>:<password>@<domain>`. Passwords are encrypted and cannot be added manually. For `no_proxy`, the value is a comma-separated list of domains the bypass the proxy server. You can alternately use the http_proxy and no_proxy environment variables for those values. For additional details, see [NuGet proxy settings](http://skolima.blogspot.com/2012/07/nuget-proxy-settings.html) (skolima.blogspot.com). |
 
-
 **Example**:
 
 ```xml
@@ -74,7 +73,6 @@ Note: `dependencyVersion` and `repositoryPath` apply only to projects using `pac
 </config>
 ```
 
-
 ## bindingRedirects section
 
 Configures whether NuGet does automatic binding redirects when a package is installed.
@@ -119,7 +117,6 @@ Controls whether the `packages` folder of a solution is included in source contr
 | --- | --- |
 | disableSourceControlIntegration | A Boolean indicating whether to ignore the packages folder when working with source control. The default value is false. |
 
-
 **Example**:
 
 ```xml
@@ -128,13 +125,13 @@ Controls whether the `packages` folder of a solution is included in source contr
 </solution>
 ```
 
-
 ## Package source sections
 
 The `packageSources`, `packageSourceCredentials`, `apikeys`, `activePackageSource`, and `disabledPackageSources` all work together to configure how NuGet works with package repositories during install, restore, and update operations.
 
 The [`nuget sources` command](../tools/cli-ref-sources.md) is generally used to manage these settings, except for `apikeys` which is managed using the [`nuget setapikey` command](../tools/cli-ref-setapikey.md).
 
+Note that the source URL for nuget.org is `https://api.nuget.org/v3/index.json`.
 
 ### packageSources
 
@@ -154,7 +151,6 @@ Lists all known package sources.
 </packageSources>
 ```
 
-
 ### packageSourceCredentials
 
 Stores usernames and passwords for sources, typically specified with the `-username` and `-password` switches with `nuget sources`. Passwords are encrypted by default unless the `-storepasswordincleartext` option is also used.
@@ -193,7 +189,7 @@ When using unencrypted passwords:
     <Test_x0020_Source>
         <add key="Username" value="user" />
         <add key="ClearTextPassword" value="hal+9ooo_da!sY" />
-    </Test_x0020_Source>    
+    </Test_x0020_Source>
 </packageSourceCredentials>
 ```
 
@@ -213,7 +209,6 @@ Stores keys for sources that use API key authentication, as set with the [`nuget
 </apikeys>
 ```
 
-
 ### disabledPackageSources
 
 Identified currently disabled sources. May be empty.
@@ -222,8 +217,6 @@ Identified currently disabled sources. May be empty.
 | --- | --- |
 | (name of source) | A Boolean indicating whether the source is disabled. |
 
-
-
 **Example:**
 
 ```xml
@@ -267,7 +260,6 @@ Similarly, if `HOME` on Mac/Linux is set to `/home/myStuff`, then `$HOME/NuGetRe
 
 If an environment variable is not found, NuGet uses the literal value from the configuration file.
 
-
 ## Example config file
 
 Below is an example `NuGet.Config` file that illustrates a number of settings:

docs/Schema/nuspec.md

@@ -168,8 +168,8 @@ And you build an assembly whose `AssemblyName` is `LoggingLibrary` with the `Rel
 The `<dependencies>` element within `<metadata>` contains any number of `<dependency>` elements that identify other packages upon which the top-level package depends. The attributes for each `<dependency>` are as follows:
 
 | Attribute | Description |
-| --- | --- | 
-| `id` | (Required) The package ID of the dependency. |
+| --- | --- |
+| `id` | (Required) The package ID of the dependency, such as "EntityFramework" and "NUnit", which is the name of the package nuget.org shows on a package page. |
 | `version` | (Required) The range of versions acceptable as a dependency. See [Package versioning](../reference/package-versioning.md#version-ranges-and-wildcards) for exact syntax. |
 | include | A comma-delimited list of include/exclude tags (see below) indicating of the dependency to include in the final package. The default value is `none`. |
 | exclude | A comma-delimited list of include/exclude tags (see below) indicating of the dependency to exclude in the final package. The  default value is `all`. Tags specified with `exclude` take precedence over those specified with `include`. For example, `include="runtime, compile" exclude="compile"` is the same as `include="runtime"`. |

docs/Tools/Package-Manager-Console.md

@@ -10,6 +10,8 @@ ms.topic: article
 ms.prod: nuget
 ms.technology: null
 ms.assetid: 2b92b119-6861-406c-82af-9d739af230e4
+f1_keywords: 
+  - "vs.nuget.packagemanager.console"
 
 # optional metadata
 

docs/Tools/Package-Manager-UI.md

@@ -12,6 +12,7 @@ f1_keywords:
   - "vs.toolsoptionspages.nuget_package_manager"
   - "vs.toolsoptionspages.nuget_package_manager.general"
   - "vs.toolsoptionspages.nuget_package_manager.package_sources"
+  - "vs.nuget.packagemanager.ui"
 description: Instructions for using the NuGet Package Manager UI in Visual Studio for working with NuGet packages.
 keywords: NuGet UI, NuGet package manager UI, NuGet in Visual Studio, managing NuGet packages, NuGet user interface, package manager in Visual Studio
 ms.reviewer:

docs/Tools/cli-ref-config.md

@@ -30,6 +30,8 @@ nuget config -AsPath <name> [options]
 
 where `<name>` and `<value>` specify a key-value pair to be set in the configuration. You can specify as many pairs as desired. To remove a value, specify the name and the `=` sign but no value.
 
+For allowable key names, see the [NuGet config file reference](../Schema/nuget-config-file.md).
+
 In NuGet 3.4+, `<value>` can use [environment variables](cli-ref-environment-variables.md).
 
 ## Options

docs/Tools/cli-ref-sources.md

@@ -27,6 +27,8 @@ ms.reviewer:
 
 Manages the list of sources located in `%AppData%\NuGet\NuGet.Config` or the specified configuration file.
 
+Note that the source URL for nuget.org is `https://api.nuget.org/v3/index.json`.
+
 ## Usage
 
 ```
@@ -35,7 +37,6 @@ nuget sources <operation> -Name <name> -Source <source>
 
 where `<operation>` is one of *List, Add, Remove, Enable, Disable,* or *Update*, `<name>` is the name of the source, and `<source>` is the source's URL.
 
-
 ## Options
 
 | Option | Description |