Blazor WebAssembly debugger cannot launch an Edge version other than stable #30977
Labels
area-blazor
Includes: Blazor, Razor Components
feature-blazor-debugging
This issue is related to debugging of Blazor WebAssembly apps
feature-blazor-wasm
This issue is related to and / or impacts Blazor WebAssembly
good first issue
Good for newcomers.
help wanted
Up for grabs. We would accept a PR to help resolve this issue
Milestone
Duplicate of #30879, which is automatically closed as resolved but is in fact not. As per Issue Management Policies, a new issue is opened.
Describe the bug
Blazor WebAssembly debugger cannot launch an Edge version other than stable because the launch.json config for
blazorwasm
does not supportruntimeExecutable
property.When you try to launch the debugger, the following message is shown:
Adding
runtimeExecutable
in launch.json results in VSC reporting the following error, and the problem is not mitigated.It is suggested that adding
runtimeExecutable
in abrowserConfig
object can solve the problem, but in my case this results in the following warning.See #30879 for more information.
To Reproduce
On a machine with dev/canary and no stable version of Microsoft Edge:
Create a ASP.NET Blazor WebAssembly project and open it in VSC. Or use this repro repo and skip to step 3.
Create the default Blazor WebAssembly run task, which can be something like this:
Start the debugger from VSC.
The web app starts but browser does not launch. The error message shows up a while later.
Adding either
runtimeExecutable
orbrowserConfig
properties will generate a warning, and they do not solve the problem.See #30879 for details. Full
launch.json
config is attached later.Further technical details
dotnet --info
:launch.json
configFull:
Minimal reproducible:
The text was updated successfully, but these errors were encountered: