Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 3 additions & 4 deletions aspnetcore/blazor/components/render-modes.md
Original file line number Diff line number Diff line change
Expand Up @@ -221,11 +221,10 @@ Prerendering is enabled by default for interactive components.

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).

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

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.
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.

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

Expand Down
2 changes: 1 addition & 1 deletion aspnetcore/fundamentals/openapi/aspnetcore-openapi.md
Original file line number Diff line number Diff line change
Expand Up @@ -86,7 +86,7 @@ The OpenAPI document can be generated in either JSON or YAML format. By default,
app.MapOpenApi("/openapi/{documentName}.yaml");
```

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

### Customize the OpenAPI document name

Expand Down
3 changes: 3 additions & 0 deletions aspnetcore/grpc/netstandard.md
Original file line number Diff line number Diff line change
Expand Up @@ -86,6 +86,9 @@ var client = new Greeter.GreeterClient(channel);
var response = await client.SayHelloAsync(new HelloRequest { Name = ".NET" });
```

> [!NOTE]
> 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.
## gRPC C# core-library

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:
Expand Down
Loading