Merged
Conversation
Member
Author
|
As soon as VS Test Explorer and dotnet test is enabled and property names are refined, I plan to write a doc with possible switches for the env var section & CLI global properties. |
Member
Author
|
Merging meanwhile to unblock some of my work. |
ViktorHofer
added a commit
to ViktorHofer/arcade
that referenced
this pull request
Jul 8, 2019
This reverts commit 4953cdf.
ViktorHofer
added a commit
that referenced
this pull request
Jul 8, 2019
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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.
The benefit of having launchsettings files isn't existent anymore. Instead we can rely on the environment variables feature in the VS Debugging section (which will simply generate a launchsettings.json file) and have the same behavior on CLI and inside VS.
I'm not porting the
-parallel noneswitch over from the template json file as the equivalentXUnitMaxThreadssetting is available which can be set as env var in the Debug section. Reason for that is that with that switch F5 is far slower than running from the console and for debugging purposes VS Test Explorer is possible now.