Bug: starup error when My ASPNETCORE_ENVIRONMENT is not setting to Development

[dengyakui]

Bug desc

In our project, we have multi environment configs, each of them has a appsettings file.for example:

• appsettings.json (common config info for all env)
• appsettings.2020test.json ( some special configs for 2020test env)
• appsettings.2020prod.json ( some special configs for 2020prod env)

When I change the default ASPNETCORE_ENVIRONMENT to custom name, like "2020test" the MudBlazor got some error after start the project.

My Configs

os: win11
IDE: VS2022 Version 17.0.0 Preview 4.1
local dotnet version : 5.0 latest /6.0 RC2
local MudBlazor version: 5.1.5 + lastest rc

---

How to reproduce

1. Create a startup Blazor Server project using the MudBlazor template
   

2. Open the launch setting file, change the env name from Development to a custome env
   

3. Start the server project, when the browser launch, the UI is a crazy large icon!
   

some static file was 404 when start not as a dev environment.

[JonBunator]

You need to include:
webBuilder.UseStaticWebAssets();
in your program.cs. Then it should work

[JonBunator]

We should also add this to the templates

[psijkof]

The PR was closed, but this issue persists.
Also for WASM when hosted.

PR created:

#133