[BUG] Pressing the restart icon during a debugging session for a c# test fails with an error

[asilverman]

Describe the Issue

In the screen recording below I am running a test in debug mode, I step through the test and then decide to restart the test, however the operation fails an VSCode says it couldn't find the process id
https://github.com/microsoft/vscode-dotnettools/assets/9611108/1f6ffbf2-ea4b-4bd9-932e-21817f4f0909

Steps To Reproduce

1. Clone azure/bicep git repo
2. run any test in debug from the test explorer
3. press the restart debugger button

Expected Behavior

I would expect the test to restart and run again, breaking in the first breakpoint. It instead fails with an error message

Environment Information

• OS: MacOS
• ms-dotnettools.csdevkit version: v1.4.2

[WardenGnaw]

The restart button will just relaunch with the same launch.json configuration provided. There needs to be a change in the test code to attach to the correct PID on restart.

[github-actions]

This issue has been marked as stale after 14 days of inactivity. @[ @ @], could you please take a look?

[asilverman]

I would love to hear back on this

[peterwald]

This is currently not supported in C# Dev Kit. We are evaluating whether to add restart functionality in a future release.

[asilverman]

Ok, that is acceptable. I hope it's not too much trouble to add it

[asilverman]

Hi @ocallesp, @peterwald any update on this bug?

[peterwald]

It's on our radar, but unfortunately no updates to report at this time.

[asilverman]

Hi @peterwald, it's been many months since I am experiencing this issue and would really appreciate if you can assist, it seems odd to me that this generally available feature for other languages simply doesn't work in C#

[AbhitejJohn]

@asilverman : We sadly have not been able to prioritize enhancements similar to this on Test Explorer given few other priorities(reliability in particular in the Test Explorer space). However, if we do hear back from more customers that this is required, we'd be happy to re-prioritize. At the moment, this is on our backlog and we'll pull it into one of the active milestones if this surfaces higher as a priority.