admin管理员组

文章数量:1315079

a library project which is using .NET framework 4.7 , the project file looks like

 <ItemGroup>
    <PackageReference Include="A" Version="1.0.0"/>
    <PackageReference Include="B" Version="4.0.0"/>
    <PackageReference Include="C" Version="2.0.0"/>
  </ItemGroup>

Here package A references 2.0.0 version of package B . Package C references 2.0.0 version of package B. After building the solution , the assembly information tool does not show 4.0.0 version of package B. The project still uses 2.0.0 version of package B.

In both Packages A and C, Package B is referenced like this .

<Reference Include="B, Version=2.0.0.0, Culture=neutral, PublicKeyToken=852c01e1b0b6deeb, processorArchitecture=MSIL">
      <Private>True</Private>
      <HintPath>packages\B.2.0.0\lib\net20\B.dll</HintPath>
</Reference>

We can't update Package A and Package C.
We tried using bindingRedirect but that did not work .

What changes can be done in this project file so that the dll only references 4.0.0 version of package B?

本文标签： vbnetHow to exclude a particular transitive dependency (dll) in NET frameworkStack Overflow

版权声明：本文标题：vb.net - How to exclude a particular transitive dependency (dll) in .NET framework - Stack Overflow 内容由网友自发贡献，该文观点仅代表作者本人， 转载请联系作者并注明出处：http://www.betaflare.com/web/1741971016a2407838.html， 本站仅提供信息存储空间服务，不拥有所有权，不承担相关法律责任。如发现本站有涉嫌抄袭侵权/违法违规的内容，一经查实，本站将立刻删除。