Update live with current master

docs/architecture/blazor-for-web-forms-developers/index.md

@@ -7,6 +7,8 @@ ms.date: 09/11/2019
 ---
 # Blazor for ASP.NET Web Forms Developers
 
+[!INCLUDE [book-preview](../../../includes/book-preview.md)]
+
 ![Screenshot that shows the Serverless Apps ebook cover.](./media/index/blazor-for-web-forms-developers-cover.png)
 
 > DOWNLOAD available at: <https://aka.ms/blazor-ebook>

docs/architecture/cloud-native/index.md

@@ -7,6 +7,8 @@ ms.date: 03/07/2019
 
 # Architecting Cloud Native .NET Applications for Azure
 
+[!INCLUDE [book-preview](../../../includes/book-preview.md)]
+
 ![cover image](./media/cover.png)
 
 PUBLISHED BY

docs/architecture/grpc-for-wcf-developers/index.md

@@ -7,6 +7,8 @@ ms.date: 09/02/2019
 
 # ASP.NET Core gRPC for WCF Developers
 
+[!INCLUDE [book-preview](../../../includes/book-preview.md)]
+
 ![cover image](./media/cover.png)
 
 PUBLISHED BY

docs/architecture/index.yml

@@ -10,7 +10,7 @@ metadata:
 abstract:
   description: Learn how to build production-ready .NET apps with free application architecture guidance.
 sections:
-- title: Available e-books
+- title: Published e-books
   items:
   - html: '<ul><li><p><a href="containerized-lifecycle/index">Containerized Docker application lifecycle with the Microsoft platform and tools</a></p>'
   - html: '<p>This guide is an introduction to the recommended end to end lifecycle processes you''ll use to develop, validate, and deploy containerized Docker applications using Visual Studio and Microsoft Azure.</p></li></ul>'
@@ -20,10 +20,12 @@ sections:
   - html: '<p>This guide is an introduction to the recommended architecture, design, and deployment processes you''ll use to build ASP.NET and ASP.NET Core applications and host those applications in Azure.</p></li></ul>'
   - html: '<ul><li><p><a href="microservices/index">Architecting container and microservice-based applications</a></p>'
   - html: '<p>This guide is an introduction to developing microservices-based applications and managing them using containers. It discusses architectural design and implementation approaches using .NET Core and Docker containers.</p></li></ul>'
-  - html: '<ul><li><p><a href="cloud-native/index">Architecting cloud-native .NET apps for Azure</a></p>'
-  - html: '<p>This guide defines what cloud native is, introduces a sample app built using cloud-native principles, and covers topics common to most cloud-native applications.</p></li></ul>'
   - html: '<ul><li><p><a href="serverless/index">Serverless apps: Architecture, patterns, and Azure implementation</a></p>'
   - html: '<p>This is a guide for building serverless applications with examples using Azure. It discusses various architecture and design approaches, the benefits and challenges that come with serverless, and provides scenarios and use cases for serverless apps.</p></li></ul>'
+- title: Preview e-books
+  items:
+  - html: '<ul><li><p><a href="cloud-native/index">Architecting cloud-native .NET apps for Azure</a></p>'
+  - html: '<p>This guide defines what cloud native is, introduces a sample app built using cloud-native principles, and covers topics common to most cloud-native applications.</p></li></ul>'
   - html: '<ul><li><p><a href="blazor-for-web-forms-developers/index">Blazor for ASP.NET Web Forms Developers</a></p>'
   - html: '<p>An introduction to Blazor for ASP.NET Web Forms developers. Learn how to build full-stack web apps with .NET using Blazor and .NET Core in a simple and familiar way.</p></li></ul>'
   - html: '<ul><li><p><a href="grpc-for-wcf-developers/index">ASP.NET Core gRPC for WCF Developers</a></p>'

docs/architecture/microservices/implement-resilient-applications/implement-http-call-retries-exponential-backoff-polly.md

