Building project with twice (or more) transitive dependencies explodes.

[NTaylorMullen]

Repro

Given the following setup: Project1 => Project2 => Project3.

When you restore Project1 you get an entry for Project2 and Project3 in the assets.json file. However, when you build Project1 Project3 is never passed to csc.

Trying restoring/building the following: TransitiveCSCRepro.zip

dotnet info:

.NET Command Line Tools (1.0.0-preview3-004007)

Product Information:
 Version:            1.0.0-preview3-004007
 Commit SHA-1 hash:  80ec02b4da

Runtime Environment:
 OS Name:     Windows
 OS Version:  10.0.14393
 OS Platform: Windows
 RID:         win10-x64

SDK: 1.0.0-alpha-20161029-1

[dsplaisted]

I think I recall that this is the intended behavior. You will get transitive project references in the output folder, but only direct project references get passed to the compiler.

[srivatsn]

Isn't this just dotnet/project-system#199 - that we don't support transitive project references yet.

[NTaylorMullen]

So NuGet handles this correctly (updates the assets.json). The bits that are left is letting MSBuild bits (this issue) and the UI work to show the inherited dependencies. Unless I'm missing something dotnet/project-system#199 would still require work in this repo to be done.

This issue ends up also being a dotnet pack problem as well.

[nguerrera]

Closing as dup of #200