提交 a3add60f 编写于 作者: J Jared Parsons

Fix MS.VB reference

The TPA now considers the output directory as a trusted place for
loading assemblies. To the point it will prefer certain DLLs in the
output directory over equal ones that ship with the runtime.

This broke a number of VB tests here because we unconditionally
referenced the desktop version of Microsoft.VisualBasic. This got copied
to the output directory, included in the TPA and hence loaded during
test execution. This breaks tests because they require the .NET Core
version of Microsoft.VisualBasic.

Conditioned the reference to be desktop only so it's not present on our
.NET Core builds
上级 72b58c94
......@@ -22,7 +22,7 @@
</ItemGroup>
<ItemGroup>
<PackageReference Include="Microsoft.DiaSymReader" Version="$(MicrosoftDiaSymReaderVersion)" />
<PackageReference Include="Microsoft.VisualBasic" Version="$(MicrosoftVisualBasicVersion)" />
<PackageReference Include="Microsoft.VisualBasic" Version="$(MicrosoftVisualBasicVersion)" Condition="'$(TargetFramework)' == 'net472'" />
</ItemGroup>
<ItemGroup>
<Compile Update="Resource.Designer.vb">
......
Markdown is supported
0% .
You are about to add 0 people to the discussion. Proceed with caution.
先完成此消息的编辑!
想要评论请 注册