Retire filemap link to dotnet/docs

.openpublishing.publish.config.json

@@ -8,7 +8,6 @@
       "xref_query_tags": ["/uwp/api"],
       "monikers": [],
       "moniker_ranges": [],
-      "filemap_share_depots": ["VS.core-docs"],
       "open_to_public_contributors": true,
       "type_mapping": {
         "Conceptual": "Content",

includes/calendar-era.md

@@ -1,3 +1,3 @@
 
 > [!IMPORTANT]
->  Eras in the Japanese calendars are based on the emperor's reign and are therefore expected to change. For example, May 1, 2019 marked the beginning of the Reiwa era in the <xref:System.Globalization.JapaneseCalendar> and <xref:System.Globalization.JapaneseLunisolarCalendar>. Such a change of era affects all applications that use these calendars. See [Handling a new era in the Japanese calendar in .NET](https://devblogs.microsoft.com/dotnet/handling-a-new-era-in-the-japanese-calendar-in-net/) for more information and to determine whether your applications are affected. See [Prepare your application for the Japanese era change](/windows/uwp/design/globalizing/japanese-era-change) for information on testing your applications on Windows systems to ensure their readiness for the era change. See [Working with eras](~/docs/standard/datetime/working-with-calendars.md#working-with-eras) for features in .NET that support calendars with multiple eras and for best practices when working with calendars that support multiple eras.
+>  Eras in the Japanese calendars are based on the emperor's reign and are therefore expected to change. For example, May 1, 2019 marked the beginning of the Reiwa era in the <xref:System.Globalization.JapaneseCalendar> and <xref:System.Globalization.JapaneseLunisolarCalendar>. Such a change of era affects all applications that use these calendars. See [Handling a new era in the Japanese calendar in .NET](https://devblogs.microsoft.com/dotnet/handling-a-new-era-in-the-japanese-calendar-in-net/) for more information and to determine whether your applications are affected. See [Prepare your application for the Japanese era change](/windows/uwp/design/globalizing/japanese-era-change) for information on testing your applications on Windows systems to ensure their readiness for the era change. See [Working with eras](/dotnet/standard/datetime/working-with-calendars#working-with-eras) for features in .NET that support calendars with multiple eras and for best practices when working with calendars that support multiple eras.

includes/interpolated-strings.md

@@ -1,3 +1,3 @@
 
 > [!IMPORTANT] 
-> Instead of calling the **String.Format** method or using [composite format strings](~/docs/standard/base-types/composite-formatting.md), you can use *interpolated strings* if your language supports them. An interpolated string is a string that contains *interpolated expressions*. Each interpolated expression is resolved with the expression's value and included in the result string when the string is assigned. For more information, see [String interpolation (C# Reference)](~/docs/csharp/language-reference/tokens/interpolated.md) and [Interpolated Strings (Visual Basic Reference)](~/docs/visual-basic/programming-guide/language-features/strings/interpolated-strings.md). 
+> Instead of calling the **String.Format** method or using [composite format strings](/dotnet/standard/base-types/composite-formatting), you can use *interpolated strings* if your language supports them. An interpolated string is a string that contains *interpolated expressions*. Each interpolated expression is resolved with the expression's value and included in the result string when the string is assigned. For more information, see [String interpolation (C# Reference)](/dotnet/csharp/language-reference/tokens/interpolated) and [Interpolated Strings (Visual Basic Reference)](/dotnet/visual-basic/programming-guide/language-features/strings/interpolated-strings). 

includes/provider-string-format.md

@@ -1,4 +1,4 @@
 
-However, when calling the **String.Format** method, it is not necessary to focus on the particular overload that you want to call. Instead, you can call the method with an object that provides culture-sensitive or custom formatting and a [composite format string](~/docs/standard/base-types/composite-formatting.md) that includes one or more format items. You assign each format item a numeric index; the first index starts at 0. In addition to the initial string, your method call should have as many additional arguments as it has index values. For example, a string whose format items have indexes of 0 and 1 should have 2 arguments; one with indexes 0 through 5 should have 6 arguments. Your language compiler will then resolve your method call to a particular overload of the **String.Format** method.   
+However, when calling the **String.Format** method, it is not necessary to focus on the particular overload that you want to call. Instead, you can call the method with an object that provides culture-sensitive or custom formatting and a [composite format string](/dotnet/standard/base-types/composite-formatting) that includes one or more format items. You assign each format item a numeric index; the first index starts at 0. In addition to the initial string, your method call should have as many additional arguments as it has index values. For example, a string whose format items have indexes of 0 and 1 should have 2 arguments; one with indexes 0 through 5 should have 6 arguments. Your language compiler will then resolve your method call to a particular overload of the **String.Format** method.   
 
 For more detailed documentation on using the **String.Format** method, see [Getting started with the String.Format method](#Starting) and [Which method do I call?](#FTaskList).   

includes/simple-string-format.md

@@ -1,4 +1,4 @@
 
-However, when calling the **String.Format** method, it is not necessary to focus on the particular overload that you want to call. Instead, you can call the method with a [composite format string](~/docs/standard/base-types/composite-formatting.md) that includes one or more format items. You assign each format item a numeric index; the first index starts at 0. In addition to the initial string, your method call should have as many additional arguments as it has index values. For example, a string whose format items have indexes of 0 and 1 should have 2 arguments; one with indexes 0 through 5 should have 6 arguments. Your language compiler will then resolve your method call to a particular overload of the **String.Format** method.   
+However, when calling the **String.Format** method, it is not necessary to focus on the particular overload that you want to call. Instead, you can call the method with a [composite format string](/dotnet/standard/base-types/composite-formatting) that includes one or more format items. You assign each format item a numeric index; the first index starts at 0. In addition to the initial string, your method call should have as many additional arguments as it has index values. For example, a string whose format items have indexes of 0 and 1 should have 2 arguments; one with indexes 0 through 5 should have 6 arguments. Your language compiler will then resolve your method call to a particular overload of the **String.Format** method.   
 
 For more detailed documentation on using the **String.Format** method, see [Getting started with the String.Format method](#Starting) and [Which method do I call?](#FTaskList).    

includes/thread-formatting.md

@@ -1,2 +1,2 @@
 
-For more information about the current thread culture, see the <xref:System.Globalization.CultureInfo.CurrentCulture?displayProperty=nameWithType> and <xref:System.Threading.Thread.CurrentCulture%2A?displayProperty=nameWithType> properties. For more information about format characters, format patterns, and the output they produce, see [Standard date and time format strings](~/docs/standard/base-types/standard-date-and-time-format-strings.md) and [Custom date and time format strings](~/docs/standard/base-types/custom-date-and-time-format-strings.md). For more information about changing the format pattern associated with a format character, see the <xref:System.Globalization.DateTimeFormatInfo> class.  
+For more information about the current thread culture, see the <xref:System.Globalization.CultureInfo.CurrentCulture?displayProperty=nameWithType> and <xref:System.Threading.Thread.CurrentCulture%2A?displayProperty=nameWithType> properties. For more information about format characters, format patterns, and the output they produce, see [Standard date and time format strings](/dotnet/standard/base-types/standard-date-and-time-format-strings) and [Custom date and time format strings](/dotnet/standard/base-types/custom-date-and-time-format-strings). For more information about changing the format pattern associated with a format character, see the <xref:System.Globalization.DateTimeFormatInfo> class.  

includes/tpl-install-instructions.md

@@ -1,2 +1,2 @@
 > [!NOTE]
-> The TPL Dataflow Library (the <xref:System.Threading.Tasks.Dataflow> namespace) is not distributed with .NET. To install the <xref:System.Threading.Tasks.Dataflow> namespace in Visual Studio, open your project, choose **Manage NuGet Packages** from the **Project** menu, and search online for the `System.Threading.Tasks.Dataflow` package. Alternatively, to install it using [the .NET Core CLI](~/docs/core/tools/index.md), run `dotnet add package System.Threading.Tasks.Dataflow`.
+> The TPL Dataflow Library (the <xref:System.Threading.Tasks.Dataflow> namespace) is not distributed with .NET. To install the <xref:System.Threading.Tasks.Dataflow> namespace in Visual Studio, open your project, choose **Manage NuGet Packages** from the **Project** menu, and search online for the `System.Threading.Tasks.Dataflow` package. Alternatively, to install it using [the .NET Core CLI](/dotnet/core/tools/), run `dotnet add package System.Threading.Tasks.Dataflow`.

includes/visual-property-note.md

@@ -1,3 +1,3 @@
 > [!NOTE]
->  Setting a visual property only has an effect if that property is both present in the control's default template and is set by using a [TemplateBinding](~/docs/framework/wpf/advanced/templatebinding-markup-extension.md). You can find a list of visual properties in the [Changing the Visual Structure of a Control](~/docs/framework/wpf/controls/customizing-the-appearance-of-an-existing-control.md#changing-the-visual-structure-of-a-control) section in the [Customizing the Appearance of an Existing Control by Creating a ControlTemplate](~/docs/framework/wpf/controls/customizing-the-appearance-of-an-existing-control.md) article.
+>  Setting a visual property only has an effect if that property is both present in the control's default template and is set by using a [TemplateBinding](/dotnet/framework/wpf/advanced/templatebinding-markup-extension). You can find a list of visual properties in the [Changing the Visual Structure of a Control](/dotnet/framework/wpf/controls/customizing-the-appearance-of-an-existing-control#changing-the-visual-structure-of-a-control) section in the [Customizing the Appearance of an Existing Control by Creating a ControlTemplate](/dotnet/framework/wpf/controls/customizing-the-appearance-of-an-existing-control) article.
 

xml/Microsoft.Build.BuildEngine/InvalidToolsetDefinitionException.xml

@@ -134,11 +134,11 @@
           <format type="text/markdown"><![CDATA[  
 
 ## Remarks  
- This constructor is called during deserialization to reconstitute the exception object transmitted over a stream. For more information, see [XML and SOAP Serialization](~/docs/standard/serialization/xml-and-soap-serialization.md).  
+ This constructor is called during deserialization to reconstitute the exception object transmitted over a stream. For more information, see [XML and SOAP Serialization](/dotnet/standard/serialization/xml-and-soap-serialization).  
 
  ]]></format>
         </remarks>
-        <related type="Article" href="~/docs/standard/serialization/xml-and-soap-serialization.md">XML and SOAP Serialization</related>
+        <related type="Article" href="/dotnet/standard/serialization/xml-and-soap-serialization">XML and SOAP Serialization</related>
       </Docs>
     </Member>
     <Member MemberName=".ctor">
@@ -182,7 +182,7 @@
 
  ]]></format>
         </remarks>
-        <related type="Article" href="~/docs/standard/exceptions/index.md">Handling and Throwing Exceptions</related>
+        <related type="Article" href="/dotnet/standard/exceptions/">Handling and Throwing Exceptions</related>
       </Docs>
     </Member>
     <Member MemberName=".ctor">
@@ -300,7 +300,7 @@
           <format type="text/markdown"><![CDATA[  
 
 ## Remarks  
- This constructor is called during deserialization to reconstitute the exception object transmitted over a stream. For more information, see [XML and SOAP Serialization](~/docs/standard/serialization/xml-and-soap-serialization.md).  
+ This constructor is called during deserialization to reconstitute the exception object transmitted over a stream. For more information, see [XML and SOAP Serialization](/dotnet/standard/serialization/xml-and-soap-serialization).  
 
  ]]></format>
         </remarks>

xml/Microsoft.Build.Debugging/DebuggerManager+IslandThread.xml

@@ -78,7 +78,7 @@
 ## Remarks  
  Call `Dispose` when you are finished using the <xref:Microsoft.Build.Debugging.DebuggerManager.IslandThread>. After calling `Dispose`, you must release all references to the <xref:Microsoft.Build.Debugging.DebuggerManager.IslandThread> so the garbage collector can reclaim the memory that it was using.  
 
- For more information, see [Cleaning Up Unmanaged Resources](~/docs/standard/garbage-collection/unmanaged.md) and [Implementing a Dispose Method](~/docs/standard/garbage-collection/implementing-dispose.md).  
+ For more information, see [Cleaning Up Unmanaged Resources](/dotnet/standard/garbage-collection/unmanaged) and [Implementing a Dispose Method](/dotnet/standard/garbage-collection/implementing-dispose).  
 
 > [!NOTE]
 >  Always call `Dispose` before you release your last reference to the <xref:Microsoft.Build.Debugging.DebuggerManager.IslandThread>. Otherwise, the resources it is using will not be freed until the garbage collector calls the <xref:Microsoft.Build.Debugging.DebuggerManager.IslandThread> object's `Finalize` method.  

xml/Microsoft.Build.Framework/OutputAttribute.xml

@@ -28,7 +28,7 @@
 ## Remarks  
  The [!INCLUDE[vstecmsbuild](~/includes/vstecmsbuild-md.md)] engine will only allow task properties marked with this attribute to output data from a task. Project authors can only use properties marked with this attribute in the `Output` element of a project file. All other task properties are treated as inputs to a task.  
 
- For more information about using attributes, see [Extending Metadata Using Attributes](~/docs/standard/attributes/index.md).  
+ For more information about using attributes, see [Extending Metadata Using Attributes](/dotnet/standard/attributes/).  
 
 
 

xml/Microsoft.Build.Framework/RequiredAttribute.xml

@@ -28,7 +28,7 @@
 ## Remarks  
  If a property marked with this attribute is not assigned a value when the task is invoked, the build will fail.  
 
- For more information about using attributes, see [Extending Metadata Using Attributes](~/docs/standard/attributes/index.md).  
+ For more information about using attributes, see [Extending Metadata Using Attributes](/dotnet/standard/attributes/).  
 
 
 

xml/Microsoft.Build.Framework/RequiredRuntimeAttribute.xml

@@ -30,7 +30,7 @@
 > [!NOTE]
 >  This attribute is currently non-functional because only one version of the CLR (2.0) is capable of running either [!INCLUDE[vstecmsbuild](~/includes/vstecmsbuild-md.md)] version 2.0 or 3.5.  
 
- For more information about using attributes, see [Extending Metadata Using Attributes](~/docs/standard/attributes/index.md).  
+ For more information about using attributes, see [Extending Metadata Using Attributes](/dotnet/standard/attributes/).  
 
  ]]></format>
     </remarks>

