Fix build validation issues (#3179)

Mikejo5000 · zivkan · web-flow · commit a61f28f8bcae · 2023-11-14T08:42:28.000-08:00
* metadata update

* Fix build validation errors

* build validation fixes

* link fix

* link fix

* Update docs/nuget-org/Publish-a-package.md

Co-authored-by: Andy Zivkovic &lt;zivkan@users.noreply.github.com&gt;

---------

Co-authored-by: Andy Zivkovic &lt;zivkan@users.noreply.github.com&gt;
diff --git a/docs/consume-packages/Team-Foundation-Build.md b/docs/consume-packages/Team-Foundation-Build.md
@@ -81,7 +81,7 @@ The source code is under the `src` folder. Although our demo only uses a single
 ### Ignore files
 
 > [!Note]
-> There is currently a [known bug in the NuGet client](https://nuget.codeplex.com/workitem/4072) that causes the client to still add the `packages` folder to version control. A workaround is to disable the source control integration. In order to do that, you need a `Nuget.Config ` file in the  `.nuget` folder that is parallel to your solution. If this folder doesn't exist yet, you need to create it. In [`Nuget.Config`](../consume-packages/configuring-nuget-behavior.md), add the following content:
+> There is currently a `[known bug in the NuGet client](https://nuget.codeplex.com/workitem/4072)` that causes the client to still add the `packages` folder to version control. A workaround is to disable the source control integration. In order to do that, you need a `Nuget.Config ` file in the  `.nuget` folder that is parallel to your solution. If this folder doesn't exist yet, you need to create it. In [`Nuget.Config`](../consume-packages/configuring-nuget-behavior.md), add the following content:
 
 ```xml
 <configuration>
diff --git a/docs/guides/Create-UWP-Packages-CS.md b/docs/guides/Create-UWP-Packages-CS.md
@@ -1,8 +1,8 @@
 ---
 title: Create NuGet Packages for the UWP Platform (C#)
 description: An end-to-end walkthrough of creating NuGet packages using a Windows Runtime Component for the Universal Windows Platform in C#.
-author: rrelyea
-ms.author: rrelyea
+author: JonDouglas
+ms.author: jodou
 ms.date: 11/01/2023
 ms.topic: tutorial
 ---
diff --git a/docs/nuget-org/Publish-a-package.md b/docs/nuget-org/Publish-a-package.md
@@ -87,8 +87,10 @@ Nuget.org has a package size limit of about 250 MB. When a package exceeding tha
 
 If such package is pushed from the command line, the following output is produced:
 
->   RequestEntityTooLarge https://www.nuget.org/api/v2/package/ 13903ms
-> error: Response status code does not indicate success: 413 (The package file exceeds the size limit. Please try again.).
+```text
+  RequestEntityTooLarge https://www.nuget.org/api/v2/package/ 13903ms
+error: Response status code does not indicate success: 413 (The package file exceeds the size limit. Please try again.).
+```
 
 If you are getting this errors consider revising the package content to reduce its size. If you are packing debug symbols into your package consider publishing them [separately](../create-packages/Symbol-Packages-snupkg.md). Other assets can be published separately as one or more dependency packages to spread them into smaller chunks.
 
diff --git a/docs/policies/Ecosystem.md b/docs/policies/Ecosystem.md
@@ -70,10 +70,10 @@ Using a new tool or technology usually comes with a learning curve. Luckily for
 That said, authoring packages–and especially good packages–along with  embracing NuGet in automated build and deployment processes, requires spending a little more time with the following resources:
 
 - [NuGet Blog](https://devblogs.microsoft.com/nuget/)
-- [NuGet team on Twitter, @nuget](http://twitter.com/nuget)
+- [NuGet team on Twitter, @nuget](https://twitter.com/nuget)
 - Books:
   - [Apress Pro NuGet](http://bit.ly/ProNuGet)
-  - [NuGet 2 Essentials](http://www.amazon.com/NuGet-2-Essentials-Damir-Arh-ebook/dp/B00GTQD5M4)
+  - [NuGet 2 Essentials](https://www.amazon.com/NuGet-2-Essentials-Damir-Arh/dp/178216586X)
 
 ## Documentation for individual packages
 
diff --git a/docs/reference/cli-reference/cli-ref-trusted-signers.md b/docs/reference/cli-reference/cli-ref-trusted-signers.md
@@ -1,8 +1,8 @@
 ---
 title: NuGet CLI trusted-signers command
 description: Reference for the nuget.exe trusted-signers command
-author: patbel
-ms.author: patbel
+author: JonDouglas
+ms.author: jodou
 ms.date: 11/12/2018
 ms.topic: reference
 ms.reviewer: rmpablos
diff --git a/docs/reference/errors-and-warnings/NU3040.md b/docs/reference/errors-and-warnings/NU3040.md
@@ -1,8 +1,8 @@
 ---
 title: NuGet Warning NU3040
 description: NU3040 Warning code
-author: patbel
-ms.author: patbel
+author: JonDouglas
+ms.author: jodou
 ms.date: 11/12/2018
 ms.topic: reference
 ms.reviewer: rmpablos
diff --git a/docs/reference/errors-and-warnings/NU5046.md b/docs/reference/errors-and-warnings/NU5046.md
@@ -1,8 +1,8 @@
 ---
 title: NuGet Error NU5046
 description: NU5046 Error code
-author: dominoFire
-ms.author: feaguila
+author: JonDouglas
+ms.author: jodou
 ms.date: 9/4/2019
 ms.topic: reference
 ms.reviewer: karann
diff --git a/docs/reference/errors-and-warnings/NU5047.md b/docs/reference/errors-and-warnings/NU5047.md
@@ -1,8 +1,8 @@
 ---
 title: NuGet Error NU5047
 description: NU5047 Error code
-author: dominoFire
-ms.author: feaguila
+author: JonDouglas
+ms.author: jodou
 ms.date: 9/4/2019
 ms.topic: reference
 ms.reviewer: karann
diff --git a/docs/reference/nuspec.md b/docs/reference/nuspec.md
@@ -123,7 +123,7 @@ If you're licensing the package under a common license, like MIT or BSD-2-Clause
 > [!Note]
 > NuGet.org only accepts license expressions that are approved by the Open Source Initiative or the Free Software Foundation.
 
-If your package is licensed under multiple common licenses, you can specify a composite license using the [SPDX expression syntax version 2.0](https://spdx.org/spdx-specification-21-web-version#h.jxpfx0ykyb60). For example:
+If your package is licensed under multiple common licenses, you can specify a composite license using the [SPDX expression syntax version 2.0](https://spdx.github.io/spdx-spec/v2-draft/SPDX-license-expressions/#d4-composite-license-expressions). For example:
 
 `<license type="expression">BSD-2-Clause OR MIT</license>`
 
diff --git a/docs/release-notes/NuGet-2.5.md b/docs/release-notes/NuGet-2.5.md
@@ -186,6 +186,6 @@ nuget sources add -name test -source http://test -ConfigFile C:\test\.nuget\Nuge
 
 ### Support for Native projects
 
-With NuGet 2.5, the NuGet tooling is now available for Native projects in Visual Studio. We expect most native packages will utilize the MSBuild imports feature above, using a tool created by the [CoApp project](https://coapp.org). For more information, read [the details about the tool](https://coapp.org/news/2013-03-27-The-Long-Awaited-post.html) on the coapp.org website.
+With NuGet 2.5, the NuGet tooling is now available for Native projects in Visual Studio. We expect most native packages will utilize the MSBuild imports feature above, using a tool created by the [CoApp project](https://github.com/coapp). For more information, read [the details about the tool](https://github.com/coapp/coapp.org/blob/master/src/dynamic/news/2013-03-27-The-Long-Awaited-post.html.md) on the coapp.org website.
 
 The target framework name of "native" is introduced for packages to include files in \build, \content, and \tools when the package is installed into a native project.  The \`lib` folder is not used for native projects.
diff --git a/docs/release-notes/NuGet-2.8.3.md b/docs/release-notes/NuGet-2.8.3.md
@@ -13,4 +13,4 @@ ms.topic: conceptual
 
 NuGet 2.8.3 was released October 17, 2014. It is a minor update to our 2.8.1 VSIX with some targeted fixes.
 
-In this release, the support for NuGet Package Manager dialog was added for [ASP.NET vNext](http://www.asp.net/vnext), [DevExtreme](http://js.devexpress.com/) and [BizTalk (.btproj)](/biztalk/core/developing-biztalk-server-applications) project types. It also includes reliability bug fixes related to the scenarios of enabling package restore and saving package manager options.
+In this release, the support for NuGet Package Manager dialog was added for [ASP.NET vNext](https://www.asp.net/vnext), [DevExtreme](https://js.devexpress.com/) and [BizTalk (.btproj)](/biztalk/core/developing-biztalk-server-applications) project types. It also includes reliability bug fixes related to the scenarios of enabling package restore and saving package manager options.
diff --git a/docs/release-notes/NuGet-3.0-Preview.md b/docs/release-notes/NuGet-3.0-Preview.md
@@ -15,7 +15,7 @@ NuGet 3.0 Preview was released on November 12, 2014 as part of the Visual Studio
 
 ## Visual Studio 2012+
 
-This NuGet 3.0 Preview is included in Visual Studio 2015 Preview. We are working to get preview drops out for Visual Studio 2012 and Visual Studio 2013 very soon. We previously shared our intent to [discontinue updates for Visual Studio 2010](http://blog.nuget.org/20141002/visual-studio-2010.html), and we did make that difficult decision.
+This NuGet 3.0 Preview is included in Visual Studio 2015 Preview. We are working to get preview drops out for Visual Studio 2012 and Visual Studio 2013 very soon. We previously shared our intent to [discontinue updates for Visual Studio 2010](https://blog.nuget.org/20141002/visual-studio-2010.html), and we did make that difficult decision.
 
 ## Brand New UI
 
@@ -113,11 +113,11 @@ Despite the investment we're putting into API v3, we've made all of these new fe
 
 Between now and 3.0 RTM, we are also working on some fundamental new NuGet features, beyond what you see in the UI. Here's a short list of salient investment areas:
 
-1. We're partnering with the Visual Studio and MSBuild teams to get [NuGet deeper into the platform](http://blog.nuget.org/20141014/in-the-platform.html).
-1. We're working to abandon installation-time package conventions and instead apply those conventions at packaging time by introducing a new "authoritative" [package manifest](http://blog.nuget.org/20141023/package-manifests.html).
+1. We're partnering with the Visual Studio and MSBuild teams to get [NuGet deeper into the platform](https://blog.nuget.org/20141014/in-the-platform.html).
+1. We're working to abandon installation-time package conventions and instead apply those conventions at packaging time by introducing a new "authoritative" [package manifest](https://blog.nuget.org/20141023/package-manifests.html).
 1. We're working to refactor the NuGet codebase to make the client and server components reusable in different domains beyond package management in Visual Studio.
 1. We're investigating the notion of "private dependencies" where a package can indicate that it has dependencies on other packages for implementation details only, and those dependencies shouldn't be surfaced as top-level dependencies.
 
 ## Stay Tuned
 
-Please keep an eye on [our blog](http://blog.nuget.org) for more progress and announcements for NuGet 3.0!
+Please keep an eye on [our blog](https://blog.nuget.org) for more progress and announcements for NuGet 3.0!
diff --git a/docs/release-notes/NuGet-3.0-RC.md b/docs/release-notes/NuGet-3.0-RC.md
@@ -32,9 +32,9 @@ In order to stabilize the NuGet clients, we resolved many issues as part of this
 
 ## GitHub presence overhaul
 
-We've made some changes to our [source code repositories on GitHub](http://github.com/nuget/home).  If you have any issues with the NuGet Visual Studio client, the Powershell commands, or the command-line executable you can log those issues and monitor their progress on our [GitHub Home repository issues list](http://github.com/nuget/home/issues).  We are tracking issues for the gallery in our [GitHub NuGetGallery repository](http://github.com/nuget/NuGetGallery/issues).
+We've made some changes to our [source code repositories on GitHub](https://github.com/nuget/home).  If you have any issues with the NuGet Visual Studio client, the Powershell commands, or the command-line executable you can log those issues and monitor their progress on our [GitHub Home repository issues list](https://github.com/nuget/home/issues).  We are tracking issues for the gallery in our [GitHub NuGetGallery repository](https://github.com/nuget/NuGetGallery/issues).
 
 
 ## Stay Tuned
 
-Please keep an eye on [our blog](http://blog.nuget.org) for more progress and announcements for NuGet 3.0!
+Please keep an eye on [our blog](https://blog.nuget.org) for more progress and announcements for NuGet 3.0!
diff --git a/docs/release-notes/NuGet-3.0.0.md b/docs/release-notes/NuGet-3.0.0.md
@@ -49,4 +49,4 @@ There were a number of known issues delivered with this release, and all of thes
 * [Multiple Packages can be gathered in parallel](https://github.com/NuGet/Home/issues/713)
 * [Removed install-package -force command](https://github.com/NuGet/Home/issues/697)
 
-Please keep an eye on [our blog](http://blog.nuget.org) for more progress and announcements as we get ready to deliver support for Windows 10 development.
+Please keep an eye on [our blog](https://blog.nuget.org) for more progress and announcements as we get ready to deliver support for Windows 10 development.
diff --git a/docs/release-notes/NuGet-3.1.md b/docs/release-notes/NuGet-3.1.md
@@ -48,7 +48,7 @@ There were a number of known issues delivered with this release.
 
 ## NuGet Command-line
 
-The NuGet command-line executable was updated and moved to a new distributable location so that historical versions of nuget.exe can continue to be made available.  You can download the 3.1 beta version of nuget.exe for Windows at: [http://dist.nuget.org/win-x86-commandline/v3.1.0-beta/nuget.exe](http://dist.nuget.org/win-x86-commandline/v3.1.0-beta/nuget.exe)
+The NuGet command-line executable was updated and moved to a new distributable location so that historical versions of nuget.exe can continue to be made available.  You can download the 3.1 beta version of nuget.exe for Windows at: [https://dist.nuget.org/win-x86-commandline/v3.1.0-beta/nuget.exe](https://dist.nuget.org/win-x86-commandline/v3.1.0-beta/nuget.exe)
 
 The new distributable location resides on the dist.nuget.org host, with a folder structure that follows this template:
 
@@ -66,4 +66,4 @@ The new distributable location resides on the dist.nuget.org host, with a folder
 1.    Cannot execute pack against a `project.json` file - [928](https://github.com/NuGet/Home/issues/928)
 2.    Is not supported on Mono - [1059](https://github.com/NuGet/Home/issues/1059)
 3.    Is not localized - [1058](https://github.com/NuGet/Home/issues/1058),   [1057](https://github.com/NuGet/Home/issues/1057)
-4.    Is not signed, just like the existing http://nuget.org/nuget.exe - [1073](https://github.com/NuGet/Home/issues/1073)
+4.    Is not signed, just like the existing https://nuget.org/nuget.exe - [1073](https://github.com/NuGet/Home/issues/1073)
diff --git a/docs/release-notes/NuGet-3.2-RC.md b/docs/release-notes/NuGet-3.2-RC.md
@@ -111,4 +111,4 @@ A complete list of issues addressed for the Visual Studio extension can be found
 
 ## Known Issues
 
-We continue to track issues on our GitHub issues list which can be found at: [http://github.com/nuget/home/issues](http://github.com/nuget/home/issues)
+We continue to track issues on our GitHub issues list which can be found at: [https://github.com/nuget/home/issues](https://github.com/nuget/home/issues)
diff --git a/docs/release-notes/NuGet-3.2.1.md b/docs/release-notes/NuGet-3.2.1.md
@@ -11,7 +11,7 @@ ms.topic: conceptual
 
 [NuGet 3.2 Release Notes](../release-notes/nuget-3.2.md) | [NuGet 3.3 Release Notes](../release-notes/nuget-3.3.md)
 
-NuGet 3.2.1 for the command-line was released October 12, 2015 with a handful of optimizations and fixes for the 3.2 release and is available from [dist.nuget.org](http://dist.nuget.org/index.html).
+NuGet 3.2.1 for the command-line was released October 12, 2015 with a handful of optimizations and fixes for the 3.2 release and is available from [dist.nuget.org](https://dist.nuget.org/index.html).
 
 ## Improvements
 
@@ -30,4 +30,4 @@ A complete list of issues addressed for the command-line and Visual Studio exten
 
 ## Known Issues
 
-We continue to track issues on our GitHub issues list which can be found at: [http://github.com/nuget/home/issues](http://github.com/nuget/home/issues)
+We continue to track issues on our GitHub issues list which can be found at: [https://github.com/nuget/home/issues](https://github.com/nuget/home/issues)
diff --git a/docs/release-notes/NuGet-3.2.md b/docs/release-notes/NuGet-3.2.md
@@ -11,7 +11,7 @@ ms.topic: conceptual
 
 [NuGet 3.2-RC Release Notes](../release-notes/nuget-3.2-RC.md) | [NuGet 3.2.1 Release Notes](../release-notes/nuget-3.2.1.md)
 
-NuGet 3.2 was released September 16, 2015 as a collection of improvements and fixes for the 3.1.1 release and is available from both [dist.nuget.org](http://dist.nuget.org/index.html) and the [Visual Studio Gallery](https://marketplace.visualstudio.com/items?itemName=NuGetTeam.NuGetPackageManagerforVisualStudio2015).
+NuGet 3.2 was released September 16, 2015 as a collection of improvements and fixes for the 3.1.1 release and is available from both [dist.nuget.org](https://dist.nuget.org/index.html) and the [Visual Studio Gallery](https://marketplace.visualstudio.com/items?itemName=NuGetTeam.NuGetPackageManagerforVisualStudio2015).
 
 ## New Features
 
@@ -109,4 +109,4 @@ A complete list of issues addressed for the Visual Studio extension can be found
 
 ## Known Issues
 
-We continue to track issues on our GitHub issues list which can be found at: [http://github.com/nuget/home/issues](http://github.com/nuget/home/issues)
+We continue to track issues on our GitHub issues list which can be found at: [https://github.com/nuget/home/issues](https://github.com/nuget/home/issues)
diff --git a/docs/release-notes/NuGet-3.3.md b/docs/release-notes/NuGet-3.3.md
@@ -32,7 +32,7 @@ NuGet 3.3 was released November 30, 2015 with a significant number of user inter
 
 ## New Command-line Features
 
-In this version we introduced the `add` and `init` commands to initialize folder-based repositories as described in the [nuget.exe reference](../reference/nuget-exe-cli-reference.md). Repositories that are constructed and maintained with this folder structure will [deliver significant performance benefits](http://blog.nuget.org/20150922/Accelerate-Package-Source.html) as outlined on our blog.
+In this version we introduced the `add` and `init` commands to initialize folder-based repositories as described in the [nuget.exe reference](../reference/nuget-exe-cli-reference.md). Repositories that are constructed and maintained with this folder structure will [deliver significant performance benefits](https://blog.nuget.org/20150922/Accelerate-Package-Source.html) as outlined on our blog.
 
 ## ContentFiles
 
@@ -54,4 +54,4 @@ The list of issues fixed in the 3.3 command-line release are recorded in the [3.
 
 ## Known Issues
 
-We continue to track issues on our GitHub issues list which can be found at: [http://github.com/nuget/home/issues](http://github.com/nuget/home/issues)
+We continue to track issues on our GitHub issues list which can be found at: [https://github.com/nuget/home/issues](https://github.com/nuget/home/issues)
diff --git a/docs/release-notes/NuGet-3.4-RC.md b/docs/release-notes/NuGet-3.4-RC.md
@@ -43,4 +43,4 @@ The following features are available in this RC, with more planned for the 3.4 f
 
 ## Known Issues
 
-We continue to track issues on our GitHub issues list which can be found at: [http://github.com/nuget/home/issues](http://github.com/nuget/home/issues)
+We continue to track issues on our GitHub issues list which can be found at: [https://github.com/nuget/home/issues](https://github.com/nuget/home/issues)
diff --git a/docs/release-notes/NuGet-3.4.1.md b/docs/release-notes/NuGet-3.4.1.md
@@ -19,4 +19,4 @@ NuGet 3.4.1 was released March 30, 2016 at the same time as the Visual Studio 20
 * Corrected an issue with Visual Studio locating `lucene.net.dll`
 * All sources should not be the default repository source after a NuGet extension install or update.  You can opt-in to this feature from the configuration settings.
 
-We continue to track issues on our GitHub issues list which can be found at: [http://github.com/nuget/home/issues](http://github.com/nuget/home/issues)
+We continue to track issues on our GitHub issues list which can be found at: [https://github.com/nuget/home/issues](https://github.com/nuget/home/issues)
diff --git a/docs/release-notes/NuGet-3.4.md b/docs/release-notes/NuGet-3.4.md
@@ -54,11 +54,11 @@ The following features were previously added in the RC and have been updated or
     * Loading projects that have an init.ps1 script (like EntityFramework)
     * Publishing web content
 
-* **Workaround:** Ensure that your Windows 10 install has the latest patches applied, expecially the January 2016 (KB 3124263) or a later update.  More details are available on [GitHub issue #1638](http://github.com/nuget/home/issues/1638)
+* **Workaround:** Ensure that your Windows 10 install has the latest patches applied, expecially the January 2016 (KB 3124263) or a later update.  More details are available on [GitHub issue #1638](https://github.com/nuget/home/issues/1638)
 
 * **Issue:** NuGet v2 protocol redirects are broken.
 Custom NuGet repositories that redirect requests to an alternative host do not honor the redirect request.
 * **Workaround:**  To work around this issue, configure the package repository URI in settings to point to the redirected server location.
 For more information, see [GitHub pull request #387](https://github.com/NuGet/NuGet.Client/pull/387).
 
-We continue to track issues on our GitHub issues list which can be found at: [http://github.com/nuget/home/issues](http://github.com/nuget/home/issues)
+We continue to track issues on our GitHub issues list which can be found at: [https://github.com/nuget/home/issues](https://github.com/nuget/home/issues)
diff --git a/docs/release-notes/NuGet-4.0-RC.md b/docs/release-notes/NuGet-4.0-RC.md
diff --git a/docs/release-notes/NuGet-5.8.md b/docs/release-notes/NuGet-5.8.md
diff --git a/docs/visual-studio-extensibility/nuget-api-in-visual-studio.md b/docs/visual-studio-extensibility/nuget-api-in-visual-studio.md
