From 3e714b8b1efe68c693469b6cab7883ff8a1b51d8 Mon Sep 17 00:00:00 2001
From: Tarek Mahmoud Sayed <tarekms@microsoft.com>
Date: Fri, 1 Jul 2016 09:44:44 -0700
Subject: Support filtering to TestTFM
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

This change is to support filtering according to the TestTFM. e.g. can do
     “build.cmd /p:FilterToTestTFM=net46”
The change here is splitting the Build phase from the Test phase in dir.traversal.targets
so we don’t have to rebuild the test assemblies when passing TestTFM property to run the test.

Now if FilterToTestTFM is not specified, we default running the tests as netcoreapp1.0
so when issuing “build.cmd/sh” Command without passing FilterToTestTFM, it will
filter the tests to netcoreapp1.0 and run those tests.
I have enabled one of the test projects System.AppContext.Tests to support net46
as example, next step will be Enabling the rest of all projects to run against all
platforms (net46, net461, net462, netcore50 and netcore50aot)
---
 dir.targets | 12 ++++++++++++
 1 file changed, 12 insertions(+)

(limited to 'dir.targets')

diff --git a/dir.targets b/dir.targets
index 87ba4ae6f6..6b16e9886d 100644
--- a/dir.targets
+++ b/dir.targets
@@ -17,6 +17,18 @@
   <Target Name="GenerateTestProjectJson" />
   <Target Name="GenerateAllTestProjectJsons" />
 
+  <Target Name="UndefineTestTFM" BeforeTargets="AssignProjectConfiguration">
+    <ItemGroup>
+      <ProjectReference>
+        <!-- 
+        Always undefine TestTFM and FilterToTestTFM for all project reference as not needed for compilation and
+        avoid bin clash tool to fail
+        -->
+        <UndefineProperties>%(ProjectReference.UndefineProperties);TestTFM;FilterToTestTFM</UndefineProperties>
+      </ProjectReference>
+    </ItemGroup>
+  </Target>
+
   <Import Project="$(ToolsDir)/Build.Common.targets" Condition="Exists('$(ToolsDir)/Build.Common.targets')" />
 
   <!-- permit a wrapping build system to contribute targets to this build -->
-- 
cgit v1.2.3