Use OS specific path for test result file
authorvitek-karas <vitek.karas@microsoft.com>
Wed, 11 Jul 2018 12:25:30 +0000 (05:25 -0700)
committervitek-karas <vitek.karas@microsoft.com>
Wed, 11 Jul 2018 12:25:30 +0000 (05:25 -0700)
This fixes a bug that we write out path with forward slashes even on windows. So the path can't be used as-is to open the result file in UI tools.

Commit migrated from https://github.com/dotnet/core-setup/commit/f410793e1673bfbedb288f4cdcc480bddc5af055

src/installer/test/dir.proj

index 274985d..bfcf521 100644 (file)
@@ -86,7 +86,7 @@
     <PropertyGroup>
       <TestArgs>--no-restore $(MSBuildPassThroughPropertyList)</TestArgs>
       <IsCrossArch Condition="'$(TargetArchitecture)' == 'arm' or '$(TargetArchitecture)' == 'arm64' or '$(TargetArchitecture)' == 'armel'">true</IsCrossArch>
-      <TestResultsXml>$(TestsOutputDir)$(TestProjectFilename)-testResults.trx</TestResultsXml>
+      <TestResultsXml>$(SystemPathTestsOutputDir)$(TestProjectFilename)-testResults.trx</TestResultsXml>
     </PropertyGroup>
     <Exec Command="$(DotnetToolCommand) test $(TestArgs) --logger &quot;trx;LogFileName=$(TestResultsXml)&quot;"
           WorkingDirectory="$(TestWorkingDirectory)"