Blazor Web App template: The `Layout` folder (namespace) isn't present in the `_Imports` file

[guardrex]

Is there an existing issue for this?

• I have searched the existing issues

Is your feature request related to a problem? Please describe the problem.

In prior releases (Blazor Server), the Shared folder namespace was placed in the _Imports file. This release for BWAs, only the Components folder is present. This results in the incongruous situation where "Layout." has to be supplied on DefaultLayout ...

<RouteView RouteData="@routeData" DefaultLayout="@typeof(Layout.MainLayout)" />

... which wasn't required before and still isn't required for Blazor WebAssembly apps. It's breaking the docs and requiring further versioned content.

Describe the solution you'd like

Consider adding it to the _Imports file ...

@using BlazorWeb_CSharp.Components.Layout

Remove "Layout." from the two DefaultLayout params in Routes.razor.

Additional context

BTW .... It seems like if the components folder is plural (Components) and the routable components folder is plural (Pages) that the layout folder name should also be plural (Layouts).

Thanks for contacting us.

We're moving this issue to the .NET 9 Planning milestone for future evaluation / consideration. We would like to keep this around to collect more feedback, which can help us with prioritizing this work. We will re-evaluate this issue, during our next planning meeting(s).
If we later determine, that the issue has no community involvement, or it's very rare and low-impact issue, we will close it - so that the team can focus on more important and high impact issues.
To learn more about what to expect next and how this issue will be handled you can read more about our triage process here.

Thanks for contacting us.

We're moving this issue to the .NET 9 Planning milestone for future evaluation / consideration. We would like to keep this around to collect more feedback, which can help us with prioritizing this work. We will re-evaluate this issue, during our next planning meeting(s).
If we later determine, that the issue has no community involvement, or it's very rare and low-impact issue, we will close it - so that the team can focus on more important and high impact issues.
To learn more about what to expect next and how this issue will be handled you can read more about our triage process here.