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.

Use edge for blazorwasm config by default

See original GitHub issue

We now have integration with the Edge Tools team that adds an “inspect” icon and functionality to Edge sessions. We should default to Edge so that blazor debugging gets this functionality too.

Currently users manually need to opt-in by specifying browser: edge:

{
  "type": "blazorwasm",
  "name": "Launch and Debug Blazor WebAssembly Application",
  "request": "launch",
  "browser": "edge",
  "url": "http://localhost:5000"
}

@captainsafia / @codepo8

Issue Analytics

State:
Created 2 years ago
Comments:18 (12 by maintainers)

Top GitHub Comments

4reactions

prnamcommented, Sep 13, 2021

In my opinion it should use / open default browser set by user in their machine (to avoid monopoly concerns in future / considering .NET Foundation working in favour of MSFT Corp as deviation from objective or bylaws etc.) and then also have an option of using Safari, Firefox accepted as valid values.

2reactions

connor4312commented, Sep 13, 2021

js-debug uses the default-browser module to check the browser on any platform, to which I PR’d in support for Windows a few months ago 🙂

Top Results From Across the Web

ASP.NET Core Blazor configuration

Configuration in app settings files are loaded by default. In the following example, a UI configuration value is stored in an app settings...

Debug ASP.NET Core Blazor WebAssembly

Blazor WebAssembly apps can be debugged using the browser developer tools in Chromium-based browsers (Edge/Chrome). You can also debug your ...

Visual Studio Code launching Chrome (Edge is my default ...

I found the problem. There is a browser setting in the launch.json file in the blazor project. One can set the browser to...

Blazor wasm debug Edge/MacOS failing : RIDER-70526

Hi @Samuel Carswell , Blazor wasm debugging works with chromium based browsers (Chrome (by default) and Edge). For using MS Edge, please choose ......

VS Code and Blazor WASM: Debug with Hot Reload

This is a post to share my findings on how to set up VS Code to debug a standalone Blazor WebAssembly application with...