Perform a pass cleaning up the web templates

[pranavkm]

• Could we move the DevServer in to the SDK / tool that's magically wired up the SDK?
• Should we consider creating a framework reference for WASM? We could remove all package references
• Why does the Client in the hosted app reference the dev server?
• Simplify file structure
• Theme redesign (for all the templates)

Also, use this issue to synchronize templates (web with MAUI): dotnet/maui#7868

[ghost]

Thanks for contacting us.
We're moving this issue to the Next sprint planning milestone for future evaluation / consideration. We will evaluate the request when we are planning the work for the next milestone. To learn more about what to expect next and how this issue will be handled you can read more about our triage process here.

[ghost]

We've moved this issue to the Backlog milestone. This means that it is not going to be worked on for the coming release. We will reassess the backlog following the current release and consider this item at that time. To learn more about our issue management process and to have better expectation regarding different types of issues you can read our Triage Process.

[TanayParikh]

I believe #37201 could be taken care of during this cleanup pass of templates.

[guardrex]

Reported by Kirk: There's a delta on CSS file indentation with most templates now adopting two spaces. The Blazor templates have four today.

[javiercn]

#40935

[guardrex]

Consider dropping the underscore prefix throughout project templates to make user code consistent among project templates, Blazor docs samples/examples, and dev coding guidelines. A search turned up the following. This might be all of them for Blazor project templates:

• https://github.com/dotnet/aspnetcore/blob/main/src/ProjectTemplates/Web.ProjectTemplates/content/ComponentsWebAssembly-CSharp/Server/Controllers/WeatherForecastController.cs#L36
• https://github.com/dotnet/aspnetcore/blob/main/src/ProjectTemplates/Web.ProjectTemplates/content/BlazorServerWeb-CSharp/Pages/Error.cshtml.cs#L15
• https://github.com/dotnet/aspnetcore/blob/main/src/ProjectTemplates/Web.ProjectTemplates/content/BlazorServerWeb-CSharp/Areas/Identity/RevalidatingIdentityAuthenticationStateProvider.cs#L13-L14
• https://github.com/dotnet/aspnetcore/blob/main/src/ProjectTemplates/Web.ProjectTemplates/content/ComponentsWebAssembly-CSharp/Server/Pages/Error.cshtml.cs#L15
• https://github.com/dotnet/aspnetcore/blob/main/src/ProjectTemplates/Web.ProjectTemplates/content/ComponentsWebAssembly-CSharp/Server/Controllers/OidcConfigurationController.cs#L8

Cross References:

• Remove underscores on Blazor topic+sample members (dotnet/AspNetCore.Docs #18176)
• Remark by Pranav that the next reference† calls for not prefixing (dotnet/AspNetCore.Docs #17797)
• †Next reference: .NET Fundamentals: Names of Type Members: Names of Fields
• Blazor access modifiers and field underscores (dotnet/aspnetcore #18446) - Additional remarks by Ryan and Pranav, including a comment that there was an internal meeting and a decision to use the this keyword for dev code/project templates.

[ghost]

Thanks for contacting us.

We're moving this issue to the .NET 7 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.

[ghost]

We've moved this issue to the Backlog milestone. This means that it is not going to be worked on for the coming release. We will reassess the backlog following the current release and consider this item at that time. To learn more about our issue management process and to have better expectation regarding different types of issues you can read our Triage Process.

[danroth27]

We think the important parts of this issue are already covered by other issues.