Open austin-owensby opened 10 months ago
After doing a bit of research, the first debug session I stop has a type of coreclr
and the 2nd is dotnetwatchattach
After doing a bit of research, the first debug session I stop has a type of
coreclr
and the 2nd isdotnetwatchattach
This is probably due to a change in vscode - the UI now probably selects the child process that watch attach creates and makes you manipulate that instead of the (intended) parent process.
I am currently very busy but if you manage to figure out how to fix it I am open to PR's :)
Just chirping in here: I also encounter this problem, additionally, every rebuild triggered through watch freezes the VSCode UI for about 30s, sometimes longer.
I have unfortunately no clue how to debug a VSCode extension, nor a setup. If someone knows of a good tutorial, I'd be open to give debugging and PR'ing a shot.
When I run the the extension everything works fine, but when I'm ready to stop I have to click the stop button twice before it actually stops.
dotnet-watch-attach-sample
repo and got the same behavior using only the necessary extensions:Environment:
Let me know if there's anything else I need to provide you to help look into this. If I have time I'll try and take a look at the source code myself.
Watch Attach output when starting:
Terminal output when starting:
Watch Attach output after first stop:
Terminal output after first stop:
Watch Attach output after second stop: