P2P references should be transitive

Example: Consider the below dependency chain ProjectA-> ProjectB->ProjectC

Here ProjectA depends on ProjectC but build fails with error

C:\Users\sridhper\.nuget\packages\microsoft.netcore.sdk\1.0.0-alpha-20160923-4\build\netstandard1.0\Microsoft.PackageDependencyResolution.targets(142,5): error : Unexpected Dependency D:\github\tryout\TestAppDependencyGraph \ProjectC\ProjectC.csproj with no version number [D:\github\tryout\TestAppDependencyGraph\ProjectA\ProjectA.csproj]

Point of failure is here

cc @eerhardt

[jez9999]

@dasMulli Still, using something like that at unit test time doesn’t stop undesirable interfaces from showing up in IntelliSense at design time. I know I might seem a bit fussy, but if I’m working in my presentation layer, VS shouldn’t be offering me an autocomplete of IFooRepo when I only want my presentation layer to access that repository through IFooService, at least in an ideal world.

[dasMulli]

Ah looks doable now by removing the correspending ReferencePathWithRefAssemblies item in e.g. before BeforeCompile. I may have mixed it up with transitive nuget references for which there initially was no ““easy”” way to remove the reference but keep the copy-local behavior.