Fix testing of libraries projects in the vscode

[Anipik]

#34025 fixes the intellisense and gives the option to user to run the an individual test or group of tests

Currently on running the test it just hangs, It could be that coreclr is build in debug mode. It would be nice to have this thing working in vscode. It may also make the debugging easier on linux machine.

cc @ViktorHofer @ericstj @danmosemsft @safern

[ViktorHofer]

Running tests in VS is not yet possible. This isn't related to a runtime configuration mismatch but due to how VSTest invokes the testhost.

[safern]

This isn't related to a runtime configuration mismatch but due to how VSTest invokes the testhost.

I guess we would need to open vscode with some environment variables just like we do for VS? I'm just wondering, I think the best is to just wait for this to land when we move to VSTest with the new features you worked with them.

[ViktorHofer]

@ManickaP do you know if testing dotnet/runtime libraries inside VSCode does already work? I never tried it out myself.

[ManickaP]

If you mean via "Test Explorer" then no, that never worked for me. I run tests from command line and if I need to debug them I use this: https://github.com/dotnet/runtime/blob/main/docs/workflow/debugging/libraries/debugging-vscode.md

[ViktorHofer]

Thanks @ManickaP. Unfortunately I don't know what this issue was originally tracking. VSCode doesn't have an in-built test explorer and dotnet test from the integrated terminal works just fine.

[ghost]

This issue has been marked needs-author-action and may be missing some important information.

[ghost]

This issue has been automatically marked no-recent-activity because it has not had any activity for 14 days. It will be closed if no further activity occurs within 14 more days. Any new comment (by anyone, not necessarily the author) will remove no-recent-activity.

[ghost]

This issue will now be closed since it had been marked no-recent-activity but received no further activity in the past 14 days. It is still possible to reopen or comment on the issue, but please note that the issue will be locked if it remains inactive for another 30 days.