Add option to not share .NET Framework testhosts - #5018
Merged
Conversation
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Adds runsettings option to disable sharing testhosts:
and ENV:
This is useful when solution is using both MSTest v2 and MSTest v3 and would like to run each project in isolated process even when they are not running in parallel, or not disabling appdomains. Otherwise the extension logic will send both extension dlls to the host for initialization and it will fail to find the extension and to run the tests.
This option only affects .NET Framework test projects that don't enable parallelization, or don't disable app domains. Such projects are sharing host, others are not.
Adds option to skip default adapters (the extensions that are place in Extensions folder in our VisualStudio folder).
This allows projects to run even if external extensions (such as Chutzpah) add dependencies that are incompatible with the projects. Without this option all extensions from the built in folder are always included in the run.
Fix #3475