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

Comments

@mkArtakMSFT
Copy link
Contributor

@mkArtakMSFT mkArtakMSFT commented Dec 3, 2019

No description provided.

@mkArtakMSFT

This comment has been minimized.

Copy link
Contributor Author

@mkArtakMSFT mkArtakMSFT commented Jan 13, 2020

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

@mkArtakMSFT mkArtakMSFT moved this from 3.2 - Preview 1 to 3.2 - Preview 2 in Blazor WASM Jan 13, 2020
@NTaylorMullen

This comment has been minimized.

Copy link
Contributor

@NTaylorMullen 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

This comment has been minimized.

Copy link
Contributor

@NTaylorMullen NTaylorMullen commented Feb 21, 2020

@SteveSandersonMS @danroth27 @mkArtakMSFT I have a PR out for O#: OmniSharp/omnisharp-vscode#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 Working label Feb 26, 2020
@NTaylorMullen NTaylorMullen removed the Working label Feb 26, 2020
@NTaylorMullen NTaylorMullen moved this from In Progress (CC: 21st Feb) to Done in Blazor WASM Feb 26, 2020
@mkArtakMSFT mkArtakMSFT added the Done label Feb 27, 2020
@msftbot msftbot bot 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.
Projects
Blazor WASM
  
Done
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
3 participants
You can’t perform that action at this time.