You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I don't really want paths to global tools in my launchSettings.json; I think this is just bad practice and also makes it difficult to support cross platform run configurations. I have the below launchSettings.json which works fine when I run it from Rider:
However, I'm not able to hit breakpoints when I launch this run configuration from Jetbrains Rider using Debug mode. Is there some way I can use the dotnet CLI tool to kick off the test tool but still be able to attach to it for debugging breakpoints?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I don't really want paths to global tools in my
launchSettings.json
; I think this is just bad practice and also makes it difficult to support cross platform run configurations. I have the belowlaunchSettings.json
which works fine when I run it from Rider:However, I'm not able to hit breakpoints when I launch this run configuration from Jetbrains Rider using Debug mode. Is there some way I can use the
dotnet
CLI tool to kick off the test tool but still be able to attach to it for debugging breakpoints?Thanks in advance.
Beta Was this translation helpful? Give feedback.
All reactions