Skip to content

Commit

Permalink
Blazor RC1 updates (dotnet#19878)
Browse files Browse the repository at this point in the history
  • Loading branch information
guardrex authored Sep 15, 2020
1 parent 1e40fbf commit b288444
Show file tree
Hide file tree
Showing 3 changed files with 4 additions and 15 deletions.
2 changes: 1 addition & 1 deletion aspnetcore/blazor/forms-validation.md
Original file line number Diff line number Diff line change
Expand Up @@ -262,7 +262,7 @@ In the following example:

## Display name support

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

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

Expand Down
4 changes: 2 additions & 2 deletions aspnetcore/blazor/fundamentals/routing.md
Original file line number Diff line number Diff line change
Expand Up @@ -181,7 +181,7 @@ For more information, see <xref:fundamentals/routing>.

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

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

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

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

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

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

::: moniker-end

Expand Down
13 changes: 1 addition & 12 deletions aspnetcore/blazor/webassembly-lazy-load-assemblies.md
Original file line number Diff line number Diff line change
Expand Up @@ -26,21 +26,10 @@ Mark assemblies for lazy loading in the app's project file (`.csproj`) using the

```xml
<ItemGroup>
<BlazorWebAssemblyLazyLoad Include="GrantImaharaRobotControls" />
<BlazorWebAssemblyLazyLoad Include="GrantImaharaRobotControls.dll" />
</ItemGroup>
```

Only assemblies that are used by the app can be lazily loaded. The linker strips unused assemblies from published output.

> [!NOTE]
> In .NET 5 Release Candidate 1 (RC1) or later, which will be released in mid-September, the assembly name will require the `.dll` extension:
>
> ```xml
> <ItemGroup>
> <BlazorWebAssemblyLazyLoad Include="GrantImaharaRobotControls.dll" />
> </ItemGroup>
> ```
## `Router` component

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

0 comments on commit b288444

Please sign in to comment.