Respect ReferenceOutputAssembly when packing a CSPROJ

[chandramouleswaran]

Hi,

Today all project references of a CSPROJ file are added to the package if nuget pack is called with -IncludeReferencedProject.

There are many real life production scenario where we have project references only to control build order - we use False to control the same.

We need a way in ProjectFactory.cs to also look at this metadata before including the output of the referenced project to the package.

https://github.com/NuGet/NuGet.PackageManagement/blob/3d6cf88131280c789d81f543b33df40421ad7e5b/src/NuGet.CommandLine/Commands/ProjectFactory.cs

Thanks
Chandra

[yishaigalatzer]

@chandramouleswaran this is the first time I'm seeing project references used this way. I've used batch build before to control the build order.

The simple answer for this kind of question is: Use a nuspec based packing. .csproj packing is a very limited feature, and our investment in it come at a low priority.

We would consider a pull request of course (code, test & docs).

[deepakaravindr]

Fixed with NuGet/NuGet.Client@f0cde66
and NuGet/NuGet.Client@c3cee71