The ToolTask has built-in parameters for ToolExe/ToolPath which allow callers to override the tool being called. This lights those up for the RunVSTestTask
There's also a minor change to avoid using an undefined %VSINSTALLDIR% and instead fallback to looking in the PATH (behavior when returning a filename from GenerateFullPathToTool).
The
ToolTaskhas built-in parameters forToolExe/ToolPathwhich allow callers to override the tool being called. This lights those up for theRunVSTestTaskThere'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
ToolTasklogic: https://github.com/dotnet/msbuild/blob/7ca3c98fad986066bbf2802c863236b4a0f4e34a/src/Utilities/ToolTask.cs#L503-L566