Replace .NET Core with .NET in migration documentation

Co-authored-by: danroth27 <1874516+danroth27@users.noreply.github.com>

Author: Copilot

aspnetcore/migration/1x-to-2x/index.md

@@ -25,7 +25,7 @@ See [Get Started with ASP.NET Core](xref:getting-started).
 
 ## Update Target Framework Moniker (TFM)
 
-Projects targeting .NET Core should use the [TFM](/dotnet/standard/frameworks) of a version greater than or equal to .NET Core 2.0. Search for the `<TargetFramework>` node in the `.csproj` file, and replace its inner text with `netcoreapp2.0`:
+Projects targeting .NET should use the [TFM](/dotnet/standard/frameworks) of a version greater than or equal to .NET 2.0. Search for the `<TargetFramework>` node in the `.csproj` file, and replace its inner text with `netcoreapp2.0`:
 
 [!code-xml[](../1x-to-2x/samples/AspNetCoreDotNetCore2App/AspNetCoreDotNetCore2App/AspNetCoreDotNetCore2App.csproj?range=3)]
 
@@ -34,15 +34,15 @@ Projects targeting .NET Framework should use the TFM of a version greater than o
 [!code-xml[](../1x-to-2x/samples/AspNetCoreDotNetFx2.0App/AspNetCoreDotNetFx2.0App/AspNetCoreDotNetFx2.0App.csproj?range=4)]
 
 > [!NOTE]
