Replace .NET Core with .NET in gRPC documentation

Copilot · danroth27 · Copilot · commit 47c07359f9ea · 2025-07-22T19:47:26.000Z
Co-authored-by: danroth27 &lt;1874516+danroth27@users.noreply.github.com&gt;
diff --git a/aspnetcore/grpc/client.md b/aspnetcore/grpc/client.md
@@ -47,7 +47,7 @@ To configure a gRPC channel to use TLS, ensure the server address starts with `h
 > [!TIP]
 > gRPC supports client certificate authentication over TLS. For information on configuring client certificates with a gRPC channel, see <xref:grpc/authn-and-authz#client-certificate-authentication>.
 
-To call unsecured gRPC services, ensure the server address starts with `http`. For example, `GrpcChannel.ForAddress("http://localhost:5000")` uses HTTP protocol. In .NET Core 3.1, additional configuration is required to [call insecure gRPC services with the .NET client](xref:grpc/troubleshoot#call-insecure-grpc-services-with-net-core-client).
+To call unsecured gRPC services, ensure the server address starts with `http`. For example, `GrpcChannel.ForAddress("http://localhost:5000")` uses HTTP protocol. In .NET 3.1, additional configuration is required to [call insecure gRPC services with the .NET client](xref:grpc/troubleshoot#call-insecure-grpc-services-with-net-core-client).
 
 ### Client performance
 
diff --git a/aspnetcore/grpc/configuration.md b/aspnetcore/grpc/configuration.md
@@ -91,7 +91,7 @@ Note that client interceptors aren't configured with `GrpcChannelOptions`. Inste
 
 `Grpc.Net.Client` uses a HTTP transport derived from `HttpMessageHandler` to make HTTP requests. Each handler offers additional options for how HTTP requests are made.
 
-The handler is configured on a channel and can be overridden by setting `GrpcChannelOptions.HttpHandler`. .NET Core 3 and .NET 5 or later uses <xref:System.Net.Http.SocketsHttpHandler> by default. gRPC client apps on .NET Framework [should configure WinHttpHandler](xref:grpc/netstandard#net-framework).
+The handler is configured on a channel and can be overridden by setting `GrpcChannelOptions.HttpHandler`. .NET 3 and .NET 5 or later uses <xref:System.Net.Http.SocketsHttpHandler> by default. gRPC client apps on .NET Framework [should configure WinHttpHandler](xref:grpc/netstandard#net-framework).
 
 For more information about the different handlers and their configuration options, see:
 
diff --git a/aspnetcore/grpc/diagnostics.md b/aspnetcore/grpc/diagnostics.md
@@ -16,13 +16,13 @@ By [James Newton-King](https://twitter.com/jamesnk)
 :::moniker range=">= aspnetcore-6.0"
 This article provides guidance for gathering diagnostics from a gRPC app to help troubleshoot issues. Topics covered include:
 
-* **Logging** - Structured logs written to [.NET Core logging](xref:fundamentals/logging/index). <xref:Microsoft.Extensions.Logging.ILogger> is used by app frameworks to write logs, and by users for their own logging in an app.
+* **Logging** - Structured logs written to [.NET logging](xref:fundamentals/logging/index). <xref:Microsoft.Extensions.Logging.ILogger> is used by app frameworks to write logs, and by users for their own logging in an app.
 * **Tracing** - Events related to an operation written using `DiaganosticSource` and `Activity`. Traces from diagnostic source are commonly used to collect app telemetry by libraries such as [Application Insights](/azure/azure-monitor/app/asp-net-core) and [OpenTelemetry](https://github.com/open-telemetry/opentelemetry-dotnet).
 * **Metrics** - Representation of data measures over intervals of time, for example, requests per second. Metrics are emitted using `EventCounter` and can be observed using [dotnet-counters](/dotnet/core/diagnostics/dotnet-counters) command-line tool or with [Application Insights](/azure/azure-monitor/app/eventcounters).
 
 ## Logging
 
-gRPC services and the gRPC client write logs using [.NET Core logging](xref:fundamentals/logging/index). Logs are a good place to start when debugging unexpected behavior in service and client apps.
+gRPC services and the gRPC client write logs using [.NET logging](xref:fundamentals/logging/index). Logs are a good place to start when debugging unexpected behavior in service and client apps.
 
 ### gRPC services logging
 
@@ -240,13 +240,13 @@ Specify the gRPC counters for Application Insight to collect in `Startup.cs`:
 :::moniker range=">= aspnetcore-3.0 < aspnetcore-6.0"
 This article provides guidance for gathering diagnostics from a gRPC app to help troubleshoot issues. Topics covered include:
 
-* **Logging** - Structured logs written to [.NET Core logging](xref:fundamentals/logging/index). <xref:Microsoft.Extensions.Logging.ILogger> is used by app frameworks to write logs, and by users for their own logging in an app.
+* **Logging** - Structured logs written to [.NET logging](xref:fundamentals/logging/index). <xref:Microsoft.Extensions.Logging.ILogger> is used by app frameworks to write logs, and by users for their own logging in an app.
 * **Tracing** - Events related to an operation written using `DiaganosticSource` and `Activity`. Traces from diagnostic source are commonly used to collect app telemetry by libraries such as [Application Insights](/azure/azure-monitor/app/asp-net-core) and [OpenTelemetry](https://github.com/open-telemetry/opentelemetry-dotnet).
 * **Metrics** - Representation of data measures over intervals of time, for example, requests per second. Metrics are emitted using `EventCounter` and can be observed using [dotnet-counters](/dotnet/core/diagnostics/dotnet-counters) command line tool or with [Application Insights](/azure/azure-monitor/app/eventcounters).
 
 ## Logging
 
-gRPC services and the gRPC client write logs using [.NET Core logging](xref:fundamentals/logging/index). Logs are a good place to start when debugging unexpected behavior in service and client apps.
+gRPC services and the gRPC client write logs using [.NET logging](xref:fundamentals/logging/index). Logs are a good place to start when debugging unexpected behavior in service and client apps.
 
 ### gRPC services logging
 
diff --git a/aspnetcore/grpc/dotnet-grpc.md b/aspnetcore/grpc/dotnet-grpc.md
@@ -11,11 +11,11 @@ uid: grpc/dotnet-grpc
 
 [!INCLUDE[](~/includes/not-latest-version.md)]
 
-`dotnet-grpc` is a .NET Core Global Tool for managing [Protobuf (`.proto`)](xref:grpc/basics#proto-file) references within a .NET gRPC project. The tool can be used to add, refresh, remove, and list Protobuf references.
+`dotnet-grpc` is a .NET Global Tool for managing [Protobuf (`.proto`)](xref:grpc/basics#proto-file) references within a .NET gRPC project. The tool can be used to add, refresh, remove, and list Protobuf references.
 
 ## Installation
 
-To install the `dotnet-grpc` [.NET Core Global Tool](/dotnet/core/tools/global-tools), run the following command:
+To install the `dotnet-grpc` [.NET Global Tool](/dotnet/core/tools/global-tools), run the following command:
 
 ```dotnetcli
 dotnet tool install -g dotnet-grpc