xml/Microsoft.Build.Tasks.Deployment.ManifestUtilities/CompatibleFramework.xml

@@ -78,7 +78,7 @@
           <format type="text/markdown"><![CDATA[  
 
 ## Remarks  
- A profile is a subset of the full .NET Framework. For example, the .NET Framework Client Profile is a subset of the [!INCLUDE[net_v35SP1_long](~/includes/net-v35sp1-long-md.md)], and the [!INCLUDE[net_client_v40_long](~/includes/net-client-v40-long-md.md)] is a subset of the [!INCLUDE[net_v45](~/includes/net-v45-md.md)]. For more information, see [.NET Framework Client Profile](~/docs/framework/deployment/client-profile.md).  
+ A profile is a subset of the full .NET Framework. For example, the .NET Framework Client Profile is a subset of the [!INCLUDE[net_v35SP1_long](~/includes/net-v35sp1-long-md.md)], and the [!INCLUDE[net_client_v40_long](~/includes/net-client-v40-long-md.md)] is a subset of the [!INCLUDE[net_v45](~/includes/net-v45-md.md)]. For more information, see [.NET Framework Client Profile](/dotnet/framework/deployment/client-profile).  
 
  ]]></format>
         </remarks>

xml/Microsoft.Build.Tasks.Hosting/ICscHostObject4.xml

