Sharing packages between multiple solutions...

Jan 27, 2012 at 6:17 PM


Is there a standard way to share packages between multiple solutions in my enlistment?

Or do I always need to have a “all.sln” that contain all the projects in my enlistment?

One idea I had was – can you please let me know the short comings with this?

-          Have one solution in my enlistment called “nugetpackage.sln”

-          Adding all packages to that – and manage updates etc. using that?

-          Individual projects just refer to the package binaries by path.



Jan 27, 2012 at 6:29 PM

There is no great way to share packages today. However, note that is you use the package restore workflow, no packages go in your source control, so the only harm in having multiple Packages folders is that it takes a bit more disk space on the dev machine. But the repo stays clean.

The shortcoming of your idea is that package installation often does more than just add assembly references (static content, xml transforms, powershell scripts). So if you just add the binary references, you'd miss out on that.