Provide option in Nuget pack command to add project dependencies as "dependents"


W.r.t the query @ http://stackoverflow.com/questions/13389597/creating-nuget-package-with-project-referencies

Scenario :
Consider a solution representing a library which is organized as three projects : Project A , B and C. A has "project" dependency on B and C.
If user has to package this, he has to build packages for project B and C. Then add B and C as dependents in A's nuspec file.
Instead how about providing a "-PackDependencies" switch to "pack" command which would automatically take care of this scenario ?
Closed Aug 12, 2013 at 9:49 PM by dotnetjunky
We have implemented this feature with the -IncludeReferencedProject switch


broggeri wrote Nov 23, 2012 at 10:26 AM

Or, make it easier to pack multiple csproj in one nupkg.

something like "nuget pack <solution>" comes to mind.

broggeri wrote Nov 23, 2012 at 11:28 AM

To come back to the original proposal, it would be best if this could work without even requiring a switch.
However one would have to come up with a way to clearly identify that the referenced project really produces a nuget package.

broggeri wrote Nov 23, 2012 at 11:31 AM

Sorry, scratch that last comment, I misunderstood the original proposal.

My first comment about 'nuget pack solution' still stands though.

JeffHandley wrote Jan 23, 2013 at 10:16 PM

Triage: Doesn't meet the bar for 2.3, but we will review it again during the NuGet 2.4 planning.