How does DNU RESTORE determine whether a dependency is a project reference and not a package reference?

Question

I force my panties to spin links to the “project” compared to the package package (for example, Nuget) in asp.net 5.0. I would really like someone to explain in more detail how links are provided in asp.net 5.0. How does “restore dnu" determine if something is a project reference, not a package reference?

I thought that the link would be drawn into the project if the projects are in the same directory, but this is clearly not the whole story. It looks like you can have a deeper nesting of directories and still get a link to the project.

Here is a diagram of my overall project structure:

I have a set of projects, some of which reference each other. There are libraries called TextHelpers and MathHelpers and a project called MainProject. Libraries live in the Libraries folder, and MainProject lives in the Tools folder. This separation is necessary because libraries and tools belong to different Git repositories:

• Root / Libraries / TextHelpers.Project1 - version 1.0.0 - *
• Root / Libraries / TextHelpers.Project2 - version 1.0.0 - *
• Root / Libraries / MathHelpers.Project1 - version 1.0.0 - *
• Root / Libraries / MathHelpers.Project2 - version 1.0.0 - *
• Root / Tools / MainProject - version 1.0.0 - *

Typically, MainProject refers to libraries as Nuget packages from the Nuget private repository (only for a folder in the file system) that serves the libraries.

MainProject , Nuget. () , () Nuget. ?

: global.json, " dnu" project.lock.json "project", "package". ?

Answer 1

dnu dnx :

• , ( , project.json ). . repo/src/project1/project.json, repo/src
• , global.json

: , , , , .

,

src/P1/project.json
src/System.Collections/project.json

src/P1/project.json System.Collections, src/System.Collection NuGet System.Collections. .

:

• global.json, , . test/T1/project.json, src global.json, src System.Collections , T1 ( ).
• , , . , . , .
• , .

, .

: dotnet ( dnx) , , .