@@ -10,7 +10,7 @@ The recommended approach for retries with exponential backoff is to take advanta
 
 Polly is a .NET library that provides resilience and transient-fault handling capabilities. You can implement those capabilities by applying Polly policies such as Retry, Circuit Breaker, Bulkhead Isolation, Timeout, and Fallback. Polly targets .NET 4.x and the .NET Standard Library 1.0 (which supports .NET Core).
 
-However, using Polly’s library with your own custom code with HttpClient can be significantly complex. In the original version of eShopOnContainers, there was a [ResilientHttpClient building-block](https://github.com/dotnet-architecture/eShopOnContainers/commit/0c317d56f3c8937f6823cf1b45f5683397274815#diff-e6532e623eb606a0f8568663403e3a10) based on Polly. But with the release of [HttpClientFactory](use-httpclientfactory-to-implement-resilient-http-requests.md), resilient HTTP communication has become much simpler to implement, so that building-block was deprecated from eShopOnContainers. 
+However, writing your own custom code to use Polly’s library with HttpClient can be significantly complex. In the original version of eShopOnContainers, there was a [ResilientHttpClient building-block](https://github.com/dotnet-architecture/eShopOnContainers/commit/0c317d56f3c8937f6823cf1b45f5683397274815#diff-e6532e623eb606a0f8568663403e3a10) based on Polly. But with the release of [HttpClientFactory](use-httpclientfactory-to-implement-resilient-http-requests.md), implementing resilient HTTP communication with Polly has become much simpler, so that building-block was deprecated from eShopOnContainers. 
 
 The following steps show how you can use Http retries with Polly integrated into HttpClientFactory, which is explained in the previous section.
 

docs/architecture/toc.yml

@@ -5,8 +5,6 @@
   items:
     - name: Architect modern web applications with ASP.NET Core and Microsoft Azure
       href: modern-web-apps-azure/
-    - name: "Architecting cloud-native .NET apps for Azure"
-      href: cloud-native/
     - name: Modernize existing .NET applications with Azure cloud and Windows Containers
       href: modernize-with-azure-containers/
     - name: Containerized Docker application lifecycle with the Microsoft platform and tools
@@ -15,6 +13,11 @@
       href: microservices/
     - name: "Serverless apps: Architecture, patterns, and Azure implementation"
       href: serverless/
+- name: Preview e-books
+  expanded: true
+  items:
+    - name: "Architecting cloud-native .NET apps for Azure"
+      href: cloud-native/
     - name: Blazor for ASP.NET Web Forms Developers
       href: blazor-for-web-forms-developers/
     - name: ASP.NET Core gRPC for WCF Developers

docs/core/compatibility/categories.md

@@ -43,4 +43,4 @@ Maintaining forward compatibility is not a goal of .NET Core.
 
 ## See also
 
-[Evaluate breaking changes in .NET Core](index.md)
+- [Evaluate breaking changes in .NET Core](index.md)

docs/core/migration/index.md

@@ -6,47 +6,44 @@ ms.custom: "seodec18"
 ---
 # Migrating .NET Core projects from project.json
 
-This document will cover migration scenarios for .NET Core projects and will go over the following three migration scenarios:
+This document covers the following three migration scenarios for .NET Core projects:
 
 1. [Migration from a valid latest schema of *project.json* to *csproj*](#migration-from-projectjson-to-csproj)
 2. [Migration from DNX to csproj](#migration-from-dnx-to-csproj)
 3. [Migration from RC3 and previous .NET Core csproj projects to the final format](#migration-from-earlier-net-core-csproj-formats-to-rtm-csproj)
 
-This document is only applicable to older .NET Core projects that still use project.json. It is not applicable for migrating from .NET Framework to .NET Core.
+This document is only applicable to older .NET Core projects that use project.json. It does not apply to migrating from .NET Framework to .NET Core.
 
 ## Migration from project.json to csproj
 
 Migration from *project.json* to *.csproj* can be done using one of the following methods:
 
-- [Visual Studio 2017](#visual-studio-2017)
+- [Visual Studio](#visual-studio)
 - [dotnet migrate command-line tool](#dotnet-migrate)
 
-Both methods use the same underlying engine to migrate the projects, so the results will be the same for both. In most cases, using one of these two ways to migrate the *project.json* to *csproj* is the only thing that is needed and no further manual editing of the project file is necessary. The resulting *.csproj* file will be named the same as the containing directory name.
+Both methods use the same underlying engine to migrate the projects, so the results will be the same for both. In most cases, using one of these two ways to migrate the *project.json* to *csproj* is the only thing that is needed, and no further manual editing of the project file is necessary. The resulting *.csproj* file will be named the same as the containing directory name.
 
-### Visual Studio 2017
+### Visual Studio
 
-When you open a *.xproj* file or a solution file which references *.xproj* files, the **One-way upgrade** dialog appears. The dialog displays the projects to be migrated.
-If you open a solution file, all the projects specified in the solution file will be listed. Review the list of projects to be migrated and select **OK**.
+When you open an *.xproj* file or a solution file that references *.xproj* files in Visual Studio 2017 or Visual Studio 2019 version 16.2 and earlier, the **One-way upgrade** dialog appears. The dialog displays the projects to be migrated. If you open a solution file, all the projects specified in the solution file are listed. Review the list of projects to be migrated and select **OK**.
 
 ![One-way upgrade dialog showing the list of projects to be migrated](media/one-way-upgrade.jpg)
 
-Visual Studio will migrate the projects chosen automatically. When migrating a solution, if you don't choose all projects, the same dialog will appear asking you to upgrade the remaining projects from that solution. After the project is migrated, you can see and modify its contents by right-clicking the project in the **Solution Explorer** window and selecting **Edit \<project name>.csproj**.
+Visual Studio migrates the selected projects automatically. When migrating a solution, if you don't choose all projects, the same dialog appears asking you to upgrade the remaining projects from that solution. After the project is migrated, you can see and modify its contents by right-clicking the project in the **Solution Explorer** window and selecting **Edit \<project name>.csproj**.
 
-Files that were migrated (*project.json*, *global.json*, *.xproj* and solution file) will be moved to a *Backup* folder. The solution file that is migrated will be upgraded to Visual Studio 2017 and you won't be able to open that solution file in previous versions of Visual Studio.
-A file named *UpgradeLog.htm* is also saved and automatically opened that contains a migration report.
+Files that were migrated (*project.json*, *global.json*, *.xproj*, and solution file) are moved to a *Backup* folder. The migrated solution file is upgraded to Visual Studio 2017 or Visual Studio 2019 and you won't be able to open that solution file in Visual Studio 2015 or earlier versions. A file named *UpgradeLog.htm* that contains a migration report is also saved and opened automatically.
 
 > [!IMPORTANT]
-> The new tooling is not available in Visual Studio 2015, so you cannot migrate your projects using that version of Visual Studio.
+> You cannot migrate your projects using Visual Studio 2015.
 
 ### dotnet migrate
 
-In the command-line scenario, you can use the [`dotnet migrate`](../tools/dotnet-migrate.md) command. It will migrate a project, a solution or a set of folders in that order, depending on which ones were found.
-When you migrate a project, the project and all its dependencies are migrated.
+In the command-line scenario, you can use the [`dotnet migrate`](../tools/dotnet-migrate.md) command. It migrates a project, a solution, or a set of folders in that order, depending on which ones were found. When you migrate a project, the project and all its dependencies are migrated.
 
-Files that were migrated (*project.json*, *global.json* and *.xproj*) will be moved to a *backup* folder.
+Files that were migrated (*project.json*, *global.json*, and *.xproj*) are moved to a *backup* folder.
 
 > [!NOTE]
-> If you are using Visual Studio Code, the `dotnet migrate` command will not modify Visual Studio Code-specific files such as `tasks.json`. These files need to be changed manually.
+> If you are using Visual Studio Code, the `dotnet migrate` command does not modify Visual Studio Code-specific files such as `tasks.json`. These files need to be changed manually.
 > This is also true if you are using Project Ryder or any editor or Integrated Development Environment (IDE) other than Visual Studio.
 
 See [A mapping between project.json and csproj properties](../tools/project-json-to-csproj.md) for a comparison of project.json and csproj formats.

docs/core/porting/project-structure.md

@@ -63,4 +63,4 @@ Changes to note are:
 
 ## See also
 
-Please see the [.NET Core porting documentation](index.md) for more guidance on migrating to .NET Core.
+- [.NET Core porting documentation](index.md)

docs/csharp/language-reference/compiler-messages/cs2032.md

@@ -17,7 +17,7 @@ Character 'character' is not allowed on the command-line or in response files
 
 ### To generate this error
 
-1. In the *My Documents* folder, create a text file that is named CS2032.rsp, and then enter the following compiler options in it:
+1. In the *My Documents* folder, create a text file that is named *CS2032.rsp*, and then enter the following compiler options in it:
 
     ```console
     /target:exe /out:cs|2032.exe cs2032.cs

docs/csharp/language-reference/compiler-messages/cs7003.md

@@ -1,9 +1,9 @@
 ---
 title: "Compiler Error CS7003"
 ms.date: 11/05/2017
-f1_keywords: 
+f1_keywords:
   - "CS7003"
-helpviewer_keywords: 
+helpviewer_keywords:
   - "CS7003"
 author: sputier
 ---
@@ -13,7 +13,7 @@ Unexpected use of an unbound generic name
 
 This error occurs if you use a generic type needing one parameter type without passing any generic parameter type name between the angle brackets. This use may be a variable declaration, or an object instantiation.
 
-## To correct this error  
+## To correct this error
 
 Provide one parameter type name in angle brackets when using a generic type.
 
@@ -22,18 +22,18 @@ Provide one parameter type name in angle brackets when using a generic type.
 The following example generates CS7003:
 
 ```csharp
-// CS7003.cs  
-    class Program
+// CS7003.cs
+class Program
+{
+    static void Main(string[] args)
     {
-        static void Main(string[] args)
-        {
-            var myVar1 = new MyGenericClass<>();  //CS7003
+        var myVar1 = new MyGenericClass<>();  //CS7003
 
-            MyGenericClass<> var2;                //CS7003
-        }
+        MyGenericClass<> var2;                //CS7003
     }
+}
 
-    public class MyGenericClass<T> { }
+public class MyGenericClass<T> { }
 ```
 
 ## See also

docs/csharp/language-reference/configure-language-version.md

@@ -18,7 +18,9 @@ The compiler determines a default based on these rules:
 |----------------|-------|---------------------------|
 |.NET Core|3.x|C# 8.0|
 |.NET Core|2.x|C# 7.3|
-|.NET Standard|all|C# 7.3|
+|.NET Standard|2.1|C# 8.0|
+|.NET Standard|2.0|C# 7.3|
+|.NET Standard|1.x|C# 7.3|
 |.NET Framework|all|C# 7.3|
 
 ## Default for previews

docs/csharp/language-reference/keywords/built-in-types-table.md

@@ -11,8 +11,8 @@ ms.assetid: 54f901f2-bf2f-472c-ae8d-73e8ecfc57fe
 ---
 # Built-in types table (C# Reference)
 
-The following table shows the keywords for built-in C# types, which are aliases of predefined types in the <xref:System> namespace.  
-  
+The following table shows the keywords for built-in C# types, which are aliases of predefined types in the <xref:System> namespace:
+
 |C# type|.NET type|  
 |--------------|-------------------------|  
 |[bool](bool.md)|<xref:System.Boolean?displayProperty=nameWithType>|  
@@ -33,9 +33,9 @@ The following table shows the keywords for built-in C# types, which are aliases
 
 ## Remarks
 
-All of the types in the table, except `object` and `string`, are referred to as simple types.  
-  
-The .NET types and their C# type keyword aliases are interchangeable. For example, you can declare an integer variable by using either of the following declarations:  
+All of the types in the table, except `object` and `string`, are referred to as simple types.
+
+The .NET types and their C# type keyword aliases are interchangeable. For example, you can declare an integer variable by using either of the following declarations:
 
 ```csharp
 int x = 123;

docs/csharp/language-reference/keywords/char.md

@@ -2,10 +2,10 @@
 title: "char keyword - C# Reference"
 ms.custom: seodec18
 ms.date: 07/20/2015
-f1_keywords: 
+f1_keywords:
   - "char"
   - "char_CSharpKeyword"
-helpviewer_keywords: 
+helpviewer_keywords:
   - "char data type [C#]"
 ms.assetid: b51cf4fb-124c-4067-af48-afbac122b228
 ---
@@ -21,7 +21,7 @@ The `char` keyword is used to declare an instance of the <xref:System.Char?displ
 
 ## Literals
 
-Constants of the `char` type can be written as character literals, hexadecimal escape sequence, or Unicode representation. You can also cast the integral character codes. In the following example four `char` variables are initialized with the same character `X`:
+Constants of the `char` type can be written as character literals, hexadecimal escape sequence, or Unicode representation. You can also cast the integral character codes. In the following example, the four elements of an array of `char` are initialized with the same character `X`:
 
 [!code-csharp[csrefKeywordsTypes#19](~/samples/snippets/csharp/VS_Snippets_VBCSharp/csrefKeywordsTypes/CS/keywordsTypes.cs#19)]
 

docs/csharp/language-reference/keywords/null.md

@@ -2,10 +2,10 @@
 title: "null keyword - C# Reference"
 ms.custom: seodec18
 ms.date: 07/20/2015
-f1_keywords: 
+f1_keywords:
   - "null"
   - "null_CSharpKeyword"
-helpviewer_keywords: 
+helpviewer_keywords:
   - "null keyword [C#]"
 ms.assetid: fecb1c60-6232-4efe-87f7-9a86ba2e9119
 ---
@@ -23,7 +23,7 @@ The following example demonstrates some behaviors of the null keyword:
 
 ## See also
 
-- [C# reference](../../language-reference/index.md)
+- [C# reference](../index.md)
 - [C# keywords](index.md)
 - [Default values table](default-values-table.md)
 - [Nothing (Visual Basic)](../../../visual-basic/language-reference/nothing.md)

docs/csharp/language-reference/operators/boolean-logical-operators.md

@@ -1,7 +1,7 @@
 ---
 title: "Boolean logical operators - C# reference"
 description: "Learn about C# operators that perform logical negation, conjunction (AND), and inclusive and exclusive disjunction (OR) operations with Boolean operands."
-ms.date: 04/08/2019
+ms.date: 09/27/2019
 author: pkulikov
 f1_keywords: 
   - "!_CSharpKeyword"
@@ -49,6 +49,8 @@ The `!` operator computes logical negation of its operand. That is, it produces
 
 [!code-csharp-interactive[logical negation](~/samples/csharp/language-reference/operators/BooleanLogicalOperators.cs#Negation)]
 
+Starting with C# 8.0, the unary postfix `!` operator is a null-forgiving operator. In an enabled nullable annotation context, you use it to declare that expression `x` of a nullable reference type isn't null: `x!`. For more information, see [Nullable reference types](../../nullable-references.md).
+
 ## <a name="logical-and-operator-"></a> Logical AND operator &amp;
 
 The `&` operator computes the logical AND of its operands. The result of `x & y` is `true` if both `x` and `y` evaluate to `true`. Otherwise, the result is `false`.

docs/csharp/misc/cs0041.md

@@ -1,13 +1,12 @@
 ---
 title: "Compiler Error CS0041"
 ms.date: 07/20/2015
-f1_keywords: 
+f1_keywords:
   - "CS0041"
-helpviewer_keywords: 
+helpviewer_keywords:
   - "CS0041"
 ms.assetid: 80dbfe00-8cdb-4275-9574-8a215c7139d6
 ---
 # Compiler Error CS0041
-The fully qualified name for 'type' is too long for debug information. Compile without '/debug' option.  
-
- This error can occur when using the [/debug](../language-reference/compiler-options/debug-compiler-option.md) compiler option. If you encounter this error, try to delete the PDB files in the bin directory and recompiling. If you are still encountering this error, you may have to repair or reinstall Visual Studio.
+
+Unexpected error writing debug information -- '{error}'