Reputation: 211
I've lost a lot of days on this and am hoping for some direction even if it is a different site to post on.
I am working on a Blazor Web Assembly application using VS 2022. About a week ago my debugger began no longer stopping on breakpoints in the client application. It does stop on the server app.
At the same time this problem started, I noticed that when I started a debug session it started opening a new tab rather than a new window in Edge; not sure if this is related.
A few points:
Been searching and finding little things to try here and there, but nothing has made a difference.
I can't think of any changes I have made to the environment, etc.
Hoping for some kind of guidance.
Upvotes: 2
Views: 2187
Reputation: 21
I am late on this. But, I just had the same issue and fixed adding this "nativeDebugging": true
to my LauchSettings.json. It looks like this:
"Dev": {
"commandName": "Project",
"launchBrowser": true,
"environmentVariables": {
"ASPNETCORE_ENVIRONMENT": "Development"
},
"dotnetRunMessages": true,
"applicationUrl": "https://localhost:6003;http://localhost:6002;",
"nativeDebugging": true
},
Upvotes: 1
Reputation: 211
Thank you BP and MM for your help.
The problem ended up being in the LaunchSettings.json file on the server app. It was missing the line:
"inspectUri": "{wsProtocol}://{url.hostname}:{url.port}/_framework/debug/ws-proxy?browser={browserInspectUri}",
I have never updated this file and can only assume that it was there before because I have been debugging successfully for quite awhile. I have not upgraded from 5 => 6.
While I don't know the root cause, it is now working. Thanks again.
Upvotes: 5