Skip to content

Commit b288444

Browse files
authored
Blazor RC1 updates (#19878)
1 parent 1e40fbf commit b288444

3 files changed

Lines changed: 4 additions & 15 deletions

File tree

aspnetcore/blazor/forms-validation.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -262,7 +262,7 @@ In the following example:
262262

263263
## Display name support
264264

265-
*This section applies to .NET 5 Release Candidate 1 (RC1) or later, which will be released in mid-September.*
265+
*This section applies to ASP.NET Core in .NET 5 Release Candidate 1 (RC1) or later.*
266266

267267
The following built-in components support display names with the `DisplayName` parameter:
268268

aspnetcore/blazor/fundamentals/routing.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -181,7 +181,7 @@ For more information, see <xref:fundamentals/routing>.
181181

182182
::: moniker range=">= aspnetcore-5.0"
183183

184-
*This section applies to .NET 5 Release Candidate 1 (RC1) or later, which will be released in mid-September.*
184+
*This section applies to ASP.NET Core in .NET 5 Release Candidate 1 (RC1) or later.*
185185

186186
Catch-all route parameters, which capture paths across multiple folder boundaries, are supported in components. The catch-all route parameter must be:
187187

@@ -206,7 +206,7 @@ Slashes and segments of the captured path are decoded. For a route template of `
206206

207207
::: moniker range="< aspnetcore-5.0"
208208

209-
Catch-all route parameters will be supported in .NET 5 Release Candidate 1 (RC1) or later, which will be released in mid-September.*
209+
Catch-all route parameters are supported in ASP.NET Core in .NET 5 Release Candidate 1 (RC1) or later.*
210210

211211
::: moniker-end
212212

aspnetcore/blazor/webassembly-lazy-load-assemblies.md

Lines changed: 1 addition & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -26,21 +26,10 @@ Mark assemblies for lazy loading in the app's project file (`.csproj`) using the
2626

2727
```xml
2828
<ItemGroup>
29-
<BlazorWebAssemblyLazyLoad Include="GrantImaharaRobotControls" />
29+
<BlazorWebAssemblyLazyLoad Include="GrantImaharaRobotControls.dll" />
3030
</ItemGroup>
3131
```
3232

33-
Only assemblies that are used by the app can be lazily loaded. The linker strips unused assemblies from published output.
34-
35-
> [!NOTE]
36-
> In .NET 5 Release Candidate 1 (RC1) or later, which will be released in mid-September, the assembly name will require the `.dll` extension:
37-
>
38-
> ```xml
39-
> <ItemGroup>
40-
> <BlazorWebAssemblyLazyLoad Include="GrantImaharaRobotControls.dll" />
41-
> </ItemGroup>
42-
> ```
43-
4433
## `Router` component
4534

4635
Blazor's `Router` component designates which assemblies Blazor searches for routable components. The `Router` component is also responsible for rendering the component for the route where the user navigates. The `Router` component supports an `OnNavigateAsync` feature that can be used in conjunction with lazy loading.

0 commit comments

Comments
 (0)