Skip to content

Commit bcdd272

Browse files
authored
Merge pull request #35759 from dotnet/main
2 parents 627a165 + c6bf58d commit bcdd272

File tree

3 files changed

+7
-5
lines changed

3 files changed

+7
-5
lines changed

aspnetcore/blazor/components/render-modes.md

Lines changed: 3 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -221,11 +221,10 @@ Prerendering is enabled by default for interactive components.
221221

222222
Internal navigation for interactive routing doesn't involve requesting new page content from the server. Therefore, prerendering doesn't occur for internal page requests, including for [enhanced navigation](xref:blazor/fundamentals/routing#enhanced-navigation-and-form-handling). For more information, see [Static versus interactive routing](xref:blazor/fundamentals/routing#static-versus-interactive-routing), [Interactive routing and prerendering](xref:blazor/components/prerender#interactive-routing-and-prerendering), and [Enhanced navigation and form handling](xref:blazor/fundamentals/routing#enhanced-navigation-and-form-handling).
223223

224-
<!-- UPDATE 10.0 Tracking https://github.com/dotnet/aspnetcore/issues/55635
225-
for .NET 10 work in this area. Update the following remark
226-
if changes are made to the framework. -->
224+
<!-- UPDATE 11.0 Tracking https://github.com/dotnet/aspnetcore/issues/55635
225+
for .NET 11 work in this area. -->
227226

228-
Disabling prerendering using the following techniques only takes effect for top-level render modes. If a parent component specifies a render mode, the prerendering settings of its children are ignored. This behavior is under investigation for possible changes with the release of .NET 10 in November, 2025.
227+
Disabling prerendering using the following techniques only takes effect for top-level render modes. If a parent component specifies a render mode, the prerendering settings of its children are ignored.
229228

230229
To disable prerendering for a *component instance*, pass the `prerender` flag with a value of `false` to the render mode:
231230

aspnetcore/fundamentals/openapi/aspnetcore-openapi.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -86,7 +86,7 @@ The OpenAPI document can be generated in either JSON or YAML format. By default,
8686
app.MapOpenApi("/openapi/{documentName}.yaml");
8787
```
8888

89-
Generating penAPI documents in YAML format at build time is currently not supported, but planned in a future preview.
89+
Generating OpenAPI documents in YAML format at build time is currently not supported, but planned in a future preview.
9090

9191
### Customize the OpenAPI document name
9292

aspnetcore/grpc/netstandard.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -86,6 +86,9 @@ var client = new Greeter.GreeterClient(channel);
8686
var response = await client.SayHelloAsync(new HelloRequest { Name = ".NET" });
8787
```
8888

89+
> [!NOTE]
90+
> The gRPC client on .NET Framework is slower than on modern .NET versions. For improved gRPC performance, apps should be updated to use modern .NET.
91+
8992
## gRPC C# core-library
9093

9194
An alternative option for .NET Framework has been to use [gRPC C# core-library](https://grpc.io/docs/languages/csharp/quickstart/) to make gRPC calls. gRPC C# core-library is:

0 commit comments

Comments
 (0)