From 03dd0bae0a6f91cf4c3f09dee11eab99156699aa Mon Sep 17 00:00:00 2001
From: Matt Mitchell <mmitche@microsoft.com>
Date: Wed, 7 Mar 2018 18:22:20 -0800
Subject: [PATCH] Workaround coreclr issue (#16828)

VSTS does not seem to be correctly honoring the working directory for batch script steps.  Explicitly qualify the setup_vs_env.cmd path
---
 buildpipeline/DotNet-Trusted-Publish.json | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/buildpipeline/DotNet-Trusted-Publish.json b/buildpipeline/DotNet-Trusted-Publish.json
index 32014cf6b2..3eca08ae29 100644
--- a/buildpipeline/DotNet-Trusted-Publish.json
+++ b/buildpipeline/DotNet-Trusted-Publish.json
@@ -79,10 +79,10 @@
         "definitionType": "task"
       },
       "inputs": {
-        "filename": "setup_vs_tools.cmd",
+        "filename": "$(Pipeline.SourcesDirectory)\\setup_vs_tools.cmd",
         "arguments": "",
         "modifyEnvironment": "true",
-        "workingFolder": "$(Pipeline.SourcesDirectory)",
+        "workingFolder": "",
         "failOnStandardError": "false"
       }
     },
@@ -758,4 +758,4 @@
     "revision": 418098432,
     "visibility": "organization"
   }
-}
\ No newline at end of file
+}
-- 
2.34.1