dotnet · gewarren · Nov 19, 2020 · Nov 18, 2020 · Nov 19, 2020 · Nov 19, 2020
diff --git a/.openpublishing.redirection.json b/.openpublishing.redirection.json
@@ -218,6 +218,14 @@
             "source_path": "docs/core/compatibility/framework-core.md",
             "redirect_url": "/dotnet/core/compatibility/fx-core"
         },
+        {
+            "source_path": "docs/core/compatibility/serialization.md",
+            "redirect_url": "/dotnet/core/compatibility/serialization/5.0/binaryformatter-deserialize-rewraps-exceptions"
+        },
+        {
+            "source_path": "docs/core/compatibility/wpf.md",
+            "redirect_url": "/dotnet/core/compatibility/windows-forms/5.0/automatically-infer-winexe-output-type"
+        },
         {
             "source_path": "docs/core/deploying/applications.md",
             "redirect_url": "/dotnet/core/deploying/index"

diff --git a/docs/core/compatibility/3.1-5.0.md b/docs/core/compatibility/3.1-5.0.md
@@ -9,7 +9,6 @@ If you're migrating from version 3.1 of .NET Core or ASP.NET Core to version 5.0
 
 ## ASP.NET Core
 
-- [ASP.NET Core apps allow deserializing quoted numbers](#aspnet-core-apps-allow-deserializing-quoted-numbers)
 - [Authentication: AzureAD.UI and AzureADB2C.UI APIs and packages marked obsolete](#authentication-azureadui-and-azureadb2cui-apis-and-packages-marked-obsolete)
 - [Authorization: Resource in endpoint routing is HttpContext](#authorization-resource-in-endpoint-routing-is-httpcontext)
 - [Azure: Microsoft-prefixed Azure integration packages removed](#azure-microsoft-prefixed-azure-integration-packages-removed)
@@ -42,10 +41,6 @@ If you're migrating from version 3.1 of .NET Core or ASP.NET Core to version 5.0
 - [SignalR: UseSignalR and UseConnections methods removed](#signalr-usesignalr-and-useconnections-methods-removed)
 - [Static files: CSV content type changed to standards-compliant](#static-files-csv-content-type-changed-to-standards-compliant)
 
-[!INCLUDE [ASP.NET Core apps allow deserializing quoted numbers](../../../includes/core-changes/serialization/5.0/jsonserializer-allows-reading-numbers-as-strings.md)]
-
-***
-
 [!INCLUDE[Authentication: AzureAD.UI and AzureADB2C.UI APIs and packages marked obsolete](~/includes/core-changes/aspnetcore/5.0/authentication-aad-packages-obsolete.md)]
 
 ***
@@ -302,97 +297,3 @@ If you're migrating from version 3.1 of .NET Core or ASP.NET Core to version 5.0
 [!INCLUDE [platformabstractions-package-removed](../../../includes/core-changes/corefx/5.0/platformabstractions-package-removed.md)]
 
 ***
-
-## Serialization
-
-- [ASP.NET Core apps allow deserializing quoted numbers](#aspnet-core-apps-allow-deserializing-quoted-numbers)
-- [PropertyNamingPolicy, PropertyNameCaseInsensitive, and Encoder options are honored when serializing and deserializing key-value pairs](#propertynamingpolicy-propertynamecaseinsensitive-and-encoder-options-are-honored-when-serializing-and-deserializing-key-value-pairs)
-- [Non-public, parameterless constructors not used for deserialization](#non-public-parameterless-constructors-not-used-for-deserialization)
-- [JsonSerializer.Serialize throws ArgumentNullException when type parameter is null](#jsonserializerserialize-throws-argumentnullexception-when-type-parameter-is-null)
-- [JsonSerializer.Deserialize requires single-character string](#jsonserializerdeserialize-requires-single-character-string)
-- [BinaryFormatter.Deserialize rewraps some exceptions in SerializationException](#binaryformatterdeserialize-rewraps-some-exceptions-in-serializationexception)
-
-[!INCLUDE [jsonserializer-allows-reading-numbers-as-strings](../../../includes/core-changes/serialization/5.0/jsonserializer-allows-reading-numbers-as-strings.md)]
-
-***
-
-[!INCLUDE [options-honored-when-serializing-key-value-pairs](../../../includes/core-changes/serialization/5.0/options-honored-when-serializing-key-value-pairs.md)]
-
-***
-
-[!INCLUDE [non-public-parameterless-constructors-not-used-for-deserialization](../../../includes/core-changes/serialization/5.0/non-public-parameterless-constructors-not-used-for-deserialization.md)]
-
-***
-
-[!INCLUDE [jsonserializer-serialize-throws-argumentnullexception-for-null-type](../../../includes/core-changes/serialization/5.0/jsonserializer-serialize-throws-argumentnullexception-for-null-type.md)]
-
-***
-
-[!INCLUDE [deserializing-json-into-char-requires-single-character](../../../includes/core-changes/serialization/5.0/deserializing-json-into-char-requires-single-character.md)]
-
-***
-
-[!INCLUDE [binaryformatter-deserialize-rewraps-exceptions](../../../includes/core-changes/serialization/5.0/binaryformatter-deserialize-rewraps-exceptions.md)]
-
-***
-
-## Windows Forms
-
-- [TextFormatFlags.ModifyString is obsolete](#textformatflagsmodifystring-is-obsolete)
-- [DataGridView no longer resets fonts for customized cell styles](#datagridview-no-longer-resets-fonts-for-customized-cell-styles)
-- [OutputType set to WinExe for WPF and WinForms apps](#outputtype-set-to-winexe-for-wpf-and-winforms-apps)
-- [DataGridView-related APIs now throw InvalidOperationException](#datagridview-related-apis-now-throw-invalidoperationexception)
-- [WinForms and WPF apps use Microsoft.NET.Sdk](#winforms-and-wpf-apps-use-microsoftnetsdk)
-- [Removed status bar controls](#removed-status-bar-controls)
-- [WinForms methods now throw ArgumentException](#winforms-methods-now-throw-argumentexception)
-- [WinForms methods now throw ArgumentNullException](#winforms-methods-now-throw-argumentnullexception)
-- [WinForms properties now throw ArgumentOutOfRangeException](#winforms-properties-now-throw-argumentoutofrangeexception)
-
-[!INCLUDE [modifystring-field-of-textformatflags-obsolete](../../../includes/core-changes/windowsforms/5.0/modifystring-field-of-textformatflags-obsolete.md)]
-
-***
-
-[!INCLUDE [datagridview-doesnt-reset-custom-font-settings](../../../includes/core-changes/windowsforms/5.0/datagridview-doesnt-reset-custom-font-settings.md)]
-
-***
-
-[!INCLUDE [automatically-infer-winexe-output-type](../../../includes/core-changes/windowsforms/5.0/automatically-infer-winexe-output-type.md)]
-
-***
-
-[!INCLUDE [null-owner-causes-invalidoperationexception](../../../includes/core-changes/windowsforms/5.0/null-owner-causes-invalidoperationexception.md)]
-
-***
-
-[!INCLUDE [sdk-and-target-framework-change](../../../includes/core-changes/windowsforms/5.0/sdk-and-target-framework-change.md)]
-
-***
-
-[!INCLUDE [winforms-deprecated-controls](../../../includes/core-changes/windowsforms/5.0/winforms-deprecated-controls.md)]
-
-***
-
-[!INCLUDE [invalid-args-cause-argumentexception](../../../includes/core-changes/windowsforms/5.0/invalid-args-cause-argumentexception.md)]
-
-***
-
-[!INCLUDE [null-args-cause-argumentnullexception](../../../includes/core-changes/windowsforms/5.0/null-args-cause-argumentnullexception.md)]
-
-***
-
-[!INCLUDE [invalid-args-cause-argumentoutofrangeexception](../../../includes/core-changes/windowsforms/5.0/invalid-args-cause-argumentoutofrangeexception.md)]
-
-***
-
-## Windows Presentation Framework (WPF)
-
-- [OutputType set to WinExe for WPF and WinForms apps](#outputtype-set-to-winexe-for-wpf-and-winforms-apps)
-- [WinForms and WPF apps use Microsoft.NET.Sdk](#winforms-and-wpf-apps-use-microsoftnetsdk)
-
-[!INCLUDE [automatically-infer-winexe-output-type](../../../includes/core-changes/windowsforms/5.0/automatically-infer-winexe-output-type.md)]
-
-***
-
-[!INCLUDE [sdk-and-target-framework-change](../../../includes/core-changes/windowsforms/5.0/sdk-and-target-framework-change.md)]
-
-***
diff --git a/docs/core/compatibility/serialization.md b/docs/core/compatibility/serialization.md
diff --git a/...rmatter-deserialize-rewraps-exceptions.md → ...rmatter-deserialize-rewraps-exceptions.md b/...rmatter-deserialize-rewraps-exceptions.md → ...rmatter-deserialize-rewraps-exceptions.md
@@ -1,18 +1,23 @@
-### BinaryFormatter.Deserialize rewraps some exceptions in SerializationException
+---
+title: "Breaking change: BinaryFormatter.Deserialize rewraps some exceptions"
+description: Learn about the breaking change in .NET 5.0 where BinaryFormatter.Deserialize rewraps some exception objects inside a SerializationException.
+ms.date: 08/18/2020
+---
+# BinaryFormatter.Deserialize rewraps some exceptions in SerializationException
 
 The <xref:System.Runtime.Serialization.Formatters.Binary.BinaryFormatter.Deserialize%2A?displayProperty=nameWithType> method now rewraps some exception objects inside a <xref:System.Runtime.Serialization.SerializationException> before propagating the exception back to the caller.
 
-#### Change description
+## Change description
 
 Previously, the <xref:System.Runtime.Serialization.Formatters.Binary.BinaryFormatter.Deserialize%2A?displayProperty=nameWithType> method allowed some arbitrary exceptions, such as <xref:System.ArgumentNullException>, to propagate up the stack to its callers.
 
 In .NET 5.0 and later, the <xref:System.Runtime.Serialization.Formatters.Binary.BinaryFormatter.Deserialize%2A?displayProperty=nameWithType> method more aggressively catches exceptions that occur due to invalid deserialization operations and wraps them in a <xref:System.Runtime.Serialization.SerializationException>.
 
-#### Version introduced
+## Version introduced
 
-5.0 Preview 1
+5.0
 
-#### Recommended action
+## Recommended action
 
 In most cases, you don't need to take any action. However, if your call site depends on a particular exception being thrown, you can unwrap the exception from the outer <xref:System.Runtime.Serialization.SerializationException>, as shown in the following example.
 
@@ -34,18 +39,18 @@ catch (SerializationException serEx) when (serEx.InnerException is MyException m
 }
 ```
 
-#### Category
-
-Serialization
-
-#### Affected APIs
+## Affected APIs
 
 - <xref:System.Runtime.Serialization.Formatters.Binary.BinaryFormatter.Deserialize%2A?displayProperty=fullName>
 
 <!--
 
-#### Affected APIs
+### Affected APIs
 
 - `Overload:System.Runtime.Serialization.Formatters.Binary.BinaryFormatter.Deserialize`
 
+### Category
+
+Serialization
+
 -->
diff --git a/...on-into-char-requires-single-character.md → ...on-into-char-requires-single-character.md b/...on-into-char-requires-single-character.md → ...on-into-char-requires-single-character.md
@@ -1,8 +1,13 @@
-### JsonSerializer.Deserialize requires single-character string
+---
+title: "Breaking change: Deserialize requires single-character string"
+description: Learn about the breaking change in .NET 5.0 where JsonSerializer.Deserialize requires a single-character string.
+ms.date: 10/18/2020
+---
+# JsonSerializer.Deserialize requires single-character string
 
 When the type parameter is <xref:System.Char>, the string argument to <xref:System.Text.Json.JsonSerializer.Deserialize%60%601(System.String,System.Text.Json.JsonSerializerOptions)?displayProperty=nameWithType> must contain a single character for deserialization to succeed.
 
-#### Change description
+## Change description
 
 In previous .NET versions, if you pass a multi-character string to <xref:System.Text.Json.JsonSerializer.Deserialize%60%601(System.String,System.Text.Json.JsonSerializerOptions)?displayProperty=nameWithType> and the type parameter is <xref:System.Char>, the deserialization succeeds and only the first character is deserialized.
 
@@ -17,30 +22,30 @@ JsonSerializer.Deserialize<char>("\"abc\"");
 JsonSerializer.Deserialize<char>("\"a\"");
 ```
 
-#### Version introduced
+## Version introduced
 
 5.0
 
-#### Reason for change
+## Reason for change
 
 <xref:System.Text.Json.JsonSerializer.Deserialize%60%601(System.String,System.Text.Json.JsonSerializerOptions)?displayProperty=nameWithType> parses text that represents a single JSON value into an instance of the type specified by the generic type parameter. Parsing should only succeed when the provided payload is valid for the specified generic type parameter. For a <xref:System.Char> value type, a valid payload is a single character string.
 
-#### Recommended action
+## Recommended action
 
 When parsing a string into a <xref:System.Char> type using <xref:System.Text.Json.JsonSerializer.Deserialize%60%601(System.String,System.Text.Json.JsonSerializerOptions)?displayProperty=nameWithType>, make sure the string consists of a single character.
 
-#### Category
-
-Serialization
-
-#### Affected APIs
+## Affected APIs
 
 - <xref:System.Text.Json.JsonSerializer.Deserialize%60%601(System.String,System.Text.Json.JsonSerializerOptions)?displayProperty=fullName>
 
 <!--
 
-#### Affected APIs
+### Affected APIs
 
 - `M:System.Text.Json.JsonSerializer.Deserialize``1(System.String,System.Text.Json.JsonSerializerOptions)`
 
+### Category
+
+Serialization
+
 -->
diff --git a/...izer-allows-reading-numbers-as-strings.md → ...izer-allows-reading-numbers-as-strings.md b/...izer-allows-reading-numbers-as-strings.md → ...izer-allows-reading-numbers-as-strings.md
@@ -1,8 +1,13 @@
-### ASP.NET Core apps allow deserializing quoted numbers
+---
+title: "Breaking change: ASP.NET Core apps allow deserializing quoted numbers"
+description: Learn about the breaking change in .NET 5.0 where ASP.NET Core apps will successfully deserialize numbers that are represented as JSON strings instead of throwing an exception.
+ms.date: 10/21/2020
+---
+# ASP.NET Core apps allow deserializing quoted numbers
 
-Starting in .NET 5.0, ASP.NET Core apps use the default deserialization options as specified by <xref:System.Text.Json.JsonSerializerDefaults.Web?displayProperty=nameWithType>. The <xref:System.Text.Json.JsonSerializerDefaults.Web> set of options includes setting <xref:System.Text.Json.JsonSerializerOptions.NumberHandling> to <xref:System.Text.Json.Serialization.JsonNumberHandling.AllowReadingFromString?displayProperty=nameWithType>. This change means that ASP.NET Core apps will successfully deserialize numbers that are represented as JSON strings, instead of throwing an exception.
+Starting in .NET 5.0, ASP.NET Core apps use the default deserialization options as specified by <xref:System.Text.Json.JsonSerializerDefaults.Web?displayProperty=nameWithType>. The <xref:System.Text.Json.JsonSerializerDefaults.Web> set of options includes setting <xref:System.Text.Json.JsonSerializerOptions.NumberHandling> to <xref:System.Text.Json.Serialization.JsonNumberHandling.AllowReadingFromString?displayProperty=nameWithType>. This change means that ASP.NET Core apps will successfully deserialize numbers that are represented as JSON strings instead of throwing an exception.
 
-#### Change description
+## Change description
 
 In .NET Core 3.0 - 3.1, <xref:System.Text.Json.JsonSerializer> throws a <xref:System.Text.Json.JsonException> during deserialization if it encounters a quoted number in a JSON payload. The quoted numbers are used to map with number properties in object graphs. In .NET Core 3.0 - 3.1, numbers are only read from <xref:System.Text.Json.JsonTokenType.Number?displayProperty=nameWithType> tokens.
 
@@ -14,15 +19,15 @@ Starting in .NET 5.0, quoted numbers in JSON payloads are considered valid, by d
 > - This is technically not a breaking change, since it makes a scenario more permissive instead of more restrictive (that is, it succeeds in coercing a number from a JSON string instead of throwing an exception). However, since this is a significant behavioral change that affects many ASP.NET Core apps, it is documented here.
 > - The <xref:System.Net.Http.Json.HttpClientJsonExtensions.GetFromJsonAsync%2A?displayProperty=nameWithType> and <xref:System.Net.Http.Json.HttpContentJsonExtensions.ReadFromJsonAsync%2A?displayProperty=nameWithType> extension methods also use the <xref:System.Text.Json.JsonSerializerDefaults.Web> set of serialization options.
 
-#### Version introduced
+## Version introduced
 
 5.0
 
-#### Reason for change
+## Reason for change
 
 Multiple users have requested an option for more permissive number handling in <xref:System.Text.Json.JsonSerializer>. This feedback indicates that many JSON producers (for example, services across the web) emit quoted numbers. By allowing quoted numbers to be read (deserialized), .NET apps can successfully parse these payloads, by default, in web contexts. The configuration is exposed via <xref:System.Text.Json.JsonSerializerDefaults.Web?displayProperty=nameWithType> so that you can specify the same options across different application layers, for example, client, server, and shared.
 
-#### Recommended action
+## Recommended action
 
 If this change is disruptive, for example, if you depend on the strict number handling for validation, you can re-enable the previous behavior. Set the <xref:System.Text.Json.JsonSerializerOptions.NumberHandling?displayProperty=nameWithType> option to <xref:System.Text.Json.Serialization.JsonNumberHandling.Strict?displayProperty=nameWithType>.
 
@@ -33,21 +38,21 @@ services.AddControllers()
    .AddJsonOptions(options.NumberHandling = JsonNumberHandling.Strict);
 ```
 
-#### Category
-
-- ASP.NET Core
-- Serialization
-
-#### Affected APIs
+## Affected APIs
 
 - <xref:System.Text.Json.JsonSerializer.Deserialize%2A?displayProperty=fullName>
 - <xref:System.Text.Json.JsonSerializer.DeserializeAsync%2A?displayProperty=fullName>
 
 <!--
 
-#### Affected APIs
+### Affected APIs
 
 - `Overload:System.Text.Json.JsonSerializer.Deserialize`
 - `Overload:System.Text.Json.JsonSerializer.DeserializeAsync`
 
+### Category
+
+- ASP.NET Core
+- Serialization
+
 -->