From d3efddae527c016e586d3510e9c08d0d86eea262 Mon Sep 17 00:00:00 2001
From: matthew-peacock <matthew.peacock@whiteoakam.com>
Date: Wed, 30 Mar 2016 14:37:47 +1100
Subject: [PATCH] Fix indirect dependencies on native dlls

Suppose Lib1 is a C# proejct uses the NuGet package containing the native dll, and Lib2 depends on Lib1, and finally Lib3 depends on Lib2.  With the current setup, the native dlls will be copied into the output directory of both Lib1 and Lib2, but not Lib3.  Using 'None' instead of 'Content' fixes this.

I don't have a reference for this behaviour, but I have replicated it with three dummy projects to be sure.  I originally got the hint from Benoit Blanchon's comment at http://stackoverflow.com/questions/19478775/
---
 build/NativeProvider.targets | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/build/NativeProvider.targets b/build/NativeProvider.targets
index 6ebd5cd3..d32847dc 100644
--- a/build/NativeProvider.targets
+++ b/build/NativeProvider.targets
@@ -7,9 +7,9 @@
   <ItemGroup Condition="'$(MSBuildThisFileDirectory)' != '' And HasTrailingSlash('$(MSBuildThisFileDirectory)')">
     <MathNetInteropFiles Include="$(MSBuildThisFileDirectory)**\*.dll" />
     <MathNetInteropFiles Include="$(MSBuildThisFileDirectory)**\*.so" />
-    <Content Include="@(MathNetInteropFiles)">
+    <None Include="@(MathNetInteropFiles)">
       <Link>%(RecursiveDir)%(FileName)%(Extension)</Link>
       <CopyToOutputDirectory>PreserveNewest</CopyToOutputDirectory>
-    </Content>
+    </None>
   </ItemGroup>
 </Project>