From 887834df6eb9574e81141ab01cd4d29961dc48f3 Mon Sep 17 00:00:00 2001
From: David Kean <davkean@microsoft.com>
Date: Tue, 8 Mar 2016 20:33:13 -0800
Subject: [PATCH] Turn off hard-linking during the build

We turned on hard-linking to reduce copy and build time, however,
this would result in behavior where copying a NuGet binary from .nuget/packages to the output directly which was then subsequently overwritten with a different version would result in the .nuget\packages folder to be corrupted because they were now linked.
---
 build/Targets/Settings.targets | 3 ---
 1 file changed, 3 deletions(-)

diff --git a/build/Targets/Settings.targets b/build/Targets/Settings.targets
index f02b3b68e3d..6d0753e3efe 100644
--- a/build/Targets/Settings.targets
+++ b/build/Targets/Settings.targets
@@ -16,9 +16,6 @@
         is specified on the command line of MSBuild
     -->
     <BaseNuGetRuntimeIdentifier Condition="'$(OS)' == 'Windows_NT'">win7</BaseNuGetRuntimeIdentifier>
-
-    <!-- Turn on hard-linking on Windows to reduce copy time and disk space -->
-    <CreateHardLinksForCopyLocalIfPossible Condition="'$(OS)' == 'Windows_NT'">true</CreateHardLinksForCopyLocalIfPossible>
   </PropertyGroup>
 
   <!-- Import the global NuGet packages -->
-- 
GitLab