Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Automatically add debug configuration when opening Blazor WASM projects in VSCode #17549

Closed
mkArtakMSFT opened this issue Dec 3, 2019 · 3 comments
Assignees
Labels
area-blazor Includes: Blazor, Razor Components Done This issue has been fixed enhancement This issue represents an ask for new feature or an enhancement to an existing one feature-blazor-wasm This issue is related to and / or impacts Blazor WebAssembly

Comments

@mkArtakMSFT
Copy link
Member

No description provided.

@mkArtakMSFT mkArtakMSFT added enhancement This issue represents an ask for new feature or an enhancement to an existing one area-blazor Includes: Blazor, Razor Components feature-blazor-wasm This issue is related to and / or impacts Blazor WebAssembly labels Dec 3, 2019
@mkArtakMSFT mkArtakMSFT added this to the blazor-wasm-preview5 milestone Dec 3, 2019
@ghost ghost added the Needs: Triage 🔍 label Dec 3, 2019
@mkArtakMSFT mkArtakMSFT added the blocked The work on this issue is blocked due to some dependency label Jan 13, 2020
@mkArtakMSFT
Copy link
Member Author

This is blocked on the JS Debugger team: https://devdiv.visualstudio.com/DevDiv/_workitems/edit/1028008

@NTaylorMullen
Copy link
Contributor

NTaylorMullen commented Feb 14, 2020

Launch.json config template:

{
    // Use IntelliSense to learn about possible attributes.
    // Hover to view descriptions of existing attributes.
    // For more information, visit: https://go.microsoft.com/fwlink/?linkid=830387
    "version": "0.2.0",
    "configurations": [
 
        {
            "type": "pwa-chrome",
            "request": "launch",
            "name": "Launch Chrome against Blazor",
            "url": "http://localhost:8080",
            "webRoot": "${workspaceFolder}",
            "inspectUri": "{wsProtocol}://{url.hostname}:{url.port}/_framework/debug/ws-proxy?browser={browserInspectUri}"
        }
    ]
}

@NTaylorMullen
Copy link
Contributor

@SteveSandersonMS @danroth27 @mkArtakMSFT I have a PR out for O#: dotnet/vscode-csharp#3593 . I haven't been able to test it end-to-end due to issues but the layout of the launch.json is there.

I'm looking for:

  1. Verification the launch.json has the correct assumptions
  2. A timeline for when I should merge that PR into O# to ensure it doesn't go out before we're ready

@mkArtakMSFT mkArtakMSFT added the Done This issue has been fixed label Feb 27, 2020
@ghost ghost locked as resolved and limited conversation to collaborators Mar 28, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area-blazor Includes: Blazor, Razor Components Done This issue has been fixed enhancement This issue represents an ask for new feature or an enhancement to an existing one feature-blazor-wasm This issue is related to and / or impacts Blazor WebAssembly
Projects
None yet
Development

No branches or pull requests

3 participants