RunVSTest: Allow overriding the ToolExe/ToolPath #548
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.
The
ToolTask
has built-in parameters forToolExe
/ToolPath
which allow callers to override the tool being called. This lights those up for theRunVSTestTask
There's also a minor change to avoid using an undefined
%VSINSTALLDIR%
and instead fallback to looking in thePATH
(behavior when returning a filename fromGenerateFullPathToTool
).Reference to relevant
ToolTask
logic: https://github.com/dotnet/msbuild/blob/7ca3c98fad986066bbf2802c863236b4a0f4e34a/src/Utilities/ToolTask.cs#L503-L566