Blazor app is not starting when host environment name is changed from Development

[voroninp]

Is there an existing issue for this?

• I have searched the existing issues

Describe the bug

The problem is that index.html file resides in Blazor project.
There's an API which processes .staticwebassets.runtime.json file, so static assets are served correctly when running not published app with dotnet run.

But default app builder uses it only for dev environment.

If I add this call, Blazor works again (with debug mode, though, but you already have tickets for this).

Expected Behavior

I'd propose default templates (and docs as well) contain a commented section with the explanation that this call must be used for any other environment:

// Uncomment it, if you are developing using Environment name other than `Development`
// See docs: .... some link.
// StaticWebAssetsLoader.UseStaticWebAssets(builder.Environment, builder.Configuration);

Steps To Reproduce

No response

Exceptions (if any)

No response

.NET Version

6.0.7

Anything else?

No response

[javiercn]

@voroninp thanks for contacting us.

We are aware of this behavior. However, we do it this way to prevent the feature from being accidentally turned on in production as it serves files from separate locations on disk other than the project.

[voroninp]

@javiercn That's fine, but it's nice to have it documented maybe?

[ghost]

This issue has been resolved and has not had any activity for 1 day. It will be closed for housekeeping purposes.

See our Issue Management Policies for more information.