Merge master into live (#21095)

* Respond to feedback for deserialization constructors (#21051)

* Fixes #20949. (#21052)

* Add f1-keyword for `class` used as generic type constraint (#21037)

* Add f1-keyword for `class` used as generic type constraint

* Add structconstraint

* Update CS0267 message and simplify example (#21047)

* Update CS0267 message and simplify example

* Update ms.date

* Added a link (#21058)

* Fixes #20958. (#21054)

* fix the source path for retired C# 7.x content (#21059)

The "whats-new" folder was missing.

* Removing redundant pipe character (#20931)

* Update single-file.md (#20925)

update ReadyToRun link now that we have the docs for it.

* Remove statement about TLS 1.3 for .NET Core 3.0 (#20922)

I think, TLS 1.3 won't be supported by .NET Core 3.0 since it's out of support and the implementation is coming with .NET 5, as stated in [Transport Layer Security (TLS) best practices with the .NET Framework](#4675 (comment)).

This info should be removed, so we have no misleading information out there... 😉

* SslStream/NegotiateStream breaking change (#20979)

* Add workload and app model to glossary (#21046)

Co-authored-by: Genevieve Warren <[email protected]>

* Breaking change for key-value pair serialization (#21050)

* Update .NET Standard overview for .NET 5 (#20955)

Co-authored-by: Genevieve Warren <[email protected]>

* Update get-started-vscode.md (#21072)

http to https after verifying link

Co-authored-by: Genevieve Warren <[email protected]>
Co-authored-by: Jon Senchyna <[email protected]>
Co-authored-by: Youssef Victor <[email protected]>
Co-authored-by: David Pine <[email protected]>
Co-authored-by: Bill Wagner <[email protected]>
Co-authored-by: William Whitwell Bailey <[email protected]>
Co-authored-by: Lakshan Fernando <[email protected]>
Co-authored-by: kapsiR <[email protected]>
Co-authored-by: Tom Dykstra <[email protected]>
Co-authored-by: icyfire0573 <[email protected]>

Author: 11 people

.openpublishing.redirection.json

@@ -2615,15 +2615,15 @@
             "redirect_url": "/dotnet/csharp/programming-guide/types/index"
         },
         {
-            "source_path": "docs/csharp/csharp-7-1.md",
+            "source_path": "docs/csharp/whats-new/csharp-7-1.md",
             "redirect_url": "/dotnet/csharp/whats-new/csharp-7"
         },
         {
-            "source_path": "docs/csharp/csharp-7-2.md",
+            "source_path": "docs/csharp/whats-new/csharp-7-2.md",
             "redirect_url": "/dotnet/csharp/whats-new/csharp-7"
         },
         {
-            "source_path": "docs/csharp/csharp-7-3.md",
+            "source_path": "docs/csharp/whats-new/csharp-7-3.md",
             "redirect_url": "/dotnet/csharp/whats-new/csharp-7"
         },
         {

docs/core/compatibility/3.1-5.0.md

@@ -205,6 +205,7 @@ If you're migrating from version 3.1 of .NET Core, ASP.NET Core, or EF Core to v
 
 ## Core .NET libraries
 
+- [FrameworkDescription's value is .NET instead of .NET Core](#frameworkdescriptions-value-is-net-instead-of-net-core)
 - [Assembly-related API behavior changes for single-file publishing format](#assembly-related-api-behavior-changes-for-single-file-publishing-format)
 - [Order of tags in Activity.Tags is reversed](#order-of-tags-in-activitytags-is-reversed)
 - [Thread.Abort is obsolete](#threadabort-is-obsolete)
@@ -226,6 +227,10 @@ If you're migrating from version 3.1 of .NET Core, ASP.NET Core, or EF Core to v
 - [CounterSet.CreateCounterSetInstance now throws InvalidOperationException if instance already exist](#countersetcreatecountersetinstance-now-throws-invalidoperationexception-if-instance-already-exists)
 - [Microsoft.DotNet.PlatformAbstractions package removed](#microsoftdotnetplatformabstractions-package-removed)
 
+[!INCLUDE [frameworkdescription-returns-net-not-net-core](../../../includes/core-changes/corefx/5.0/frameworkdescription-returns-net-not-net-core.md)]
+
+***
+
 [!INCLUDE [assembly-api-behavior-changes-for-single-file-publish](../../../includes/core-changes/corefx/5.0/assembly-api-behavior-changes-for-single-file-publish.md)]
 
 ***
@@ -375,10 +380,20 @@ If you're migrating from version 3.1 of .NET Core, ASP.NET Core, or EF Core to v
 
 ## Networking
 
+- [NegotiateStream and SslStream allow successive Begin operations](#negotiatestream-and-sslstream-allow-successive-begin-operations)
+- [Socket.LocalEndPoint is updated after calling SendToAsync](#socketlocalendpoint-is-updated-after-calling-sendtoasync)
 - [WinHttpHandler removed from .NET runtime](#winhttphandler-removed-from-net-runtime)
 - [MulticastOption.Group doesn't accept a null value](#multicastoptiongroup-doesnt-accept-a-null-value)
 - [Cookie Path handling now conforms to RFC 6265](#cookie-path-handling-now-conforms-to-rfc-6265)
 
+[!INCLUDE [negotiatestream-sslstream-dont-fail-on-successive-begin-calls](../../../includes/core-changes/networking/5.0/negotiatestream-sslstream-dont-fail-on-successive-begin-calls.md)]
+
+***
+
+[!INCLUDE [localendpoint-updated-on-sendtoasync](../../../includes/core-changes/networking/5.0/localendpoint-updated-on-sendtoasync.md)]
+
+***
+
 [!INCLUDE [winhttphandler-removed-from-runtime](../../../includes/core-changes/networking/5.0/winhttphandler-removed-from-runtime.md)]
 
 ***
@@ -393,11 +408,16 @@ If you're migrating from version 3.1 of .NET Core, ASP.NET Core, or EF Core to v
 
 ## Serialization
 
+- [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 [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)]
 
 ***

docs/core/compatibility/corefx.md

@@ -11,6 +11,7 @@ The following breaking changes are documented on this page:
 
 | Breaking change | Version introduced |
 | - | :-: |
+| [FrameworkDescription's value is .NET instead of .NET Core](#frameworkdescriptions-value-is-net-instead-of-net-core) | 5.0 |
 | [Assembly-related API behavior changes for single-file publishing format](#assembly-related-api-behavior-changes-for-single-file-publishing-format) | 5.0 |
 | [Order of tags in Activity.Tags is reversed](#order-of-tags-in-activitytags-is-reversed) | 5.0 |
 | [Parameter names changed in RC1](#parameter-names-changed-in-rc1) | 5.0 |
@@ -52,6 +53,10 @@ The following breaking changes are documented on this page:
 
 ## .NET 5.0
 
+[!INCLUDE [frameworkdescription-returns-net-not-net-core](../../../includes/core-changes/corefx/5.0/frameworkdescription-returns-net-not-net-core.md)]
+
+***
+
 [!INCLUDE [assembly-api-behavior-changes-for-single-file-publish](../../../includes/core-changes/corefx/5.0/assembly-api-behavior-changes-for-single-file-publish.md)]
 
 ***

docs/core/compatibility/networking.md

@@ -9,6 +9,8 @@ The following breaking changes are documented on this page:
 
 | Breaking change | Introduced version |
 | - | - |
+| [NegotiateStream and SslStream allow successive Begin operations](#negotiatestream-and-sslstream-allow-successive-begin-operations) | 5.0 |
+| [Socket.LocalEndPoint is updated after calling SendToAsync](#socketlocalendpoint-is-updated-after-calling-sendtoasync) | 5.0 |
 | [WinHttpHandler removed from .NET runtime](#winhttphandler-removed-from-net-runtime) | 5.0 |
 | [MulticastOption.Group doesn't accept a null value](#multicastoptiongroup-doesnt-accept-a-null-value) | 5.0 |
 | [Cookie Path handling now conforms to RFC 6265](#cookie-path-handling-now-conforms-to-rfc-6265) | 5.0 |
@@ -17,6 +19,14 @@ The following breaking changes are documented on this page:
 
 ## .NET 5.0
 
+[!INCLUDE [negotiatestream-sslstream-dont-fail-on-successive-begin-calls](../../../includes/core-changes/networking/5.0/negotiatestream-sslstream-dont-fail-on-successive-begin-calls.md)]
+
+***
+
+[!INCLUDE [localendpoint-updated-on-sendtoasync](../../../includes/core-changes/networking/5.0/localendpoint-updated-on-sendtoasync.md)]
+
+***
+
 [!INCLUDE [winhttphandler-removed-from-runtime](../../../includes/core-changes/networking/5.0/winhttphandler-removed-from-runtime.md)]
 
 ***

docs/core/compatibility/serialization.md

@@ -9,13 +9,18 @@ The following breaking changes are documented on this page:
 
 | Breaking change | Introduced version |
 | - | - |
+| [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) | 5.0 |
 | [Non-public, parameterless constructors not used for deserialization](#non-public-parameterless-constructors-not-used-for-deserialization) | 5.0 |
 | [JsonSerializer.Serialize throws ArgumentNullException when type parameter is null](#jsonserializerserialize-throws-argumentnullexception-when-type-parameter-is-null) | 5.0 |
 | [JsonSerializer.Deserialize requires single-character string](#jsonserializerdeserialize-requires-single-character-string) | 5.0 |
 | [BinaryFormatter.Deserialize rewraps some exceptions in SerializationException](#binaryformatterdeserialize-rewraps-some-exceptions-in-serializationexception) | 5.0 |
 
 ## .NET 5.0
 
+[!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)]
 
 ***

docs/core/deploying/single-file.md

@@ -9,7 +9,7 @@ ms.date: 08/28/2020
 
 Bundling all application-dependent files into a single binary provides an application developer with the attractive option to deploy and distribute the application as a single file. This deployment model has been available since .NET Core 3.0 and has been enhanced in .NET 5.0. Previously in .NET Core 3.0, when a user runs your single-file app, .NET Core host first extracts all files to a temporary directory before running the application. .NET 5.0 improves this experience by directly running the code without the need to extract the files from the app.
 
-Single File deployment is available for both the [framework-dependent deployment model](index.md#publish-framework-dependent) and [self-contained applications](index.md#publish-self-contained). The size of the single file in a self-contained application will be large since it will include the runtime and the framework libraries. The single file deployment option can be combined with [ReadyToRun](../tools/dotnet-publish.md) and [Trim (an experimental feature in .NET 5.0)](trim-self-contained.md) publish options.
+Single File deployment is available for both the [framework-dependent deployment model](index.md#publish-framework-dependent) and [self-contained applications](index.md#publish-self-contained). The size of the single file in a self-contained application will be large since it will include the runtime and the framework libraries. The single file deployment option can be combined with [ReadyToRun](ready-to-run.md) and [Trim (an experimental feature in .NET 5.0)](trim-self-contained.md) publish options.
 
 ## API incompatibility
 

docs/core/dotnet-five.md

@@ -1,7 +1,7 @@
 ---
 title: What's new in .NET 5
 description: Learn about .NET 5, a cross platform and open-source development platform that is the next evolution of .NET Core.
-ms.date: 09/02/2020
+ms.date: 10/13/2020
 ms.topic: overview
 ms.author: dapine
 author: IEvangelist
@@ -33,7 +33,7 @@ The advent of .NET Core has evolved the .NET ecosystem in compelling ways. It ma
   - [System.Text.RegularExpressions](https://devblogs.microsoft.com/dotnet/regex-performance-improvements-in-net-5)
   - [Async ValueTask pooling](https://devblogs.microsoft.com/dotnet/async-valuetask-pooling-in-net-5)
   - [Many more areas](https://devblogs.microsoft.com/dotnet/performance-improvements-in-net-5)
-- Container size optimizations
+- [Container size optimizations](https://github.com/dotnet/dotnet-docker/issues/1814#issuecomment-625294750)
 - [App trimming](https://devblogs.microsoft.com/dotnet/app-trimming-in-net-5)
 - [C# compiler enhancements](https://devblogs.microsoft.com/dotnet/automatically-find-latent-bugs-in-your-code-with-net-5)
 - Tooling support for dump debugging

docs/core/whats-new/dotnet-core-3-0.md

@@ -390,7 +390,7 @@ The GPIO packages include APIs for *GPIO*, *SPI*, *I2C*, and *PWM* devices. The
 When available, .NET Core 3.0 uses **OpenSSL 1.1.1**, **OpenSSL 1.1.0**, or **OpenSSL 1.0.2** on a Linux system. When **OpenSSL 1.1.1** is available, both <xref:System.Net.Security.SslStream?displayProperty=nameWithType> and <xref:System.Net.Http.HttpClient?displayProperty=nameWithType> types will use **TLS 1.3** (assuming both the client and server support **TLS 1.3**).
 
 > [!IMPORTANT]
-> Windows and macOS do not yet support **TLS 1.3**. .NET Core 3.0 will support **TLS 1.3** on these operating systems when support becomes available.
+> Windows and macOS do not yet support **TLS 1.3**.
 
 The following C# 8.0 example demonstrates .NET Core 3.0 on Ubuntu 18.10 connecting to <https://www.cloudflare.com>:
 

docs/csharp/language-reference/keywords/where-generic-type-constraint.md

@@ -6,6 +6,8 @@ ms.date: 04/15/2020
 f1_keywords:
   - "whereconstraint"
   - "whereconstraint_CSharpKeyword"
+  - "classconstraint_CSharpKeyword"
+  - "structconstraint_CSharpKeyword"
 helpviewer_keywords:
   - "where (generic type constraint) [C#]"
 ---

docs/csharp/misc/cs0267.md

@@ -1,7 +1,7 @@
 ---
 description: "Compiler Error CS0267"
 title: "Compiler Error CS0267"
-ms.date: 07/20/2015
+ms.date: 10/12/2020
 f1_keywords: 
   - "CS0267"
 helpviewer_keywords: 
@@ -10,31 +10,20 @@ ms.assetid: 11aaab96-5838-4e36-9551-5b032a1089e1
 ---
 # Compiler Error CS0267
 
-The partial modifier can only appear immediately before 'class', 'struct', or 'interface'  
-  
- The placement of the **partial** modifier was incorrect in the declaration of the class, struct or interface. To fix the error, reorder the modifiers. For more information, see [Partial Classes and Methods](../programming-guide/classes-and-structs/partial-classes-and-methods.md).  
-  
- The following sample generates CS0267:  
-  
-```csharp  
-// CS0267.cs  
-public partial class MyClass  
-{  
-   public MyClass()  
-   {  
-   }  
-}  
-  
-partial public class MyClass  // CS0267  
-// Try this line instead:  
-// public partial class MyClass  
-{  
-   public void Foo()  
-   {  
-   }  
-  
-   public static void Main()  
-   {  
-   }  
-}  
+The partial modifier can only appear immediately before 'class', 'record', 'struct', 'interface', or a method return type.
+
+The placement of the **partial** modifier was incorrect in the declaration of the class, record, struct, interface, or method. To fix the error, reorder the modifiers. For more information, see [Partial Classes and Methods](../programming-guide/classes-and-structs/partial-classes-and-methods.md).
+
+The following sample generates CS0267:
+
+```csharp
+public partial class MyClass
+{
+}
+
+partial public class MyClass  // CS0267
+// Try this line instead:
+// public partial class MyClass
+{
+}
 ```