From 9f6c9e8bd0b280317a87542016b45651500bcecb Mon Sep 17 00:00:00 2001
From: Eric Erhardt <eric.erhardt@microsoft.com>
Date: Tue, 19 Mar 2019 08:53:29 -0500
Subject: [PATCH] Updating the FunctionalTests to clearly explain why they are
 not strong named signed.

---
 .../Microsoft.ML.Functional.Tests.csproj                     | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/test/Microsoft.ML.Functional.Tests/Microsoft.ML.Functional.Tests.csproj b/test/Microsoft.ML.Functional.Tests/Microsoft.ML.Functional.Tests.csproj
index 88c51526af..c1c7af9263 100644
--- a/test/Microsoft.ML.Functional.Tests/Microsoft.ML.Functional.Tests.csproj
+++ b/test/Microsoft.ML.Functional.Tests/Microsoft.ML.Functional.Tests.csproj
@@ -1,8 +1,9 @@
 <Project Sdk="Microsoft.NET.Sdk">
 
   <PropertyGroup>
-    <!-- We are turning off strong naming to ensure we never add `InternalsVisibleTo` for these tests -->
-    <SignAssembly>true</SignAssembly>
+    <!-- DON'T CHANGE THIS!!! We are turning off strong naming to ensure we never add `InternalsVisibleTo` for these tests -->
+    <SignAssembly>false</SignAssembly>
+    <!-- DON'T CHANGE THIS!!! We are turning off strong naming to ensure we never add `InternalsVisibleTo` for these tests -->
     <PublicSign>false</PublicSign>
   </PropertyGroup>