I have been using NuGet to manage my internally created builds for several months, and it works very well. I recently discovered "portable class libraries" that were also great until it was time to install the packages.
Say I have a PCL that is for .NET 4.5, SL5, and .NET for Windows Store apps. I run nuget spec to create a .nuspec file, edit the values, pack it and add .nupkg to our internal channel. If I open the .nupkg file in Package Explorer, I see one content folder under lib called portable-win + net45 + sl50.
When I try to install a package from any compatible project into another solution, I get the following message:
"Project.PCL" cannot be installed because it is not compatible with any project in the solution. The package is not intended for any frameworks. "
If I manually create .nupkg in Package Explorer, updating the version number, adding the lib folder for each target infrastructure (and not the portable folder) and adding the Project.PCL.dll file to each folder, I can add a package for compatible projects in the solution. But for this process, every time I want to update PCl, it's a little tedious (I created a small .cmd file in the project root folder to quickly pack and deploy).
Do other people have this problem? How can I pack PCL in the same way as other types of projects?
Note. I am using VS 2012 Ultimate and NuGet 2.2
source share