question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Blazor WASM debugging in VSC unable to open browser

See original GitHub issue

Issue moved from dotnet/aspnetcore#22527


From @guardrex on Thursday, June 4, 2020 12:48:25 AM

Describe the bug

Edge doesn’t open for WASM debugging in VSC.

To Reproduce

Stock WASM app created from the 3.2 template and configured for Edge …

{
    "version": "0.2.0",
    "configurations": [
        {
            "name": "Launch and Debug Standalone Blazor WebAssembly App",
            "type": "blazorwasm",
            "request": "launch",
            "cwd": "${workspaceFolder}",
            "browser": "edge"
        }
    ]
}

Exception

image

Additional note

The error dialog suggests setting the runtime executable for Edge (runtimeExecutable), but I don’t think that’s possible (not without hacks perhaps). Edge docs don’t reveal much info about how Edge is launched, and they certainly they don’t speak to an executable that does it. Research seemed to indicate that Edge doesn’t launch via an executable.

Further technical details

.NET Core SDK (reflecting any global.json): Version: 3.1.300 Commit: b2475c1295

Runtime Environment: OS Name: Windows OS Version: 10.0.18363 OS Platform: Windows RID: win10-x64 Base Path: C:\Program Files\dotnet\sdk\3.1.300\

Host (useful for support): Version: 3.1.4 Commit: 0c2e69caa6

.NET Core SDKs installed: 3.1.300 [C:\Program Files\dotnet\sdk]

.NET Core runtimes installed: Microsoft.AspNetCore.All 2.1.18 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All] Microsoft.AspNetCore.All 2.2.8 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All] Microsoft.AspNetCore.App 2.1.18 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App] Microsoft.AspNetCore.App 2.2.8 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App] Microsoft.AspNetCore.App 3.0.0 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App] Microsoft.AspNetCore.App 3.1.0 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App] Microsoft.AspNetCore.App 3.1.2 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App] Microsoft.AspNetCore.App 3.1.4 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App] Microsoft.NETCore.App 2.1.18 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App] Microsoft.NETCore.App 2.2.8 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App] Microsoft.NETCore.App 3.0.0 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App] Microsoft.NETCore.App 3.1.0 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App] Microsoft.NETCore.App 3.1.2 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App] Microsoft.NETCore.App 3.1.4 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App] Microsoft.WindowsDesktop.App 3.0.0 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App] Microsoft.WindowsDesktop.App 3.1.2 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App] Microsoft.WindowsDesktop.App 3.1.4 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]

VS Code

Version: 1.45.1 (system setup) Commit: 5763d909d5f12fe19f215cbfdd29a91c0fa9208a Date: 2020-05-14T08:27:35.169Z Electron: 7.2.4 Chrome: 78.0.3904.130 Node.js: 12.8.1 V8: 7.8.279.23-electron.0 OS: Windows_NT x64 10.0.18363

JavaScript Debugger (Nightly)

Version: 2020.6.317

Microsoft Edge

Version: 44.18362.449.0

cc: @captainsafia

Issue Analytics

  • State:closed
  • Created 3 years ago
  • Comments:15 (3 by maintainers)

github_iconTop GitHub Comments

1reaction
connor4312commented, Jun 4, 2020

Thanks for confirming, close the issue on this repo then.

0reactions
guardrexcommented, Jun 4, 2020

Safia, rubber 🦆 says that you’ll say yearp! to that.

Thanks again @connor4312 … we’ll steer others in the right direction with the topic.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Blazor WASM debugging in VSC unable to open browser
I suspect that the JS debugger is looking for Edge in a certain location and unable to find it there based on the...
Read more >
Cannot debug Blazor wasm - Stack Overflow
I'm using chromium on linux (ubuntu 20). When I try debug, I get this error in a popup: Unable to launch browser: "Failed...
Read more >
Debug ASP.NET Core Blazor WebAssembly - Microsoft Learn
Troubleshoot · In the Debugger tab, open the developer tools in your browser. · Confirm that you've installed and trusted the ASP.NET Core...
Read more >
Not able to successfully debug Blazor WebAssembly project ...
It looks like there was an issue launching the Chrome debugging browser. This is likely due to a misconfigured Chrome installation on your...
Read more >
vscode and blazor debugging just broke - Reddit
I've been developing blazor wasm apps in vscode for the past few months without incident. ... Unable to launch browser: "Invalid URL: ...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found