Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Dependencies node should respect DisableTransitiveProjectReferences

See original GitHub issue

When a project sets property DisableTransitiveProjectReferences to true, the dependencies node should not display transitive project references.

Current

App.csproj

<PropertyGroup>
  <TargetFramework>netcoreapp3.1</TargetFramework>
  <DisableTransitiveProjectReferences>true</DisableTransitiveProjectReferences>
</PropertyGroup>
<ItemGroup>
  <ProjectReference Include="..\ClassLibrary1\ClassLibrary1.csproj" />
</ItemGroup>

ClassLibrary1.csproj

<ItemGroup>
  <ProjectReference Include="..\ClassLibrary2\ClassLibrary2.csproj" />
</ItemGroup>

App’s Dependencies Tree

Expected

ClassLibrary2 does not appear as a child dependency of ClassLibrary1 in the App project.

Issue Analytics

State:
Created 4 years ago
Reactions:1
Comments:10 (9 by maintainers)

Top GitHub Comments

2reactions

pzwaracommented, Jun 5, 2020

I would like to use DisableTransitiveProjectReferences to hide implementation\project references\nugets from referenced project and that the dependency of dependency won’t be shown by intellisense in VS. Wasn’t this flag made for it?

By using PrivateAssets = "All" I have System.IO.FileNotFoundException exceptions, because dll’s are not copied. So how can I separate / hide implementation details between different layers of application?

0reactions

drewnoakescommented, May 1, 2020

The tree shows what’s in the assets file. My understanding is that the assets file should not contain the transitively-referenced-project due to DisableTransitiveProjectReferences being true. If that’s so then the fix is to get the assets file to model this correctly, in which case the UI will update automatically.