Build package from multiple csproj

Apr 4, 2012 at 10:05 AM
Edited Apr 4, 2012 at 10:07 AM

One thing that would be nice is the ability to build a package from multiple project outputs. For instance if you have solution containing a 2 versions of the same library, one targeted at Silverlight and one at .Net it would be nice to be able to point to both csproj files and have Nuget figure it out.

The only problem I can see is choosing which one to create the metadata from.

Obviously I realise you can do this using <File> in the <nuspec> but one problem with that is the file path will need "Debug" or "Release" depending on the build so you need to substitute it (or have 2 files).

Apr 20, 2012 at 8:48 PM

I would find this usefull too.

What if the nuget pack command accepted a list of projects. It could then package all of these together. It should scan all of the projects for a nuspec file and use the first one it finds, and use metadata from the corresponding project. If there is no nuspec file it should just use the metadata from the first project in the list.

I've submitted a separate issue to deal with the basepath for files.