diff --git a/aspnetcore/grpc/grpcweb.md b/aspnetcore/grpc/grpcweb.md
@@ -51,7 +51,7 @@ Alternatively, the gRPC-Web middleware can be configured so that all services su
 :::code language="csharp" source="~/grpc/grpcweb/sample/8.x/GrpcGreeter/Program.cs" id="snippet_WebEnableAllServices" highlight="9":::
 
 > [!NOTE]
-> There is a known issue that causes gRPC-Web to fail when [hosted by HTTP.sys](xref:fundamentals/servers/httpsys) in .NET Core 3.x.
+> There is a known issue that causes gRPC-Web to fail when [hosted by HTTP.sys](xref:fundamentals/servers/httpsys) in .NET 3.x.
 >
 > A workaround to get gRPC-Web working on HTTP.sys is available in [Grpc-web experimental and UseHttpSys()? (grpc/grpc-dotnet #853)](https://github.com/grpc/grpc-dotnet/issues/853#issuecomment-610078202).
 
diff --git a/aspnetcore/grpc/grpcweb/includes/grpcweb3-5.md b/aspnetcore/grpc/grpcweb/includes/grpcweb3-5.md
@@ -36,7 +36,7 @@ Alternatively, the gRPC-Web middleware can be configured so that all services su
 [!code-csharp[](~/grpc/grpcweb/sample/3-5.x/AllServicesSupportExample_Startup.cs?name=snippet_1&highlight=12)]
 
 > [!NOTE]
-> There is a known issue that causes gRPC-Web to fail when [hosted by HTTP.sys](xref:fundamentals/servers/httpsys) in .NET Core 3.x.
+> There is a known issue that causes gRPC-Web to fail when [hosted by HTTP.sys](xref:fundamentals/servers/httpsys) in .NET 3.x.
 >
 > A workaround to get gRPC-Web working on HTTP.sys is available in [Grpc-web experimental and UseHttpSys()? (grpc/grpc-dotnet #853)](https://github.com/grpc/grpc-dotnet/issues/853#issuecomment-610078202).
 
diff --git a/aspnetcore/grpc/grpcweb/includes/grpcweb6-7.md b/aspnetcore/grpc/grpcweb/includes/grpcweb6-7.md
@@ -36,7 +36,7 @@ Alternatively, the gRPC-Web middleware can be configured so that all services su
 :::code language="csharp" source="~/grpc/grpcweb/sample/8.x/GrpcGreeter/Program.cs" id="snippet_WebEnableAllServices" highlight="9":::
 
 > [!NOTE]
-> There is a known issue that causes gRPC-Web to fail when [hosted by HTTP.sys](xref:fundamentals/servers/httpsys) in .NET Core 3.x.
+> There is a known issue that causes gRPC-Web to fail when [hosted by HTTP.sys](xref:fundamentals/servers/httpsys) in .NET 3.x.
 >
 > A workaround to get gRPC-Web working on HTTP.sys is available in [Grpc-web experimental and UseHttpSys()? (grpc/grpc-dotnet #853)](https://github.com/grpc/grpc-dotnet/issues/853#issuecomment-610078202).
 
diff --git a/aspnetcore/grpc/interprocess/includes/interprocess5-7.md b/aspnetcore/grpc/interprocess/includes/interprocess5-7.md
@@ -12,7 +12,7 @@ Processes running on the same machine can be designed to communicate with each o
 
 gRPC calls are sent from a client to a server. To communicate between apps on a machine with gRPC, at least one app must host an ASP.NET Core gRPC server.
 
-ASP.NET Core and gRPC can be hosted in any app using .NET Core 3.1 or later by adding the `Microsoft.AspNetCore.App` framework to the project.
+ASP.NET Core and gRPC can be hosted in any app using .NET 3.1 or later by adding the `Microsoft.AspNetCore.App` framework to the project.
 
 [!code-xml[](~/grpc/interprocess/Server.csproj?highlight=4-6)]
 
diff --git a/aspnetcore/grpc/migration.md b/aspnetcore/grpc/migration.md
@@ -20,8 +20,8 @@ Due to the implementation of the underlying stack, not all features work in the
 
 gRPC C-core and gRPC for .NET have different platform support:
 
-* **gRPC C-core**: A C++ gRPC implementation with its own TLS and HTTP/2 stacks. The `Grpc.Core` package is a .NET wrapper around gRPC C-core and contains a gRPC client and server. It supports .NET Framework, .NET Core, and .NET 5 or later.
-* **gRPC for .NET**: Designed for .NET Core 3.x and .NET 5 or later. It uses TLS and HTTP/2 stacks built into modern .NET releases. The `Grpc.AspNetCore` package contains a gRPC server that is hosted in ASP.NET Core and requires .NET Core 3.x or .NET 5 or later. The `Grpc.Net.Client` package contains a gRPC client. The client in `Grpc.Net.Client` has limited support for .NET Framework using <xref:System.Net.Http.WinHttpHandler>.
+* **gRPC C-core**: A C++ gRPC implementation with its own TLS and HTTP/2 stacks. The `Grpc.Core` package is a .NET wrapper around gRPC C-core and contains a gRPC client and server. It supports .NET Framework, .NET, and .NET 5 or later.
+* **gRPC for .NET**: Designed for .NET 3.x and .NET 5 or later. It uses TLS and HTTP/2 stacks built into modern .NET releases. The `Grpc.AspNetCore` package contains a gRPC server that is hosted in ASP.NET Core and requires .NET 3.x or .NET 5 or later. The `Grpc.Net.Client` package contains a gRPC client. The client in `Grpc.Net.Client` has limited support for .NET Framework using <xref:System.Net.Http.WinHttpHandler>.
 
 For more information, see <xref:grpc/supported-platforms>.
 
diff --git a/aspnetcore/grpc/netstandard.md b/aspnetcore/grpc/netstandard.md
@@ -19,7 +19,7 @@ This article discusses how to use the .NET gRPC client with .NET implementations
 
 The following .NET implementations (or later) support [Grpc.Net.Client](https://www.nuget.org/packages/Grpc.Net.Client/) but don't have full support for HTTP/2:
 
-* .NET Core 2.1
+* .NET 2.1
 * .NET Framework 4.6.1
 * Mono 5.4
 * Universal Windows Platform 10.0.16299
diff --git a/aspnetcore/grpc/performance.md b/aspnetcore/grpc/performance.md
@@ -62,7 +62,7 @@ var channel = GrpcChannel.ForAddress("https://localhost", new GrpcChannelOptions
 
 :::moniker-end
 
-There are a couple of workarounds for .NET Core 3.1 apps:
+There are a couple of workarounds for .NET 3.1 apps:
 
 * Create separate gRPC channels for areas of the app with high load. For example, the `Logger` gRPC service might have a high load. Use a separate channel to create the `LoggerClient` in the app.
 * Use a pool of gRPC channels, for example,  create a list of gRPC channels. `Random` is used to pick a channel from the list each time a gRPC channel is needed. Using `Random` randomly distributes calls over multiple connections.
diff --git a/aspnetcore/grpc/security.md b/aspnetcore/grpc/security.md
@@ -14,7 +14,7 @@ uid: grpc/security
 
 By [James Newton-King](https://twitter.com/jamesnk)
 
-This article provides information on securing gRPC with .NET Core.
+This article provides information on securing gRPC with .NET.
 
 ## Transport security
 
diff --git a/aspnetcore/grpc/supported-platforms.md b/aspnetcore/grpc/supported-platforms.md
@@ -29,14 +29,14 @@ gRPC on .NET supports both wire-formats. `application/grpc` is used by default.
 
 ## ASP.NET Core gRPC server requirements
 
-Hosting gRPC services with ASP.NET Core requires .NET Core 3.x or later.
+Hosting gRPC services with ASP.NET Core requires .NET 3.x or later.
 
 > [!div class="checklist"]
 >
 > * .NET 5 or later
-> * .NET Core 3
+> * .NET 3
 
-ASP.NET Core gRPC services can be hosted on all operating system that .NET Core supports.
+ASP.NET Core gRPC services can be hosted on all operating system that .NET supports.
 
 :::moniker range=">= aspnetcore-8.0"
 
@@ -87,7 +87,7 @@ For information about configuring ASP.NET Core servers to run gRPC, see <xref:gr
 
 ## .NET gRPC client requirements
 
-The [Grpc.Net.Client](https://www.nuget.org/packages/Grpc.Net.Client/) package supports gRPC calls over HTTP/2 on .NET Core 3 and .NET 5 or later.
+The [Grpc.Net.Client](https://www.nuget.org/packages/Grpc.Net.Client/) package supports gRPC calls over HTTP/2 on .NET 3 and .NET 5 or later.
 
 Limited support is available for gRPC over HTTP/2 on .NET Framework. Other .NET versions such as UWP and Unity don't have required HTTP/2 support, and must use gRPC-Web instead.
 
@@ -96,8 +96,8 @@ The following table lists .NET implementations and their gRPC client support:
 | .NET implementation                          | gRPC over HTTP/2   | gRPC-Web   |
 |----------------------------------------------|--------------------|------------|
 | .NET 5 or later                              | ✔️                | ✔️         |
-| .NET Core 3                                  | ✔️                | ✔️         |
-| .NET Core 2.1                                | ❌                | ✔️         |
+| .NET 3                                  | ✔️                | ✔️         |
+| .NET 2.1                                | ❌                | ✔️         |
 | .NET Framework 4.6.1                         | ⚠️&dagger;        | ✔️         |
 | Blazor WebAssembly                           | ❌                | ✔️         |
 | Mono 5.4                                     | ❌                | ✔️         |
diff --git a/aspnetcore/grpc/troubleshoot.md b/aspnetcore/grpc/troubleshoot.md
@@ -34,7 +34,7 @@ info: Microsoft.Hosting.Lifetime[0]
       Hosting environment: Development
 ```
 
-The .NET Core client must use `https` in the server address to make calls with a secured connection:
+The .NET client must use `https` in the server address to make calls with a secured connection:
 
 [!code-csharp[](~/grpc/troubleshoot/sample/8.0/GrpcGreeterClient/Program.cs?name=snippet_StandardHTTPS)]
 
@@ -60,14 +60,14 @@ The [gRPC client factory](xref:grpc/clientfactory) allows calls without a truste
 > [!WARNING]
 > Untrusted certificates should only be used during app development. Production apps should always use valid certificates.
 
-## Call insecure gRPC services with .NET Core client
+## Call insecure gRPC services with .NET client
 
 The .NET gRPC client can call insecure gRPC services by specifing `http` in the server address. For example, `GrpcChannel.ForAddress("http://localhost:5000")`.
 
 There are some additional requirements to call insecure gRPC services depending on the .NET version an app is using:
 
 * .NET 5 or later requires [Grpc.Net.Client](https://www.nuget.org/packages/Grpc.Net.Client) version 2.32.0 or later.
-* .NET Core 3.x requires additional configuration. The app must set the `System.Net.Http.SocketsHttpHandler.Http2UnencryptedSupport` switch to `true`. For more information see [Asp.Net Core 3.x: Call insecure gRPC services with the .NET client](xref:grpc/troubleshoot?view=aspnetcore-3.1#call-insecure-grpc-services-with-net-core-client-2):
+* .NET 3.x requires additional configuration. The app must set the `System.Net.Http.SocketsHttpHandler.Http2UnencryptedSupport` switch to `true`. For more information see [Asp.Net Core 3.x: Call insecure gRPC services with the .NET client](xref:grpc/troubleshoot?view=aspnetcore-3.1#call-insecure-grpc-services-with-net-core-client-2):
 
 > [!IMPORTANT]
 > Insecure gRPC services must be hosted on a HTTP/2-only port. For more information, see [ASP.NET Core protocol negotiation](xref:grpc/aspnetcore#protocol-negotiation).
@@ -113,7 +113,7 @@ WPF projects have a [known issue](https://github.com/dotnet/wpf/issues/810) that
 
 You can workaround this issue by:
 
-1. Create a new .NET Core class library project.
+1. Create a new .NET class library project.
 2. In the new project, add references to enable [C# code generation from `.proto` files](xref:grpc/basics#generated-c-assets):
     * Add the following package references:
         * [Grpc.Tools](https://www.nuget.org/packages/Grpc.Tools/)
diff --git a/aspnetcore/grpc/troubleshoot/includes/troubleshoot3-7.md b/aspnetcore/grpc/troubleshoot/includes/troubleshoot3-7.md
diff --git a/aspnetcore/grpc/why-migrate-wcf-to-dotnet-grpc.md b/aspnetcore/grpc/why-migrate-wcf-to-dotnet-grpc.md

Original file line number	Diff line number	Diff line change
`@@ -51,7 +51,7 @@ Alternatively, the gRPC-Web middleware can be configured so that all services su`
`51`	`51`	`:::code language="csharp" source="~/grpc/grpcweb/sample/8.x/GrpcGreeter/Program.cs" id="snippet_WebEnableAllServices" highlight="9":::`
`52`	`52`
`53`	`53`	`> [!NOTE]`
`54`		`-> There is a known issue that causes gRPC-Web to fail when [hosted by HTTP.sys](xref:fundamentals/servers/httpsys) in .NET Core 3.x.`
	`54`	`+> There is a known issue that causes gRPC-Web to fail when [hosted by HTTP.sys](xref:fundamentals/servers/httpsys) in .NET 3.x.`
`55`	`55`	`>`
`56`	`56`	`> A workaround to get gRPC-Web working on HTTP.sys is available in [Grpc-web experimental and UseHttpSys()? (grpc/grpc-dotnet #853)](https://github.com/grpc/grpc-dotnet/issues/853#issuecomment-610078202).`
`57`	`57`
Original file line number	Diff line number	Diff line change
`@@ -36,7 +36,7 @@ Alternatively, the gRPC-Web middleware can be configured so that all services su`
`36`	`36`	`[!code-csharp[](~/grpc/grpcweb/sample/3-5.x/AllServicesSupportExample_Startup.cs?name=snippet_1&highlight=12)]`
`37`	`37`
`38`	`38`	`> [!NOTE]`
`39`		`-> There is a known issue that causes gRPC-Web to fail when [hosted by HTTP.sys](xref:fundamentals/servers/httpsys) in .NET Core 3.x.`
	`39`	`+> There is a known issue that causes gRPC-Web to fail when [hosted by HTTP.sys](xref:fundamentals/servers/httpsys) in .NET 3.x.`
`40`	`40`	`>`
`41`	`41`	`> A workaround to get gRPC-Web working on HTTP.sys is available in [Grpc-web experimental and UseHttpSys()? (grpc/grpc-dotnet #853)](https://github.com/grpc/grpc-dotnet/issues/853#issuecomment-610078202).`
`42`	`42`