Fixed bugs for .NET 5 specific content (#22609)

Sumit Ghosh · Youssef1313 · web-flow · commit b7682e138628 · 2021-02-05T08:05:03.000-06:00
* Fixed .NET specific branding microservice

* Fixed copyright year version.

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

Co-authored-by: Youssef Victor &lt;31348972+Youssef1313@users.noreply.github.com&gt;

Co-authored-by: Youssef Victor &lt;31348972+Youssef1313@users.noreply.github.com&gt;
diff --git a/docs/architecture/blazor-for-web-forms-developers/index.md b/docs/architecture/blazor-for-web-forms-developers/index.md
@@ -4,7 +4,7 @@ description: Learn how to build full-stack web apps with .NET using Blazor and .
 author: danroth27
 ms.author: daroth
 no-loc: [Blazor, WebAssembly]
-ms.date: 12/01/2020
+ms.date: 02/02/2021
 ---
 # Blazor for ASP.NET Web Forms Developers
 
@@ -26,7 +26,7 @@ One Microsoft Way
 
 Redmond, Washington 98052-6399
 
-Copyright © 2020 by Microsoft Corporation
+Copyright © 2021 by Microsoft Corporation
 
 All rights reserved. No part of the contents of this book may be reproduced or transmitted in any form or by any means without the written permission of the publisher.
 
diff --git a/docs/architecture/microservices/docker-application-development-process/docker-app-development-workflow.md b/docs/architecture/microservices/docker-application-development-process/docker-app-development-workflow.md
@@ -1,7 +1,7 @@
 ---
 title: Development workflow for Docker apps
 description: Understand the details of the workflow for developing Docker-based applications. Begin step by step and get into some details to optimize Dockerfiles and end with the simplified workflow available when using Visual Studio.
-ms.date: 01/13/2021
+ms.date: 02/02/2021
 ---
 # Development workflow for Docker apps
 
@@ -47,7 +47,7 @@ To begin, make sure you have [Docker Community Edition (CE)](https://docs.docker
 
 [Get started with Docker CE for Windows](https://docs.docker.com/docker-for-windows/)
 
-In addition, you need Visual Studio 2019 version 16.4 or later, with the **.NET Core cross-platform development** workload installed, as shown in Figure 5-2.
+In addition, you need Visual Studio 2019 version 16.8, with the **.NET Core cross-platform development** workload installed, as shown in Figure 5-2.
 
 ![Screenshot of the .NET Core cross-platform development selection.](./media/docker-app-development-workflow/dotnet-core-cross-platform-development.png)
 
@@ -126,7 +126,7 @@ You can specify additional configuration settings in the Dockerfile, depending o
 
 ### Using multi-arch image repositories
 
-A single repo can contain platform variants, such as a Linux image and a Windows image. This feature allows vendors like Microsoft (base image creators) to create a single repo to cover multiple platforms (that is Linux and Windows). For example, the [dotnet/core](https://hub.docker.com/_/microsoft-dotnet/) repository available in the Docker Hub registry provides support for Linux and Windows Nano Server by using the same repo name.
+A single repo can contain platform variants, such as a Linux image and a Windows image. This feature allows vendors like Microsoft (base image creators) to create a single repo to cover multiple platforms (that is Linux and Windows). For example, the [.NET](https://hub.docker.com/_/microsoft-dotnet/) repository available in the Docker Hub registry provides support for Linux and Windows Nano Server by using the same repo name.
 
 If you specify a tag, targeting a platform that is explicit like in the following cases:
 
@@ -500,7 +500,7 @@ The docker-compose up and docker run commands (or running and debugging the cont
 
 ## Step 6. Test your Docker application using your local Docker host
 
-This step will vary depending on what your application is doing. In a simple .NET Core Web application that is deployed as a single container or service, you can access the service by opening a browser on the Docker host and navigating to that site, as shown in Figure 5-13. (If the configuration in the Dockerfile maps the container to a port on the host that is anything other than 80, include the host port in the URL.)
+This step will vary depending on what your application is doing. In a simple .NET Web application that is deployed as a single container or service, you can access the service by opening a browser on the Docker host and navigating to that site, as shown in Figure 5-13. (If the configuration in the Dockerfile maps the container to a port on the host that is anything other than 80, include the host port in the URL.)
 
 ![Screenshot of the response from localhost/API/values.](./media/docker-app-development-workflow/test-docker-app-locally-localhost.png)
 
diff --git a/docs/architecture/microservices/docker-application-development-process/index.md b/docs/architecture/microservices/docker-application-development-process/index.md
@@ -1,7 +1,7 @@
 ---
 title: Development process for Docker-based applications
 description: Get a high-level overview of the options for developing Docker-based applications. Using your choice of Visual Studio for Windows, Visual Studio for Mac, or Visual Studio Code for multiplatform support (Windows, macOS, and Linux).
-ms.date: 01/13/2021
+ms.date: 02/02/2021
 ---
 # Development process for Docker-based applications
 
@@ -13,7 +13,7 @@ ms.date: 01/13/2021
 
 Whether you prefer a full and powerful IDE or a lightweight and agile editor, Microsoft has tools that you can use for developing Docker applications.
 
-**Visual Studio (for Windows).** Docker-based .NET 5 application development with Visual Studio requires Visual Studio 2019 version 16.4 or later. Visual Studio 2019 comes with tools for Docker already built in. The tools for Docker let you develop, run, and validate your applications directly in the target Docker environment. You can press F5 to run and debug your application (single container or multiple containers) directly into a Docker host, or press CTRL+F5 to edit and refresh your application without having to rebuild the container. This IDE is the most powerful development choice for Docker-based apps.
+**Visual Studio (for Windows).** Docker-based .NET 5 application development with Visual Studio requires Visual Studio 2019 version 16.8 or later. Visual Studio 2019 comes with tools for Docker already built in. The tools for Docker let you develop, run, and validate your applications directly in the target Docker environment. You can press F5 to run and debug your application (single container or multiple containers) directly into a Docker host, or press CTRL+F5 to edit and refresh your application without having to rebuild the container. This IDE is the most powerful development choice for Docker-based apps.
 
 **Visual Studio for Mac.** It's an IDE, evolution of Xamarin Studio, running in macOS. For .NET 5 development, it requires version 8.4 or later. This tool should be the preferred choice for developers working in macOS machines who also want to use a powerful IDE.
 
diff --git a/docs/architecture/microservices/docker-application-development-process/media/docker-app-development-workflow/dotnet-core-cross-platform-development-old.png b/docs/architecture/microservices/docker-application-development-process/media/docker-app-development-workflow/dotnet-core-cross-platform-development-old.png
diff --git a/docs/architecture/microservices/docker-application-development-process/media/docker-app-development-workflow/dotnet-core-cross-platform-development.png b/docs/architecture/microservices/docker-application-development-process/media/docker-app-development-workflow/dotnet-core-cross-platform-development.png
diff --git a/docs/architecture/microservices/index.md b/docs/architecture/microservices/index.md
@@ -1,11 +1,11 @@
 ---
 title: .NET Microservices. Architecture for Containerized .NET Applications
 description: .NET Microservices Architecture for Containerized .NET Applications | Microservices are modular and independently deployable services. Docker containers (for Linux and Windows) simplify deployment and testing by bundling a service and its dependencies into a single unit, which is then run in an isolated environment.
-ms.date: 01/13/2021
+ms.date: 02/02/2021
 ---
 # .NET Microservices: Architecture for Containerized .NET Applications
 
-![Book cover](./media/cover-small.png)
+![Book cover](./media/cover-large.png)
 
 **EDITION v5.0** - Updated to ASP.NET Core 5.0
 
@@ -62,9 +62,9 @@ You will also find this guide useful if you are a technical decision maker, such
 
 ### How to use this guide
 
-The first part of this guide introduces Docker containers, discusses how to choose between .NET Core and the .NET Framework as a development framework, and provides an overview of microservices. This content is for architects and technical decision makers who want an overview but don't need to focus on code implementation details.
+The first part of this guide introduces Docker containers, discusses how to choose between .NET 5 and the .NET Framework as a development framework, and provides an overview of microservices. This content is for architects and technical decision makers who want an overview but don't need to focus on code implementation details.
 
-The second part of the guide starts with the [Development process for Docker based applications](./docker-application-development-process/index.md) section. It focuses on the development and microservice patterns for implementing applications using .NET Core and Docker. This section will be of most interest to developers and architects who want to focus on code and on patterns and implementation details.
+The second part of the guide starts with the [Development process for Docker based applications](./docker-application-development-process/index.md) section. It focuses on the development and microservice patterns for implementing applications using .NET and Docker. This section will be of most interest to developers and architects who want to focus on code and on patterns and implementation details.
 
 ## Related microservice and container-based reference application: eShopOnContainers
 
@@ -156,7 +156,7 @@ One Microsoft Way
 
 Redmond, Washington 98052-6399
 
-Copyright © 2020 by Microsoft Corporation
+Copyright © 2021 by Microsoft Corporation
 
 All rights reserved. No part of the contents of this book may be reproduced or transmitted in any form or by any means without the written permission of the publisher.
 
diff --git a/docs/architecture/microservices/media/cover-large.png b/docs/architecture/microservices/media/cover-large.png
diff --git a/docs/architecture/microservices/microservice-ddd-cqrs-patterns/net-core-microservice-domain-model.md b/docs/architecture/microservices/microservice-ddd-cqrs-patterns/net-core-microservice-domain-model.md
@@ -1,10 +1,10 @@
 ---
 title: Implementing a microservice domain model with .NET
 description: .NET Microservices Architecture for Containerized .NET Applications | Get into the implementation details of a DDD-oriented domain model.
-ms.date: 01/13/2021
+ms.date: 02/02/2021
 ---
 
-# Implement a microservice domain model with .NET Core
+# Implement a microservice domain model with .NET
 
 In the previous section, the fundamental design principles and patterns for designing a domain model were explained. Now it is time to explore possible ways to implement the domain model by using .NET (plain C\# code) and EF Core. Your domain model will be composed simply of your code. It will have just the EF Core model requirements, but not real dependencies on EF. You should not have hard dependencies or references to EF Core or any other ORM in your domain model.
 
diff --git a/docs/architecture/microservices/multi-container-microservice-net-applications/media/microservice-application-design/eshoponcontainers-reference-application-architecture.png b/docs/architecture/microservices/multi-container-microservice-net-applications/media/microservice-application-design/eshoponcontainers-reference-application-architecture.png
diff --git a/docs/architecture/microservices/net-core-net-framework-containers/index.md b/docs/architecture/microservices/net-core-net-framework-containers/index.md
@@ -1,9 +1,9 @@
 ---
 title: Choosing Between .NET 5 and .NET Framework for Docker Containers
 description: .NET Microservices Architecture for Containerized .NET Applications | Choosing Between .NET 5 and .NET Framework for Docker Containers
-ms.date: 01/13/2021
+ms.date: 02/02/2021
 ---
-# Choosing Between .NET and .NET Framework for Docker Containers
+# Choosing Between .NET 5 and .NET Framework for Docker Containers
 
 There are two supported frameworks for building server-side containerized Docker applications with .NET: [.NET Framework and .NET 5](https://dotnet.microsoft.com/download). They share many .NET platform components, and you can share code across the two. However, there are fundamental differences between them, and which framework you use will depend on what you want to accomplish. This section provides guidance on when to choose each framework.
 
diff --git a/docs/architecture/microservices/net-core-net-framework-containers/net-core-container-scenarios.md b/docs/architecture/microservices/net-core-net-framework-containers/net-core-container-scenarios.md
@@ -1,7 +1,7 @@
 ---
 title: When to choose .NET 5 for Docker containers
 description: .NET Microservices Architecture for Containerized .NET Applications | When to choose .NET for Docker containers
-ms.date: 01/13/2021
+ms.date: 02/02/2021
 ---
 # When to choose .NET for Docker containers
 
@@ -27,7 +27,7 @@ In addition to the IDEs and editors, you can use the [.NET CLI](../../../core/to
 
 ## Using containers for new ("green-field") projects
 
-Containers are commonly used in conjunction with a microservices architecture, although they can also be used to containerize web apps or services that follow any architectural pattern. You can use .NET Framework on Windows Containers, but the modularity and lightweight nature of .NET 5 makes it perfect for containers and microservices architectures. When you create and deploy a container, its image is far smaller with .NET Core than with .NET Framework.
+Containers are commonly used in conjunction with a microservices architecture, although they can also be used to containerize web apps or services that follow any architectural pattern. You can use .NET Framework on Windows Containers, but the modularity and lightweight nature of .NET 5 makes it perfect for containers and microservices architectures. When you create and deploy a container, its image is far smaller with .NET 5 than with .NET Framework.
 
 ## Create and deploy microservices on containers
 
diff --git a/docs/architecture/microservices/toc.yml b/docs/architecture/microservices/toc.yml
@@ -10,7 +10,7 @@
       href: container-docker-introduction/docker-terminology.md
     - name: Docker containers, images, and registries
       href: container-docker-introduction/docker-containers-images-registries.md
-  - name: Choosing Between NET 5 and NET Framework for Docker Containers
+  - name: Choosing Between .NET 5 and .NET Framework for Docker Containers
     href: net-core-net-framework-containers/index.md
     items:
     - name: General guidance
@@ -65,7 +65,7 @@
     items:
     - name: Development workflow for Docker apps
       href: docker-application-development-process/docker-app-development-workflow.md
-  - name: Designing and Developing Multi Container and Microservice Based NET Applications
+  - name: Designing and Developing Multi Container and Microservice Based .NET Applications
     href: multi-container-microservice-net-applications/index.md
     items:
     - name: Designing a microservice-oriented application
@@ -144,7 +144,7 @@
       href: implement-resilient-applications/implement-circuit-breaker-pattern.md
     - name: Health monitoring
       href: implement-resilient-applications/monitor-app-health.md
-  - name: Securing NET Microservices and Web Applications
+  - name: Securing .NET Microservices and Web Applications
     href: secure-net-microservices-web-applications/index.md
     items:
     - name: About authorization in .NET microservices and web applications
diff --git a/docs/architecture/modern-web-apps-azure/index.md b/docs/architecture/modern-web-apps-azure/index.md
@@ -3,7 +3,7 @@ title: Architect modern web applications with ASP.NET Core and Azure
 description: A guide that provides end-to-end guidance on building monolithic web applications using ASP.NET Core and Azure.
 author: ardalis
 ms.author: wiwagn
-ms.date: 12/07/2020
+ms.date: 02/02/2021
 ---
 
 # Architect Modern Web Applications with ASP.NET Core and Azure
@@ -24,7 +24,7 @@ One Microsoft Way
 
 Redmond, Washington 98052-6399
 
-Copyright © 2020 by Microsoft Corporation
+Copyright © 2021 by Microsoft Corporation
 
 All rights reserved. No part of the contents of this book may be reproduced or transmitted in any form or by any means without the written permission of the publisher.
 
