master to live (NuGet#881)

* Update rate limits for package push & unlist APIs

Docs change for NuGet/NuGetGallery#5821.
DO NOT MERGE YET! To be merged when change is live.

* fix package description msbuild property

* Update cli-ref-install.md

* Address #871

* Address #868

* Address #873

* Small edit to address #870

* fixed exclude files copy/paste error

Source Files in the Exclude example were a pattern, not a discreet set of files. If I've misunderstood, let me know!

* 4.7 relnotes (NuGet#876)

* Create NuGet-4.7-RTM.md

* Update NuGet-4.7-RTM.md

* Update NuGet-4.7-RTM.md

* Updates

* updates

* 4.7 rtm

* 4.7rtm

* Update NuGet-4.7-RTM.md

* Added more concrete file names

Hopefully this is more clear.

* init commit

* Update NuGet-4.7-RTM.md (NuGet#879)

Author: karann-msft

docs/api/rate-limits.md

@@ -42,5 +42,5 @@ The following tables list the rate limits for the NuGet.org API.
 
 | API | Limit Type | Limit Value | API usecase | 
 |:---|:---|:---|:--- |
-**PUT** `/api/v2/package` | API Key | 100 / minute | Upload a new NuGet package (version) via v2 push endpoint 
-**DELETE** `/api/v2/package/{id}/{version}` | API Key | 100 / minute | Unlist a NuGet package (version) via v2 endpoint 
+**PUT** `/api/v2/package` | API Key | 250 / hour | Upload a new NuGet package (version) via v2 push endpoint 
+**DELETE** `/api/v2/package/{id}/{version}` | API Key | 250 / hour | Unlist a NuGet package (version) via v2 endpoint 

docs/reference/nuspec.md

@@ -384,9 +384,10 @@ Each `<file>` element specifies the following attributes:
 **Excluding files**
 
     Source files:
-        \tools\*.bak
-        \tools\*.log
-        \tools\build\*.log
+        \tools\fileA.bak
+        \tools\fileB.bak
+        \tools\fileA.log
+        \tools\build\fileB.log
 
     .nuspec entries:
         <file src="tools\*.*" target="tools" exclude="tools\*.bak" />

docs/release-notes/NuGet-4.7-RTM.md

@@ -20,6 +20,22 @@ ms.topic: conceptual
 
 ## Known issues
 
+### The `Migrate packages.config to PackageReference...` option is not available in the right-click context menu
+
+#### Issue
+
+When a project is first opened, NuGet may not have initialized until a NuGet operation is performed. This causes the migration option to not show up in the right-click context menu on `packages.config` or `References`.
+
+#### Workaround
+
+Peform any one of the following NuGet actions:
+* Open the Package Manager UI - Right-click on `References` and select `Manage NuGet Packages...`
+* Open the Package Manager Console - From `Tools > NuGet Package Manager`, select `Package Manager Console`
+* Run NuGet restore - Right-click on the solution node in the Solution Explorer and select `Restore NuGet Packages`
+* Build the project which also triggers NuGet restore
+
+You should now be able to see the migration option. Note that this option is not supported and will not show up for ASP.NET and C++ project types.
+
 ### Issues with .NET Standard 2.0 with .NET Framework & NuGet
 
 .NET Standard & its tooling was designed such that projects targeting .NET Framework 4.6.1 can consume NuGet packages & projects targeting .NET Standard 2.0 or earlier. [This document](https://github.com/dotnet/standard/issues/481) summarizes the issues around that scenario, the plan for addressing them, and workarounds you can deploy with today's state of the tooling.