Workaround "2.0" publish bug when referencing "1.1" security assemblies.

This hack downgrades the security assemblies to "1.0" versions, so the assets are excluded.  When the underlying bug is fixed (or Roslyn moves to "2.0") we can remove this hack.

See https://github.com/dotnet/standard/issues/191.
This commit is contained in:
Eric Erhardt 2017-02-02 10:25:03 -06:00
parent 68015b6bec
commit 3f3443d2df

View file

@ -5,7 +5,7 @@
<PropertyGroup>
<VersionPrefix>$(CliVersionPrefix)</VersionPrefix>
<TargetFramework>netcoreapp2.0</TargetFramework>
<RuntimeFrameworkVersion>$(CLI_SharedFrameworkVersion)</RuntimeFrameworkVersion>
<RuntimeFrameworkVersion>$(CLI_SharedFrameworkVersion)</RuntimeFrameworkVersion>
<GenerateRuntimeConfigurationFiles>true</GenerateRuntimeConfigurationFiles>
</PropertyGroup>
<ItemGroup>
@ -14,6 +14,12 @@
<PackageReference Include="Microsoft.CodeAnalysis.Build.Tasks" Version="$(CLI_Roslyn_Version)" />
<PackageReference Include="Microsoft.Net.Compilers.netcore" Version="$(CLI_Roslyn_Version)" />
<PackageReference Include="Microsoft.DiaSymReader.Native" Version="1.4.0" />
<!-- workaround for https://github.com/dotnet/standard/issues/191 so OpenSsl native assets aren't published -->
<PackageReference Include="System.Security.Cryptography.Algorithms" Version="4.2.0" />
<PackageReference Include="System.Security.Cryptography.Encoding" Version="4.0.0" />
<PackageReference Include="System.Security.Cryptography.OpenSsl" Version="4.0.0" />
<PackageReference Include="System.Security.Cryptography.X509Certificates" Version="4.1.0" />
</ItemGroup>
<ItemGroup>