-> .NET Core 2.0 offers a much larger surface area than .NET Core 1.x. If you're targeting .NET Framework solely because of missing APIs in .NET Core 1.x, targeting .NET Core 2.0 is likely to work.
+> .NET 2.0 offers a much larger surface area than .NET 1.x. If you're targeting .NET Framework solely because of missing APIs in .NET 1.x, targeting .NET 2.0 is likely to work.
 
 If the project file contains `<RuntimeFrameworkVersion>1.{sub-version}</RuntimeFrameworkVersion>`, see [this GitHub issue](https://github.com/dotnet/AspNetCore/issues/3221#issuecomment-413094268).
 
 <a name="global-json"></a>
 
-## Update .NET Core SDK version in global.json
+## Update .NET SDK version in global.json
 
-If your solution relies upon a [global.json](/dotnet/core/tools/global-json) file to target a specific .NET Core SDK version, update its `version` property to use the 2.0 version installed on your machine:
+If your solution relies upon a [global.json](/dotnet/core/tools/global-json) file to target a specific .NET SDK version, update its `version` property to use the 2.0 version installed on your machine:
 
 [!code-json[](../1x-to-2x/samples/AspNetCoreDotNetCore2App/global.json?highlight=3)]
 
@@ -52,7 +52,7 @@ If your solution relies upon a [global.json](/dotnet/core/tools/global-json) fil
 
 The `.csproj` file in a 1.x project lists each NuGet package used by the project.
 
-In an ASP.NET Core 2.0 project targeting .NET Core 2.0, a single [metapackage](xref:fundamentals/metapackage) reference in the `.csproj` file replaces the collection of packages:
+In an ASP.NET Core 2.0 project targeting .NET 2.0, a single [metapackage](xref:fundamentals/metapackage) reference in the `.csproj` file replaces the collection of packages:
 
 [!code-xml[](../1x-to-2x/samples/AspNetCoreDotNetCore2App/AspNetCoreDotNetCore2App/AspNetCoreDotNetCore2App.csproj?range=8-10)]
 
@@ -72,7 +72,7 @@ The package `Microsoft.Extensions.CommandLineUtils` has been [retired](https://g
 
 In the `.csproj` file, update the `Version` attribute of each `<DotNetCliToolReference />` node to 2.0.0.
 
-For example, here's the list of CLI tools used in a typical ASP.NET Core 2.0 project targeting .NET Core 2.0:
+For example, here's the list of CLI tools used in a typical ASP.NET Core 2.0 project targeting .NET 2.0:
 
 [!code-xml[](../1x-to-2x/samples/AspNetCoreDotNetCore2App/AspNetCoreDotNetCore2App/AspNetCoreDotNetCore2App.csproj?range=12-16)]
 
@@ -170,11 +170,11 @@ Effortless setup of application performance instrumentation is important. You ca
 
 ASP.NET Core 1.1 projects created in Visual Studio 2017 added Application Insights by default. If you're not using the Application Insights SDK directly, outside of `Program.cs` and `Startup.cs`, follow these steps:
 
-1. If targeting .NET Core, remove the following `<PackageReference />` node from the `.csproj` file:
+1. If targeting .NET, remove the following `<PackageReference />` node from the `.csproj` file:
 
     [!code-xml[](../1x-to-2x/samples/AspNetCoreDotNetCore1App/AspNetCoreDotNetCore1App/AspNetCoreDotNetCore1App.csproj?range=10)]
 
-2. If targeting .NET Core, remove the `UseApplicationInsights` extension method invocation from `Program.cs`:
+2. If targeting .NET, remove the `UseApplicationInsights` extension method invocation from `Program.cs`:
 
     [!code-csharp[](../1x-to-2x/samples/AspNetCoreDotNetCore1App/AspNetCoreDotNetCore1App/Program.cs?name=snippet_ProgramCsMain&highlight=8)]
 

aspnetcore/migration/20_21.md

@@ -31,7 +31,7 @@ This article provides an overview on migration to ASP.NET Core 2.1. It doesn't c
 
 Update the project file:
 
-* Change the target framework to .NET Core 2.1 by updating the project file to `<TargetFramework>netcoreapp2.1</TargetFramework>`.
+* Change the target framework to .NET 2.1 by updating the project file to `<TargetFramework>netcoreapp2.1</TargetFramework>`.
 * Replace the package reference for `Microsoft.AspNetCore.All` with a package reference for `Microsoft.AspNetCore.App`. You may need to add dependencies that were removed from `Microsoft.AspNetCore.All`. For more information, see <xref:fundamentals/metapackage#migrate> and <xref:fundamentals/metapackage-app>.
 * Remove the "Version" attribute on the package reference to `Microsoft.AspNetCore.App`. Projects that use `<Project Sdk="Microsoft.NET.Sdk.Web">` don't need to set the version. The version is implied by the target framework and selected to best match the way ASP.NET Core 2.1 works. For more information, see the [Rules for projects targeting the shared framework](#rules-for-projects-targeting-the-shared-framework) section.
 * For apps that target the .NET Framework, update each package reference to 2.1.
@@ -64,7 +64,7 @@ The version specified by the package reference is the *minimum required* version
 
 Known issues for projects targeting a shared framework:
 
-* The .NET Core 2.1.300 SDK (first included in Visual Studio 15.6) set the implicit version of  `Microsoft.AspNetCore.App` to 2.1.0 which caused conflicts with Entity Framework Core 2.1.1. The recommended solution is to upgrade the .NET Core SDK to 2.1.301 or later. For more information, see [Packages that share dependencies with Microsoft.AspNetCore.App cannot reference patch versions](https://github.com/aspnet/Universe/issues/1180).
+* The .NET 2.1.300 SDK (first included in Visual Studio 15.6) set the implicit version of  `Microsoft.AspNetCore.App` to 2.1.0 which caused conflicts with Entity Framework Core 2.1.1. The recommended solution is to upgrade the .NET SDK to 2.1.301 or later. For more information, see [Packages that share dependencies with Microsoft.AspNetCore.App cannot reference patch versions](https://github.com/aspnet/Universe/issues/1180).
 * All projects that must use `Microsoft.AspNetCore.All` or `Microsoft.AspNetCore.App` should add a package reference for the package in the project file, even if they contain a project reference to another project using `Microsoft.AspNetCore.All` or `Microsoft.AspNetCore.App`.
 
   Example:

aspnetcore/migration/21-to-22.md

@@ -31,7 +31,7 @@ This article explains how to update an existing ASP.NET Core 2.1 project to ASP.
 
 ## Update Target Framework Moniker (TFM)
 
-Projects targeting .NET Core should use the [TFM](/dotnet/standard/frameworks) of a version greater than or equal to .NET Core 2.2. In the project file, update the `<TargetFramework>` node's inner text with `netcoreapp2.2`:
+Projects targeting .NET should use the [TFM](/dotnet/standard/frameworks) of a version greater than or equal to .NET 2.2. In the project file, update the `<TargetFramework>` node's inner text with `netcoreapp2.2`:
 
 ```xml
 <TargetFramework>netcoreapp2.2</TargetFramework>
@@ -66,7 +66,7 @@ For more information and example *web.config* files, see <xref:host-and-deploy/a
 
 ## Update package references
 
-If targeting .NET Core, remove the metapackage reference's `Version` attribute in the project file. Inclusion of a `Version` attribute results in the following warning:
+If targeting .NET, remove the metapackage reference's `Version` attribute in the project file. Inclusion of a `Version` attribute results in the following warning:
 
 ```console
 A PackageReference to 'Microsoft.AspNetCore.App' specified a Version of `2.2.0`. Specifying the version of this package is not recommended. For more information, see https://aka.ms/sdkimplicitrefs
@@ -100,9 +100,9 @@ If referencing the [Microsoft.AspNetCore.Razor.Design](https://www.nuget.org/pac
 Detected package downgrade: Microsoft.AspNetCore.Razor.Design from 2.2.0 to 2.1.2. Reference the package directly from the project to select a different version.
 ```
 
-## Update .NET Core SDK version in global.json
+## Update .NET SDK version in global.json
 
-If your solution relies upon a [global.json](/dotnet/core/tools/global-json) file to target a specific .NET Core SDK version, update its `version` property to the 2.2 version installed on your machine:
+If your solution relies upon a [global.json](/dotnet/core/tools/global-json) file to target a specific .NET SDK version, update its `version` property to the 2.2 version installed on your machine:
 
 ```json
 {

aspnetcore/migration/22-to-30.md

@@ -32,9 +32,9 @@ This article explains how to update an existing ASP.NET Core 2.2 project to ASP.
 
 ---
 
-## Update .NET Core SDK version in global.json
+## Update .NET SDK version in global.json
 
-If your solution relies upon a [global.json](/dotnet/core/tools/global-json) file to target a specific .NET Core SDK version, update its `version` property to the 3.0 version installed on your machine:
+If your solution relies upon a [global.json](/dotnet/core/tools/global-json) file to target a specific .NET SDK version, update its `version` property to the 3.0 version installed on your machine:
 
 ```json
 {
@@ -48,7 +48,7 @@ If your solution relies upon a [global.json](/dotnet/core/tools/global-json) fil
 
 ### Update the Target Framework
 
-ASP.NET Core 3.0 or later only run on .NET Core. Set the [Target Framework Moniker (TFM)](/dotnet/standard/frameworks) to `netcoreapp3.0`:
+ASP.NET Core 3.0 or later only run on .NET. Set the [Target Framework Moniker (TFM)](/dotnet/standard/frameworks) to `netcoreapp3.0`:
 
 [!code-xml[](22-to-30/samples/Web1.csproj?highlight=4)]
 
@@ -293,7 +293,7 @@ In the preceding image, added code is shown in green. For information on the fol
 
 Projects that target `Microsoft.NET.Sdk.Web` implicitly reference analyzers previously shipped as part of the [Microsoft.AspNetCore.Mvc.Analyzers](https://www.nuget.org/packages/Microsoft.AspNetCore.Mvc.Analyzers/) package. No additional references are required to enable these.
 
-If your app uses [API analyzers](xref:web-api/advanced/analyzers) previously shipped using the [Microsoft.AspNetCore.Mvc.Api.Analyzers](https://www.nuget.org/packages/Microsoft.AspNetCore.Mvc.Api.Analyzers/) package, edit your project file to reference the analyzers shipped as part of the .NET Core Web SDK:
+If your app uses [API analyzers](xref:web-api/advanced/analyzers) previously shipped using the [Microsoft.AspNetCore.Mvc.Api.Analyzers](https://www.nuget.org/packages/Microsoft.AspNetCore.Mvc.Api.Analyzers/) package, edit your project file to reference the analyzers shipped as part of the .NET Web SDK:
 
 ```xml
 <Project Sdk="Microsoft.NET.Sdk.Web">
@@ -455,7 +455,7 @@ Apps and libraries targeting ASP.NET Core 2.1 or later should remove any direct
 
 As part of the work to [improve the ASP.NET Core shared framework](https://blogs.msdn.microsoft.com/webdev/2018/10/29/a-first-look-at-changes-coming-in-asp-net-core-3-0/), [Newtonsoft.Json (Json.NET)](https://www.newtonsoft.com/json/help/html/Introduction.htm) has been removed from the ASP.NET Core shared framework.
 
-The default JSON serializer for ASP.NET Core is now <xref:System.Text.Json>, which is new in .NET Core 3.0. Consider using `System.Text.Json` when possible. It's high-performance and doesn't require an additional library dependency. However, since `System.Text.Json` is new, it might currently be missing features that your app needs. For more information, see [How to migrate from Newtonsoft.Json to System.Text.Json](/dotnet/standard/serialization/system-text-json-migrate-from-newtonsoft-how-to).
+The default JSON serializer for ASP.NET Core is now <xref:System.Text.Json>, which is new in .NET 3.0. Consider using `System.Text.Json` when possible. It's high-performance and doesn't require an additional library dependency. However, since `System.Text.Json` is new, it might currently be missing features that your app needs. For more information, see [How to migrate from Newtonsoft.Json to System.Text.Json](/dotnet/standard/serialization/system-text-json-migrate-from-newtonsoft-how-to).
 
 ### Use Newtonsoft.Json in an ASP.NET Core 3.0 SignalR project
 
@@ -880,7 +880,7 @@ In ASP.NET Core 2.2, you could set the `TransportMaxBufferSize` and that would e
 
 #### SignalR assemblies in shared framework
 
-ASP.NET Core SignalR server-side assemblies are now installed with the .NET Core SDK. For more information, see [Remove obsolete package references](#remove-obsolete-package-references) in this document.
+ASP.NET Core SignalR server-side assemblies are now installed with the .NET SDK. For more information, see [Remove obsolete package references](#remove-obsolete-package-references) in this document.
 
 ### MVC controllers
 
@@ -1197,7 +1197,7 @@ For more information on using ASP.NET Core APIs in a class library, see <xref:fu
 
 ## Miscellaneous changes
 
-The validation system in .NET Core 3.0 or later treats non-nullable parameters or bound properties as if they had a `[Required]` attribute. For more information, see [[Required] attribute](xref:mvc/models/validation?view=aspnetcore-3.1#required-attribute).
+The validation system in .NET 3.0 or later treats non-nullable parameters or bound properties as if they had a `[Required]` attribute. For more information, see [[Required] attribute](xref:mvc/models/validation?view=aspnetcore-3.1#required-attribute).
 
 ### Publish
 
@@ -1234,15 +1234,15 @@ Review breaking changes:
 
 * [Complete list of breaking changes in the ASP.NET Core 3.0 release](https://github.com/aspnet/Announcements/issues?page=1&q=is%3Aissue+is%3Aopen+label%3A%22Breaking+change%22+label%3A3.0.0)
 * [Breaking API changes in Antiforgery, CORS, Diagnostics, MVC, and Routing](https://github.com/aspnet/Announcements/issues/387). This list includes breaking changes for compatibility switches.
-* For a summary of 2.2-to-3.0 breaking changes across .NET Core, ASP.NET Core, and Entity Framework Core, see [Breaking changes for migration from version 2.2 to 3.0](/dotnet/core/compatibility/2.2-3.0).
+* For a summary of 2.2-to-3.0 breaking changes across .NET, ASP.NET Core, and Entity Framework Core, see [Breaking changes for migration from version 2.2 to 3.0](/dotnet/core/compatibility/2.2-3.0).
 
 ## Endpoint routing with catch-all parameter
 
 [!INCLUDE[](~/includes/catchall.md)]
 
-## .NET Core 3.0 on Azure App Service
+## .NET 3.0 on Azure App Service
 
-The rollout of .NET Core to Azure App Service is finished. .NET Core 3.0 is available in all Azure App Service datacenters.
+The rollout of .NET to Azure App Service is finished. .NET 3.0 is available in all Azure App Service datacenters.
 
 ## ASP.NET Core Module (ANCM)
 

aspnetcore/migration/30-to-31.md

@@ -29,9 +29,9 @@ This article explains how to update an existing ASP.NET Core 3.0 project to ASP.
 
 ---
 
-## Update .NET Core SDK version in global.json
+## Update .NET SDK version in global.json
 
-If you rely upon a [global.json](/dotnet/core/tools/global-json) file to target a specific .NET Core SDK version, update the `version` property to the 3.1 SDK version that's installed. For example:
+If you rely upon a [global.json](/dotnet/core/tools/global-json) file to target a specific .NET SDK version, update the `version` property to the 3.1 SDK version that's installed. For example:
 
 ```diff
 {
@@ -97,7 +97,7 @@ In the `.pubxml` file update the `TargetFramework` to 3.1:
 
 ## Review breaking changes
 
-Review 3.0-to-3.1 breaking changes across .NET Core, ASP.NET Core, and Entity Framework Core at [Breaking changes for migration from version 3.0 to 3.1](/dotnet/core/compatibility/3.0-3.1).
+Review 3.0-to-3.1 breaking changes across .NET, ASP.NET Core, and Entity Framework Core at [Breaking changes for migration from version 3.0 to 3.1](/dotnet/core/compatibility/3.0-3.1).
 
 ## Optional changes
 

aspnetcore/migration/31-to-50.md

@@ -28,9 +28,9 @@ This article explains how to update an existing ASP.NET Core 3.1 project to ASP.
 
 ---
 
-## Update .NET Core SDK version in global.json
+## Update .NET SDK version in global.json
 
-If you rely upon a [global.json](/dotnet/core/tools/global-json) file to target a specific .NET Core SDK version, update the `version` property to the .NET 5 SDK version that's installed. For example:
+If you rely upon a [global.json](/dotnet/core/tools/global-json) file to target a specific .NET SDK version, update the `version` property to the .NET 5 SDK version that's installed. For example:
 
 ```diff
 {
@@ -779,4 +779,4 @@ The following tutorials also explain the migration:
 
 ## Review breaking changes
 
-For breaking changes from .NET Core 3.1 to .NET 5, see [Breaking changes for migration from version 3.1 to 5.0](/dotnet/core/compatibility/3.1-5.0). ASP.NET Core and Entity Framework Core are also included in the list.
+For breaking changes from .NET 3.1 to .NET 5, see [Breaking changes for migration from version 3.1 to 5.0](/dotnet/core/compatibility/3.1-5.0). ASP.NET Core and Entity Framework Core are also included in the list.

aspnetcore/migration/60-70.md

@@ -26,9 +26,9 @@ This article explains how to update an existing ASP.NET Core in .NET 6 project t
 
 ---
 
-## Update .NET Core SDK version in global.json
+## Update .NET SDK version in global.json
 
-If you rely on a [global.json](/dotnet/core/tools/global-json) file to target a specific .NET Core SDK version, update the `version` property to the .NET 7 SDK version that's installed. For example:
+If you rely on a [global.json](/dotnet/core/tools/global-json) file to target a specific .NET SDK version, update the `version` property to the .NET 7 SDK version that's installed. For example:
 
 ```diff
 {

aspnetcore/migration/70-80.md

@@ -24,7 +24,7 @@ This article explains how to update an existing ASP.NET Core in .NET 7 project t
 
 ## Update the .NET SDK version in `global.json`
 
-If you rely on a [`global.json`](/dotnet/core/tools/global-json) file to target a specific .NET Core SDK version, update the `version` property to the .NET 8 SDK version that's installed. For example:
+If you rely on a [`global.json`](/dotnet/core/tools/global-json) file to target a specific .NET SDK version, update the `version` property to the .NET 8 SDK version that's installed. For example:
 
 ```diff
 {

aspnetcore/migration/80-90.md

@@ -27,7 +27,7 @@ This article explains how to update an ASP.NET Core in .NET 8 to ASP.NET Core in
 
 ## Update the .NET SDK version in `global.json`
 
-If you rely on a [`global.json`](/dotnet/core/tools/global-json) file to target a specific .NET Core SDK version, update the `version` property to the .NET 9 SDK version that's installed. For example:
+If you rely on a [`global.json`](/dotnet/core/tools/global-json) file to target a specific .NET SDK version, update the `version` property to the .NET 9 SDK version that's installed. For example:
 
 ```diff
 {

aspnetcore/migration/fx-to-core/areas/webapi.md

@@ -228,7 +228,7 @@ Add a new API project to migrate to:
 
 1. Add a new **ASP.NET Core Web Application** project to the solution.
 1. In the **Configure your new project** dialog, Name the project *ProductsCore*, and select **Create**.
-1. In the **Create a new ASP.NET Core Web Application** dialog, confirm that **.NET Core** and **ASP.NET Core 3.1** are selected. Select the **API** project template, and select **Create**.
+1. In the **Create a new ASP.NET Core Web Application** dialog, confirm that **.NET** and **ASP.NET Core 3.1** are selected. Select the **API** project template, and select **Create**.
 1. Remove the `WeatherForecast.cs` and `Controllers/WeatherForecastController.cs` example files from the new *ProductsCore* project.
 
 The solution now contains two projects. The following sections explain migrating the *ProductsApp* project's contents to the *ProductsCore* project.