@@ -100,7 +100,7 @@
           <format type="text/markdown"><![CDATA[  
 
 ## Remarks  
- If the <xref:Microsoft.Build.Tasks.ManagedCompiler.Prefer32Bit%2A> property is set on the project, <xref:Microsoft.Build.Tasks.Hosting.ICscHostObject4.SetPlatformWith32BitPreference%2A> changes the `/platform` value from `AnyCPU` or the default value (`null` or "") to `AnyCPU32BitPreferred`. For more information, see [/platform (C# Compiler Options)](~/docs/csharp/language-reference/compiler-options/platform-compiler-option.md).  
+ If the <xref:Microsoft.Build.Tasks.ManagedCompiler.Prefer32Bit%2A> property is set on the project, <xref:Microsoft.Build.Tasks.Hosting.ICscHostObject4.SetPlatformWith32BitPreference%2A> changes the `/platform` value from `AnyCPU` or the default value (`null` or "") to `AnyCPU32BitPreferred`. For more information, see [/platform (C# Compiler Options)](/dotnet/csharp/language-reference/compiler-options/platform-compiler-option).  
 
  If the `/platform` value is set to `AnyCPU` (`/platform:AnyCPU`), your application runs as a 64-bit process whenever possible and falls back to 32-bit for 32-bit-only systems. However, you might prefer an application to run as a 32-bit process because 64-bit applications may consume more memory. The `AnyCPU32BitPreferred` setting is similar to `AnyCPU`, except that its default action is to run applications in 32-bit mode on systems that support either mode.  This setting accommodates future processors that may not fall back to 32-bit mode.  
 

xml/Microsoft.Build.Tasks.Hosting/IVbcHostObject5.xml

@@ -170,7 +170,7 @@
           <format type="text/markdown"><![CDATA[  
 
 ## Remarks  
- If the <xref:Microsoft.Build.Tasks.ManagedCompiler.Prefer32Bit%2A> property is set on the project, <xref:Microsoft.Build.Tasks.Hosting.IVbcHostObject5.SetPlatformWith32BitPreference%2A> changes the `/platform` value `AnyCPU` or the default platform value (`null` or "") to `AnyCPU32BitPreferred`. For more information, see [/platform (Visual Basic)](~/docs/visual-basic/reference/command-line-compiler/platform.md). The `AnyCPU` `/platform` switch setting (`/platform:AnyCPU`) runs your application as a 64-bit process whenever possible, falling back to 32-bit for 32-bit-only systems. However, running applications as 32-bit is often preferred to running them as 64-bit because 64-bit applications may consume more memory. The `AnyCPU32BitPreferred` setting is similar to `AnyCPU` except that its default action is to run applications in 32-bit mode on systems that support either 32-bit or 64-bit mode. This setting accommodates future processors that may not have a fallback 32-bit mode.  
+ If the <xref:Microsoft.Build.Tasks.ManagedCompiler.Prefer32Bit%2A> property is set on the project, <xref:Microsoft.Build.Tasks.Hosting.IVbcHostObject5.SetPlatformWith32BitPreference%2A> changes the `/platform` value `AnyCPU` or the default platform value (`null` or "") to `AnyCPU32BitPreferred`. For more information, see [/platform (Visual Basic)](/dotnet/visual-basic/reference/command-line-compiler/platform). The `AnyCPU` `/platform` switch setting (`/platform:AnyCPU`) runs your application as a 64-bit process whenever possible, falling back to 32-bit for 32-bit-only systems. However, running applications as 32-bit is often preferred to running them as 64-bit because 64-bit applications may consume more memory. The `AnyCPU32BitPreferred` setting is similar to `AnyCPU` except that its default action is to run applications in 32-bit mode on systems that support either 32-bit or 64-bit mode. This setting accommodates future processors that may not have a fallback 32-bit mode.  
 
  ]]></format>
         </remarks>