Sdk: Should we make dotnet restore do a transitive restore for P2P references?
For instance, when we have project A depend on project B and we do a dotnet restore on A, should it also automatically do a restore on B.
livarcocc
All 4 comments
@livarcocc what happens if B depends on C? Go until there are no more P2P references?
blackdwarf
on 9 Feb 2016
This would be nice. It's a little awkward that build will try and build transitive projects, but restore won't restore them.
bricelam
on 9 Feb 2016
We need this. Once you get to real projects not using VS, it turns into a real mess. I'm trying to integrate the CLI into a build system right now. There are many different sets of .NET Core projects in it. The only way I can be sure that everything is restored before any individual piece tries to build is to jam a restore from the root before anything else happens. I'd really like to see either this or dotnet/cli#1742 very soon.
billwert
on 31 May 2016
Please move this issue to nuget/home
TheRealPiotrP
on 28 Jul 2016
Related issues
ulrichb
路
3Comments
pranavkm
路
3Comments
thomaslevesque
路
3Comments
davkean
路
3Comments
fmorriso
路
3Comments
Most helpful comment
We need this. Once you get to real projects not using VS, it turns into a real mess. I'm trying to integrate the CLI into a build system right now. There are many different sets of .NET Core projects in it. The only way I can be sure that everything is restored before any individual piece tries to build is to jam a restore from the root before anything else happens. I'd really like to see either this or dotnet/cli#1742 very soon.