The Properties/launchSettings.json file is no longer used to control the environment in standalone Blazor WebAssembly apps.

[swheat-starr]

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.

This page documents the change that discontinues use of launchSettings.json to set the environment variable for standalone Blazor WebAssembly apps. The reasons for this change are not clear. I suggest that this change negates two important features of launchSettings.json:

1.) A developer can easily change environments without making a change to a source-controlled file. This means that there is no worry of the change being inadvertently checked in.

2.) launchSettings.json works well and works consistently with the rest of the .net ecosystem.

Describe the solution you'd like

Does the use of launchSettings.json exclude the changes made in .net 10? If not, I suggest that the pre-.net 10 functionality be restored to allow the continued use of launchSettings.json. If a developer wishes to also use WasmApplicationEnvironmentName also than perhaps that setting can supersede launchSettings.json.

Additional context

Reference:
#59456