The best approach is to create NuGet's dependency on a specified project.
Suppose you have two projects in your solution:
Solution | ProjectA | ProjectB
ProjectA has a link to ProjectB, and both are NuGet packages (both have nuspec files). If you want to create a ProjectA package that depends on ProjectB, run in the root of ProjectA:
NuGet Pack -IncludeReferencedProjects
Given IncludeReferencedProjects, NuGet will traverse related projects inside the solution, looking for nuspec files (this means that the project is a package). If nuspec, if found, it is added as a dependency.
In this example, he will find the nuspec file in ProjectB and add it as a dependency. When you install ProjectA, ProjectB will also be installed, and it will be added as a link.
source share