We work on a lot of different programs, and for all of them we created common helper and core projects, providing core and helping functionality for our programs. We have these projects for Portable, .NET and Silverlight projects. Now when we extend
one of these projects it easily gets confusing and messy to upgrade the used assemblies in our programs.

So I thought it would be nice wrap these helper and core assemblies into private NuGet packages, simply running an update-command whereever needed. I'd even go so far to immediately create and publish a new package on TFS checkin. Using only seperate .NET
and Silverlight packages is not an option, because in our main projects we also use portable projects to share code and data-objects with .NET (web service) and Silverlight.

So what I'm missing in nuget is the possibility to create nuget packages from Portable projects, and install these packages to other portable projects. Not sure whether the second works already (I didn't test), as I failed with the first task already.

I believe this can be rather difficult with the many different combinations you can have in portable projects. Perhaps an option would be to start with the lowest shared subset for the most common used platforms (.NET, Silverlight, WP).

I have good news for you. Portable library support will go into 2.1, which is slated to be released in late September.

And it will support both of your tasks, meaning a package containing portable assemblies can be installed into a portable project, as well as a normal project if the project is supported by the portable assemblies.

I was thinking of testing out the new PCL support but I had a few questions first. #1 how does this affect nuget pack command? Is their a new pcl folder or something different?

Also how does this work with two projects that have an incompatible set of supported runtimes selected? Say I have PCL library A that as part of it's targets, targets the Xbox 360 but then I have PCL library B that only targets .NET 4.5 apps and windows
store apps. Now I try to add a nuget reference to project B from project A. I'm assuming this will not be allowed.

Now for a slightly more complicated situation. Say I have two versions of project A both portable libraries. One includes support for Xbox 360 and one does not. So Project A with 360 support, and Project A without 360 support.
Can these be packed together in one package or can a package just have a single pcl version? IF they can be packaged together when adding a reference how will nuget choose which one to select?

(Note that in the current build, we haven't supported Xbox yet. We are considering adding it.)

For your first scenario, you're right. The package will not be installed into the project.

For the second scenario, you can include both versions in one package. Just use the folder format as described above, one with Xbox and one without. However, as I said, NuGet doesn't recognize the Xbox moniker yet, so the folder will be treated as invalid.

I'm not that experienced in creating nuget packages yet.. But is it right that I can't create packages with the Visual Studio Extension, and need the command line program? If I'm wrong, please explain (and extend the docs) how to do it using the extensions.
Else please suply a link to the nightly build for the command line program. :)