Merge pull request NuGet#2170 from DCtheGeek/dmc-links-pass1

Links: NuGet - Pass 1

Author: JonDouglas

docs/api/search-query-service-resource.md

@@ -118,7 +118,7 @@ packageTypes   | array of objects           | yes      | The package types defin
 
 On nuget.org, a verified package is one which has a package ID matching a reserved ID prefix and owned by one of the
 reserved prefix's owners. For more information, see the
-[documentation about ID prefix reservation](../reference/id-prefix-reservation.md).
+[documentation about ID prefix reservation](../nuget-org/id-prefix-reservation.md).
 
 The metadata contained in the search result object is taken from the latest package version. Each item in the
 `versions` array is a JSON object with the following properties:
@@ -141,4 +141,4 @@ name      | string  | yes      | The name of the package type.
 
 ### Sample response
 
-[!code-JSON [search-result.json](./_data/search-result.json)]
+[!code-JSON [search-result.json](./_data/search-result.json)]

docs/consume-packages/install-use-packages-powershell.md

@@ -163,7 +163,7 @@ $profile
 C:\Users\<user>\Documents\WindowsPowerShell\NuGet_profile.ps1
 ```
 
-For more details, refer to [Windows PowerShell Profiles](https://technet.microsoft.com/library/bb613488.aspx).
+For more details, refer to [Windows PowerShell Profiles](/previous-versions//bb613488(v=vs.85)).
 
 ## Use the nuget.exe CLI in the console
 
@@ -172,4 +172,4 @@ To make the [`nuget.exe` CLI](../reference/nuget-exe-cli-reference.md) available
 ```ps
 # Other versions are available, see https://www.nuget.org/packages/NuGet.CommandLine/
 Install-Package NuGet.CommandLine -Version 4.4.1
-```
+```

docs/create-packages/Sign-a-Package.md

@@ -14,7 +14,7 @@ Signed packages allows for content integrity verification checks which provides
 
 ## Get a code signing certificate
 
