Links: .NET (2021-01) (#22319)

Author: DCtheGeek

docs/architecture/blazor-for-web-forms-developers/project-structure.md

@@ -215,7 +215,7 @@ In the Blazor WebAssembly app, the host page is a simple static HTML file under
 
 ```
 
-The root component to render is configured in the app's `Program.Main` method with the flexibility to register different services through dependency injection.You can refer add services to an app in [Blazor WebAssembly](https://docs.microsoft.com/aspnet/core/blazor/fundamentals/dependency-injection?view=aspnetcore-5.0#blazor-webassembly)
+The root component to render is specified in the app's `Program.Main` method with the flexibility to register services through dependency injection. For more information, see [ASP.NET Core Blazor dependency injection](/aspnet/core/blazor/fundamentals/dependency-injection?pivots=webassembly).
 
 ```csharp
 public class Program

docs/architecture/modern-web-apps-azure/common-client-side-web-technologies.md

@@ -162,7 +162,7 @@ Running .NET code inside web browsers is made possible by WebAssembly (abbreviat
 
 WebAssembly code can access the full functionality of the browser via JavaScript, called JavaScript interoperability, often shortened to JavaScript interop or JS interop. .NET code executed via WebAssembly in the browser runs in the browser's JavaScript sandbox with the protections that the sandbox provides against malicious actions on the client machine.
 
-For more details, see [Introduction to ASP.NET Core Blazor](https://docs.microsoft.com/aspnet/core/blazor/?view=aspnetcore-5.0)
+For more information, see [Introduction to ASP.NET Core Blazor](/aspnet/core/blazor/).
 
 ### Choosing a SPA Framework
 

docs/azure/migration/app-service.md

@@ -18,7 +18,7 @@ Verify access to on-premises resources as these may need to be migrated or chang
 
 * Create a VPN connecting App Service to on-premises resources using [Azure Virtual Networks](/azure/app-service/web-sites-integrate-with-vnet).
 * Securely expose on-premises services to the cloud without firewall changes using [Azure Relay](/azure/service-bus-relay/relay-what-is-it).
-* Migrate dependencies such as a [SQL database](https://go.microsoft.com/fwlink/?linkid=863217) to Azure.
+* Migrate dependencies such as a [SQL database](./sql.md) to Azure.
 * Use platform-as-a-service offerings in the cloud to reduce dependencies. For example, rather than connect to an on-premises mail server, consider using [SendGrid](/azure/sendgrid-dotnet-how-to-send-email).
 
 ### Port Bindings

docs/azure/migration/vm.md

@@ -21,7 +21,7 @@ These tutorials demonstrate the steps to create (or migrate) a virtual machine,
   - [Create a new virtual machine for ASP.NET Applications](https://go.microsoft.com/fwlink/?linkid=863237)
   - [Migrate an existing on-premises VMWare virtual machine](/azure/migrate/tutorial-migrate-vmware)
   - [Migrate an existing on-premises Hyper-V virtual machine](/azure/migrate/tutorial-migrate-hyper-v)
-- [Publish your app using Visual Studio](https://go.microsoft.com/fwlink/?linkid=863240)
+- [Publish your app using Visual Studio](/azure/virtual-machines/windows/publish-web-app-from-visual-studio)
 - [Create a secure virtual network for your VMs](/azure/virtual-network/virtual-network-get-started-vnet-subnet)
 - [Create a CI/CD pipeline for your application](/vsts/build-release/apps/cd/deploy-webdeploy-iis-deploygroups)
 - [Move to a VM scale set for high availability and scalability](/azure/virtual-machine-scale-sets/virtual-machine-scale-sets-deploy-app)

docs/azure/sdk/azure-sdk-for-dotnet.md

@@ -27,4 +27,4 @@ To use an Azure SDK package in one of your .NET applications, you want to follow
 
 3. **Write code using the SDK in your application -** When working with Azure services, your code will first create a client object to work with the service and then call methods on that client object to interact with the service.  Both synchronous and asynchronous methods are provided.  Examples of using each individual SDK package are provided throughout the Azure documentation.
 
-4. **Configure logging for the SDK (optional) -** If you need to diagnose issues between your application and Azure, you can [enable logging in the Azure SDK for .NET](./logging.md).
+4. **Configure logging for the SDK (optional) -** If you need to diagnose issues between your application and Azure, you can [enable logging in the Azure SDK for .NET](../logging.md).

docs/core/additional-tools/self-signed-certificates-guide.md

@@ -205,7 +205,7 @@ dotnet dev-certs https --clean
 
 ### With PowerShell
 
-You can use PowerShell to generate self-signed certificates. The [PKI Client](https://docs.microsoft.com/powershell/module/pkiclient/new-selfsignedcertificate?view=win10-ps&preserver-view=true) can be used to generate a self-signed certificate.
+You can use PowerShell to generate self-signed certificates. The [PKI Client](/powershell/module/pkiclient/new-selfsignedcertificate?preserve-view=true&view=win10-ps) can be used to generate a self-signed certificate.
 
 ```powershell
 $cert = New-SelfSignedCertificate -DnsName @("contoso.com", "www.contoso.com") -CertStoreLocation "cert:\LocalMachine\My"

docs/core/compatibility/core-libraries/5.0/binaryformatter-serialization-obsolete.md

@@ -69,7 +69,7 @@ These methods are marked obsolete as part of an effort to wind down usage of <xr
   </PropertyGroup>
   ```
 
-For more information about recommended actions, see [Resolving BinaryFormatter obsoletion and disablement errors](https://aka.ms/binaryformatter).
+For more information about recommended actions, see [Resolving BinaryFormatter obsoletion and disablement errors](../../../../standard/serialization/binaryformatter-security-guide.md).
 
 ## Affected APIs
 

docs/core/compatibility/syslib-warnings/syslib0011.md

@@ -19,11 +19,11 @@ Due to [security vulnerabilities](../../../standard/serialization/binaryformatte
 
 Consider using <xref:System.Text.Json.JsonSerializer> or <xref:System.Xml.Serialization.XmlSerializer> instead of <xref:System.Runtime.Serialization.Formatters.Binary.BinaryFormatter>.
 
-For more information about recommended actions, see [Resolving BinaryFormatter obsoletion and disablement errors](https://aka.ms/binaryformatter).
+For more information about recommended actions, see [Resolving BinaryFormatter obsoletion and disablement errors](../../../standard/serialization/binaryformatter-security-guide.md).
 
 [!INCLUDE [suppress-syslib-warning](../../../../includes/suppress-syslib-warning.md)]
 
 ## See also
 
-- [Resolving BinaryFormatter obsoletion and disablement errors](https://aka.ms/binaryformatter)
+- [Resolving BinaryFormatter obsoletion and disablement errors](../../../standard/serialization/binaryformatter-security-guide.md)
 - [BinaryFormatter serialization methods are obsolete and prohibited in ASP.NET apps](../core-libraries/5.0/binaryformatter-serialization-obsolete.md)

docs/core/diagnostics/dumps.md

@@ -14,7 +14,6 @@ Dumps can be collected in a variety of ways depending on which platform you are
 
 > [!NOTE]
 > Collecting a dump inside a container requires PTRACE capability, which can be added via `--cap-add=SYS_PTRACE` or `--privileged`.
-
 > [!NOTE]
 > Dumps may contain sensitive information because they can contain the full memory of the running process. Handle them with any security restrictions and guidances in mind.
 
@@ -48,11 +47,10 @@ To collect dump at your own request, you can use `dotnet-dump`, which is a CLI t
 
 ## Analyze dumps
 
-You can anlayze dumps using the [`dotnet-dump`](dotnet-dump.md) CLI tool or with [Visual Studio](https://docs.microsoft.com/visualstudio/debugger/using-dump-files).
+You can anlayze dumps using the [`dotnet-dump`](dotnet-dump.md) CLI tool or with [Visual Studio](/visualstudio/debugger/using-dump-files).
 
 > [!NOTE]
 > Visual Studio version 16.8 and later allows you to [open Linux dumps](https://devblogs.microsoft.com/visualstudio/linux-managed-memory-dump-debugging/) generated on .NET Core 3.1.7 or later.  
-
 > [!NOTE]
 > If native debugging is necessary, the [SOS debugger extension](sos-debugging-extension.md) can be used with [LLDB on Linux and macOS](debug-linux-dumps.md#analyze-dumps-on-linux). SOS is also supported with [Windbg/cdb](/windows-hardware/drivers/debugger/debugger-download-tools) on Windows, although Visual Studio is recommended.
 

docs/core/diagnostics/index.md

@@ -63,7 +63,7 @@ The [dotnet-gcdump](dotnet-gcdump.md) tool is a way to collect GC (Garbage Colle
 
 ### dotnet-sos
 
-[dotnet-sos](dotnet-sos.md) installs the [SOS debugging extension](sos-debugging-extension.md) on Linux and macOS (and on Windows if you're using [Windbg/cdb](https://docs.microsoft.com/windows-hardware/drivers/debugger/debugger-download-tools)).
+[dotnet-sos](dotnet-sos.md) installs the [SOS debugging extension](sos-debugging-extension.md) on Linux and macOS (and on Windows if you're using [Windbg/cdb](/windows-hardware/drivers/debugger/debugger-download-tools)).
 
 ### PerfCollect
 

docs/core/introduction.md

@@ -18,7 +18,7 @@ ms.custom: "updateeachrelease"
   * [Windows Forms](/dotnet/desktop/winforms/)
   * [Universal Windows Platform (UWP)](/windows/uwp/get-started/create-a-hello-world-app-xaml-universal)
 * [Games](https://dotnet.microsoft.com/apps/games)
-* [Internet of Things (IoT)](/dotnet/iot)
+* [Internet of Things (IoT)](../iot/index.yml)
 * [Machine learning](../machine-learning/index.yml)
 * [Console apps](tutorials/with-visual-studio-code.md)
 * [Windows services](/aspnet/core/host-and-deploy/windows-service)

docs/core/tools/sdk-errors/netsdk1059.md

@@ -11,4 +11,4 @@ f1_keywords:
 
 **This article applies to:** ✔️ .NET Core 2.1.100 SDK and later versions
 
-When the .NET SDK issues warning NETSDK1059, your project contains an obsolete .NET CLI tool. As of .NET Core 2.1, these tools are included in the .NET SDK and do not need to be explicitly referenced by the project. More information for migrating to .NET Core 2.1 can be found [here](https://aka.ms/dotnetclitools-in-box).
+When the .NET SDK issues warning NETSDK1059, your project contains an obsolete .NET CLI tool. As of .NET Core 2.1, these tools are included in the .NET SDK and do not need to be explicitly referenced by the project. More information for migrating to .NET Core 2.1 can be found [here](../../migration/20-21.md).

docs/framework/data/adonet/method-based-query-syntax-examples-join-linq-to-dataset.md

@@ -45,5 +45,3 @@ Joining is an important operation in queries that target data sources that have
 - [LINQ to DataSet Examples](linq-to-dataset-examples.md)
 - [Standard Query Operators Overview (C#)](../../../csharp/programming-guide/concepts/linq/standard-query-operators-overview.md)
 - [Standard Query Operators Overview (Visual Basic)](../../../visual-basic/programming-guide/concepts/linq/standard-query-operators-overview.md)
-- [Join Samples](https://go.microsoft.com/fwlink/?LinkId=187357)
-- [Dataset Samples](https://go.microsoft.com/fwlink/?LinkId=187358)

docs/framework/data/wcf/wcf-data-services-protocol-implementation-details.md

@@ -11,7 +11,7 @@ The Open Data Protocol (OData) requires that a data service that implements the
 
 ### Support for the $format Query Option  
 
- The OData protocol supports both JavaScript Notation (JSON) and Atom feeds, and OData provides the `$format` system query option to allow a client to request the format of the response feed. This system query option, if supported by the data service, must override the value of the Accept header of the request. WCF Data Services supports returning both JSON and Atom feeds. However, the default implementation does not support the `$format` query option and uses only the value of the Accept header to determine the format of the response. There are cases when your data service may need to support the `$format` query option, such as when clients cannot set the Accept header. To support these scenarios, you must extend your data service to handle this option in the URI. You can add this functionality to your data service by downloading the [JSONP and URL-controlled format support for ADO.NET Data Services](https://go.microsoft.com/fwlink/?LinkId=208228) sample project from the MSDN Code Gallery web site and adding it to your data service project. This sample removes the `$format` query option and changes the Accept header to `application/json`. When you include the sample project and adding the `JSONPSupportBehaviorAttribute` to your data service class enables the service to handle the `$format` query option `$format=json`. Further customization of this sample project is required to also handle `$format=atom` or other custom formats.  
+ The OData protocol supports both JavaScript Notation (JSON) and Atom feeds, and OData provides the `$format` system query option to allow a client to request the format of the response feed. This system query option, if supported by the data service, must override the value of the Accept header of the request. WCF Data Services supports returning both JSON and Atom feeds. However, the default implementation does not support the `$format` query option and uses only the value of the Accept header to determine the format of the response. There are cases when your data service may need to support the `$format` query option, such as when clients cannot set the Accept header. To support these scenarios, you must extend your data service to handle this option in the URI.
 
 ## WCF Data Services Behaviors  
 

docs/framework/deployment/deployment-guide-for-developers.md

@@ -310,19 +310,19 @@ The following table lists the most common return codes for the .NET Framework re
 
 See the following content:
 
-- [Background Intelligent Transfer Service (BITS) error codes](https://go.microsoft.com/fwlink/?LinkId=180946)
+- [Background Intelligent Transfer Service (BITS) error codes](/windows/win32/bits/bits-return-values)
 
-- [URL moniker error codes](https://go.microsoft.com/fwlink/?LinkId=180947)
+- [URL moniker error codes](/previous-versions/windows/internet-explorer/ie-developer/platform-apis/ms775145(v=vs.85))
 
-- [WinHttp error codes](https://go.microsoft.com/fwlink/?LinkId=180948)
+- [WinHttp error codes](/windows/win32/winhttp/error-messages)
 
 #### Other error codes
 
 See the following content:
 
-- [Windows Installer error codes](https://go.microsoft.com/fwlink/?LinkId=180949)
+- [Windows Installer error codes](/previous-versions/aa368542(v=vs.85))
 
-- [Windows Update Agent result codes](https://go.microsoft.com/fwlink/?LinkId=180951)
+- [Windows Update Agent result codes](/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/cc720442(v=ws.10))
 
 ## Uninstalling the .NET Framework
 

docs/framework/install/guide-for-developers.md

@@ -128,7 +128,7 @@ Both web and offline installers are designed for x86-based and x64-based compute
 
 - .NET Framework 4.5 and later versions replace .NET Framework 4.0. When you install these versions on a system that has .NET Framework 4 installed, the assemblies are replaced.
 
-- Uninstalling .NET Framework 4.5 or later versions also removes pre-existing .NET Framework 4 files. If you want to go back to .NET Framework 4, you must reinstall it and any updates to it. See [Installing the .NET Framework 4](https://go.microsoft.com/fwlink/p/?LinkId=230665).
+- Uninstalling .NET Framework 4.5 or later versions also removes pre-existing .NET Framework 4 files. If you want to go back to .NET Framework 4, you must reinstall it and any updates to it. See [Installing the .NET Framework 4](/previous-versions/dotnet/netframework-4.0/5a4x27ek(v=vs.100)).
 
 - You must have administrative credentials to install .NET Framework 4.5 or later versions.
 

docs/framework/network-programming/peer-name-resolution-protocol.md

@@ -47,7 +47,3 @@ The Peer Name Resolution Protocol demonstrates the following properties:
 - <xref:System.ServiceModel.PeerResolvers>
 - <xref:System.Net.PeerToPeer>
 - [Network Programming Samples](network-programming-samples.md)
-
-<!-- to-do: review sample links
-- [PeerToPeer Technology Sample](https://go.microsoft.com/fwlink/?LinkID=179571)
--->

docs/framework/wcf/feature-details/side-by-side-versioning-in-workflowservicehost.md

@@ -10,9 +10,6 @@ ms.assetid: 60887eed-df40-4412-b812-41e1dd329d15
 
 The <xref:System.ServiceModel.Activities.WorkflowServiceHost> side-by-side versioning introduced in .NET Framework 4.5 provides the capability to host multiple versions of a workflow service on a single endpoint. The side-by-side functionality provided allows a workflow service to be configured so that new instances of the workflow service are created using the new workflow definition, while running instances complete using the existing definition. This topic provides an overview of workflow service side-by-side execution using <xref:System.ServiceModel.Activities.WorkflowServiceHost>.  
 
-> [!NOTE]
-> To download a sample and watch a video walkthrough of workflow service side-by-side versioning, see [Side by Side Versioning with a Web-Hosted Xamlx Workflow Service](https://go.microsoft.com/fwlink/?LinkId=393746).  
-  
 ## Hosting Multiple Versions in a Workflow Service  
 
  <xref:System.ServiceModel.Activities.WorkflowServiceHost> contains two properties that can be configured to allow multiple versions of a workflow to execute side-by-side: <xref:System.ServiceModel.Activities.WorkflowServiceHost.SupportedVersions%2A> and <xref:System.ServiceModel.Activities.WorkflowService.DefinitionIdentity%2A>. <xref:System.ServiceModel.Activities.WorkflowServiceHost.SupportedVersions%2A> contains the supported versions of the workflow service, and <xref:System.ServiceModel.Activities.WorkflowService.DefinitionIdentity%2A> is used to uniquely identify each workflow service. This is done by associating a <xref:System.Activities.WorkflowIdentity> with the workflow service. A <xref:System.Activities.WorkflowIdentity> contains three identifying pieces of information. <xref:System.Activities.WorkflowIdentity.Name%2A> and <xref:System.Activities.WorkflowIdentity.Version%2A> contain a name and a <xref:System.Version> and are required, and <xref:System.Activities.WorkflowIdentity.Package%2A> is optional and can be used to specify an additional string containing information such as assembly name or other desired information. Each workflow service contained in the <xref:System.ServiceModel.Activities.WorkflowServiceHost.SupportedVersions%2A> collection must have a unique <xref:System.Activities.WorkflowIdentity>. A <xref:System.Activities.WorkflowIdentity> is unique if any of its three properties are different from another <xref:System.Activities.WorkflowIdentity>. A `null` <xref:System.Activities.WorkflowIdentity> is an allowable value for <xref:System.ServiceModel.Activities.WorkflowService.DefinitionIdentity%2A>, but only one previous version of a workflow service may have a `null` <xref:System.Activities.WorkflowIdentity>.  

docs/framework/windows-workflow-foundation/dynamic-update.md

@@ -54,9 +54,6 @@ ActivityBuilder ab = XamlServices.Load(
 DynamicUpdateServices.PrepareForUpdate(ab);
 ```
 
-> [!NOTE]
-> To download the sample code that accompanies this topic, see [Dynamic Update sample code](https://go.microsoft.com/fwlink/?LinkId=227905).
-
 ### <a name="Update"></a> Update the workflow definition to reflect the desired changes
 
 Once the workflow definition has been prepared for updating, the desired changes can be made. You can add or remove activities, add, move or delete public variables, add or remove arguments, and make changes to the signature of activity delegates. You cannot remove a running activity or change the signature of a running delegate. These changes may be made using code, or in a re-hosted workflow designer. In the following example, a custom `VerifyAppraisal` activity is added to the Sequence that makes up the body of the `MortgageWorkflow` from the previous example.
@@ -191,6 +188,3 @@ wfApp.Load(InstanceId);
 // Resume the workflow.
 // wfApp.ResumeBookmark(...);
 ```
-
-> [!NOTE]
-> To download the sample code that accompanies this topic, see [Dynamic Update sample code](https://go.microsoft.com/fwlink/?LinkId=227905).

docs/framework/windows-workflow-foundation/how-to-create-a-custom-tracking-participant.md

@@ -10,9 +10,6 @@ ms.assetid: 1b612c7e-2381-4a7c-b07a-77030415f2a3
 
 Workflow tracking provides visibility into the status of workflow execution. The workflow runtime emits tracking records that describe workflow lifecycle events, activity lifecycle events, bookmark resumptions, and faults. These tracking records are consumed by tracking participants. Windows Workflow Foundation (WF) includes a standard tracking participant that writes tracking records as Event Tracing for Windows (ETW) events. If that does not meet your requirements, you can also write a custom tracking participant. This tutorial step describes how to create a custom tracking participant and tracking profile that capture the output of `WriteLine` activities so that they can be displayed to the user.  
 
-> [!NOTE]
-> Each topic in the Getting Started tutorial depends on the previous topics. To complete this topic, you must first complete the previous topics. To download a completed version or view a video walkthrough of the tutorial, see [Windows Workflow Foundation (WF45) - Getting Started Tutorial](https://go.microsoft.com/fwlink/?LinkID=248976).  
-  
 ## To create the custom tracking participant  
 
 1. Right-click **NumberGuessWorkflowHost** in **Solution Explorer** and choose **Add**, **Class**. Type `StatusTrackingParticipant` into the **Name** box, and click **Add**.