Enable native debugging for vstest.console #10401
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
With environment variable
VSTEST_HOST_NATIVE_DEBUG
, we can use a native debugger to debug tests but it requires--InIsolation
flag.When using the argument
--tests:
to run a specific test, testhost.exe is spawned twice and we must attach twice to properly debug.When the environment variable
VSTEST_RUNNER_DEBUG
is set, vstest.console only waits for a managed debugger.I propose to add new environment variable
VSTEST_RUNNER_NATIVE_DEBUG
to enable native debugging of vstest.conssole.This will enable native debugging of tests without the
--InIsolation
flag.Related issue
Fixes #10393