-Valid certificates may be obtained from a public certificate authority such as [Symantec](https://trustcenter.websecurity.symantec.com/process/trust/productOptions?productType=SoftwareValidationClass3), [DigiCert](https://www.digicert.com/code-signing/), [Go Daddy](https://www.godaddy.com/web-security/code-signing-certificate), [Global Sign](https://www.globalsign.com/en/code-signing-certificate/), [Comodo](https://www.comodo.com/e-commerce/code-signing/code-signing-certificate.php), [Certum](https://www.certum.eu/certum/cert,offer_en_open_source_cs.xml), etc. The complete list of certification authorities trusted by Windows can be obtained from [http://aka.ms/trustcertpartners](https://aka.ms/trustcertpartners).
+Valid certificates may be obtained from a public certificate authority such as [Symantec](https://trustcenter.websecurity.symantec.com/process/trust/productOptions?productType=SoftwareValidationClass3), [DigiCert](https://www.digicert.com/code-signing/), [Go Daddy](https://www.godaddy.com/web-security/code-signing-certificate), [Global Sign](https://www.globalsign.com/en/code-signing-certificate/), [Comodo](https://www.comodo.com/e-commerce/code-signing/code-signing-certificate.php), [Certum](https://www.certum.eu/certum/cert,offer_en_open_source_cs.xml), etc. The complete list of certification authorities trusted by Windows can be obtained from [http://aka.ms/trustcertpartners](/security/trusted-root/participants-list).
 
 You can use self-issued certificates for testing purposes. However, packages signed using self-issued certificates are not accepted by NuGet.org. Learn more about [creating a test certificate](#create-a-test-certificate)
 
@@ -99,4 +99,4 @@ This command creates a testing certificate available in the current user's perso
 ## Related articles
 
 - [Manage package trust boundaries](../consume-packages/installing-signed-packages.md)
-- [Signed Packages Reference](../reference/Signed-Packages-Reference.md)
+- [Signed Packages Reference](../reference/Signed-Packages-Reference.md)

docs/create-packages/Source-and-Config-File-Transformations.md

@@ -47,7 +47,7 @@ The `$rootnamespace$` token is the most commonly used project property; all othe
 As described in the sections that follow, config file transformations can be done in two ways:
 
 - Include `app.config.transform` and `web.config.transform` files in your package's `content` folder, where the `.transform` extension tells NuGet that these files contain the XML to merge with existing config files when the package is installed. When a package is uninstalled, that same XML is removed.
-- Include `app.config.install.xdt` and `web.config.install.xdt` files in your package's `content` folder, using [XDT syntax](https://msdn.microsoft.com/library/dd465326.aspx) to describe the desired changes. With this option you can also include a `.uninstall.xdt` file to reverse changes when the package is removed from a project.
+- Include `app.config.install.xdt` and `web.config.install.xdt` files in your package's `content` folder, using [XDT syntax](/previous-versions/aspnet/dd465326(v=vs.110)) to describe the desired changes. With this option you can also include a `.uninstall.xdt` file to reverse changes when the package is removed from a project.
 
 > [!Note]
 > Transformations are not applied to `.config` files referenced as a link in Visual Studio.
@@ -110,7 +110,7 @@ To see the effect of installing and uninstalling the package, create a new ASP.N
 > [!Note]
 > As mentioned in the [package compatibility issues section of the docs for migrating from `packages.config` to `PackageReference`](../consume-packages/migrate-packages-config-to-package-reference.md#package-compatibility-issues), XDT transformations as described below are only supported by `packages.config`. If you add the below files to your package, consumers using your package with `PackageReference` will not have the transformations applied (refer to [this sample](https://github.com/NuGet/Samples/tree/master/XDTransformExample) to make XDT transforms work with`PackageReference`).
 
-You can modify config files using [XDT syntax](https://msdn.microsoft.com/library/dd465326.aspx). You can also have NuGet replace tokens with [project properties](/dotnet/api/vslangproj.projectproperties?view=visualstudiosdk-2017&viewFallbackFrom=netframework-4.7) by including the property name within `$` delimiters (case-insensitive).
+You can modify config files using [XDT syntax](/previous-versions/aspnet/dd465326(v=vs.110)). You can also have NuGet replace tokens with [project properties](/dotnet/api/vslangproj.projectproperties?view=visualstudiosdk-2017&viewFallbackFrom=netframework-4.7) by including the property name within `$` delimiters (case-insensitive).
 
 For example, the following `app.config.install.xdt` file will insert an `appSettings` element into `app.config` containing the `FullPath`, `FileName`, and `ActiveConfigurationSettings` values from the project:
 
@@ -174,4 +174,4 @@ To remove only the `MyNuModule` element during package uninstall, the `web.confi
         </modules>
     </system.webServer>
 </configuration>
-```
+```

docs/create-packages/Supporting-Multiple-Target-Frameworks.md

@@ -66,7 +66,7 @@ Please note, NuGet always picks these compile or runtime assets from one folder
 
 See [Create UWP Packages](../guides/create-uwp-packages.md) for an example of referencing these files in the `.nuspec` manifest.
 
-Also, see [Packing a Windows store app component with NuGet](https://blogs.msdn.microsoft.com/mim/2013/09/02/packaging-a-windows-store-apps-component-with-nuget-part-2)
+Also, see [Packing a Windows store app component with NuGet](/archive/blogs/mim/packaging-a-windows-store-apps-component-with-nuget-part-2)
 
 ## Matching assembly versions and the target framework in a project
 
@@ -177,4 +177,4 @@ With `packages.config`, content files and PowerShell scripts can be grouped by t
 If a framework folder is left empty, NuGet doesn't add assembly references or content files or run the PowerShell scripts for that framework.
 
 > [!Note]
-> Because `init.ps1` is executed at the solution level and not dependent on project, it must be placed directly under the `tools` folder. It's ignored if placed under a framework folder.
+> Because `init.ps1` is executed at the solution level and not dependent on project, it must be placed directly under the `tools` folder. It's ignored if placed under a framework folder.

docs/create-packages/creating-a-package-msbuild.md

@@ -9,7 +9,7 @@ ms.topic: conceptual
 
 # Create a NuGet package using MSBuild
 
-When you create a NuGet package from your code, you package that functionality into a component that can be shared with and used by any number of other developers. This article describes how to create a package using MSBuild. MSBuild comes preinstalled with every Visual Studio workload that contains NuGet. Additionally you can also use MSBuild through the dotnet CLI with [dotnet msbuild](https://docs.microsoft.com/dotnet/core/tools/dotnet-msbuild).
+When you create a NuGet package from your code, you package that functionality into a component that can be shared with and used by any number of other developers. This article describes how to create a package using MSBuild. MSBuild comes preinstalled with every Visual Studio workload that contains NuGet. Additionally you can also use MSBuild through the dotnet CLI with [dotnet msbuild](/dotnet/core/tools/dotnet-msbuild).
 
 For .NET Core and .NET Standard projects that use the [SDK-style format](../resources/check-project-format.md), and any other SDK-style projects, NuGet uses information in the project file directly to create a package.  For a non-SDK-style project that uses `<PackageReference>`, NuGet also uses the project file to create a package.
 
@@ -184,4 +184,4 @@ You might also want to extend the capabilities of your package or otherwise supp
 Finally, there are additional package types to be aware of:
 
 - [Native Packages](../guides/native-packages.md)
-- [Symbol Packages](../create-packages/symbol-packages-snupkg.md)
+- [Symbol Packages](../create-packages/symbol-packages-snupkg.md)

docs/guides/Create-UI-Controls.md

@@ -89,7 +89,7 @@ Supported formats are `.png`, `.jpg`, `.jpeg`, `.gif`, and `.bmp`. The recommend
 
 ![Tool box icon sample](https://raw.githubusercontent.com/NuGet/docs.microsoft.com-nuget/live/docs/guides/media/ColorPicker_16x16x24.bmp)
 
-The pink background is replaced at runtime. The icons are recolored when the Visual Studio theme is changed and that background color is expected. For more information, please reference [Images and Icons for Visual Studio](https://docs.microsoft.com/visualstudio/extensibility/ux-guidelines/images-and-icons-for-visual-studio).
+The pink background is replaced at runtime. The icons are recolored when the Visual Studio theme is changed and that background color is expected. For more information, please reference [Images and Icons for Visual Studio](/visualstudio/extensibility/ux-guidelines/images-and-icons-for-visual-studio).
 
 In the example below, the project contains an image file named “ManagedPackage.MyCustomControl.png”.
 
@@ -152,4 +152,4 @@ For an example, refer to [MyCustomControl.cs](https://github.com/NuGet/Samples/b
 ## See also
 
 - [Create UWP Packages](create-uwp-packages.md)
-- [ExtensionSDKasNuGetPackage sample](https://github.com/NuGet/Samples/tree/master/ExtensionSDKasNuGetPackage)
+- [ExtensionSDKasNuGetPackage sample](https://github.com/NuGet/Samples/tree/master/ExtensionSDKasNuGetPackage)

docs/guides/Create-UWP-Packages-CS.md

@@ -17,7 +17,7 @@ In this walkthrough you create a NuGet package with a C# UWP component (includin
 
 1. Visual Studio 2019. Install the 2019 Community edition for free from [visualstudio.com](https://www.visualstudio.com/); you can use the Professional and Enterprise editions as well.
 
-1. NuGet CLI. Download the latest version of `nuget.exe` from [nuget.org/downloads](https://nuget.org/downloads), saving it to a location of your choice (the download is the `.exe` directly). Then add that location to your PATH environment variable if it isn't already. [More details](/nuget/reference/nuget-exe-cli-reference#windows).
+1. NuGet CLI. Download the latest version of `nuget.exe` from [nuget.org/downloads](https://nuget.org/downloads), saving it to a location of your choice (the download is the `.exe` directly). Then add that location to your PATH environment variable if it isn't already. [More details](../reference/nuget-exe-cli-reference.md#windows).
 
 ## Create a UWP Windows Runtime component
 
@@ -47,7 +47,7 @@ In this walkthrough you create a NuGet package with a C# UWP component (includin
 To create the initial `.nuspec` file, do the three steps below. The sections that follow then guide you through other necessary updates.
 
 1. Open a command prompt and navigate to the folder containing `ImageEnhancer.csproj` (this will be a subfolder below where the solution file is).
-1. Run the [`NuGet spec`](/nuget/reference/cli-reference/cli-ref-spec) command to generate `ImageEnhancer.nuspec` (the name of the file is taken from the name of the `.csroj` file):
+1. Run the [`NuGet spec`](../reference/cli-reference/cli-ref-spec.md) command to generate `ImageEnhancer.nuspec` (the name of the file is taken from the name of the `.csroj` file):
 
     ```cli
     nuget spec
@@ -192,7 +192,7 @@ Your final `.nuspec` file should now look like the following, where again YOUR_N
 
 ## Package the component
 
-With the completed `.nuspec` referencing all the files you need to include in the package, you're ready to run the [`nuget pack`](/nuget/reference/cli-reference/cli-ref-pack) command:
+With the completed `.nuspec` referencing all the files you need to include in the package, you're ready to run the [`nuget pack`](../reference/cli-reference/cli-ref-pack.md) command:
 
 ```cli
 nuget pack ImageEnhancer.nuspec
@@ -214,4 +214,4 @@ To make your package available to other developers,  follow the instructions on
 - [Package versioning](../concepts/package-versioning.md)
 - [Supporting Multiple .NET Framework Versions](../create-packages/supporting-multiple-target-frameworks.md)
 - [Include MSBuild props and targets in a package](../create-packages/creating-a-package.md#include-msbuild-props-and-targets-in-a-package)
-- [Creating Localized Packages](../create-packages/creating-localized-packages.md)
+- [Creating Localized Packages](../create-packages/creating-localized-packages.md)

docs/guides/analyzers-conventions.md

@@ -9,7 +9,7 @@ ms.topic: conceptual
 
 # Analyzer NuGet formats
 
-The .NET Compiler Platform (also known as "Roslyn") allows developers to create [analyzers](https://github.com/dotnet/roslyn/wiki/How-To-Write-a-C%23-Analyzer-and-Code-Fix) that examine the syntax tree and semantics of code as it's being written. This provides developers with a way to create domain-specific analysis tools, such as those that would help guide the use of a particular API or library. You can find more information on the [.NET/Roslyn](https://github.com/dotnet/roslyn/wiki) GitHub wiki. Also see the article, [Use Roslyn to Write a Live Code Analyzer for your API](https://msdn.microsoft.com/magazine/dn879356.aspx) in MSDN Magazine.
+The .NET Compiler Platform (also known as "Roslyn") allows developers to create [analyzers](https://github.com/dotnet/roslyn/wiki/How-To-Write-a-C%23-Analyzer-and-Code-Fix) that examine the syntax tree and semantics of code as it's being written. This provides developers with a way to create domain-specific analysis tools, such as those that would help guide the use of a particular API or library. You can find more information on the [.NET/Roslyn](https://github.com/dotnet/roslyn/wiki) GitHub wiki. Also see the article, [Use Roslyn to Write a Live Code Analyzer for your API](/archive/msdn-magazine/2014/special-issue/csharp-and-visual-basic-use-roslyn-to-write-a-live-code-analyzer-for-your-api) in MSDN Magazine.
 
 Analyzers themselves are typically packaged and distributed as part of the NuGet packages that implement the API or library in question.
 
@@ -163,4 +163,4 @@ foreach($analyzersPath in $analyzersPaths)
         }
     }
 }
-```
+```