Updating Portable Class Library question

Topics: General
Feb 27, 2013 at 12:41 AM

So I have a portable class library for Json.NET 4.5.11 for these frameworks:

I am thinking of updating Json.NET to 5.0.0 and the PLC project to something like:

My question is will NuGet successfully direct people who don't have a .NET 4.5 project or people who are using Silverlight to the old PCL in 4.5.11 or would I need to maintain two PCL projects?

~ J
Feb 27, 2013 at 3:26 AM
No, NuGet doesn't automatically direct people to the old PCL.

What is your actual goal? Do you still want to support Silverlight in your new 5.0.0 version?
Feb 28, 2013 at 12:31 AM
I want to balance possibly disrupting some people vs maintaining too many projects. What is your advice?
Feb 28, 2013 at 12:44 AM
You can put the old Silverlight .dll into a separate Silverlight folder in your new package.
Feb 28, 2013 at 1:05 AM
I'm not a fan of having old versions of a dll in a package but I already have a separate Silverlight 5 project (and WP project).

Am I right that the only people updating the portable dll will effect will be people who have created their own PCL and are targeting older frameworks than my new PCL supports?
Feb 28, 2013 at 2:41 AM
I'm still not clear what are the frameworks that you are planning to support in the new version. Can you provide more details?
Feb 28, 2013 at 2:55 AM
Right now there is:

I considering making the next version:

Basically adding net45, upgrading windowsphone from 7 to 8 and upgrading the portable library.
Feb 28, 2013 at 3:07 AM
Thanks. Yes, you're right. If you want to continue to support the old PCL projects (with net40 and sl4), I'm afraid you will have to maintain two PCL projects.

NuGet is not smart enought to search for the "latest compatible" package.
Feb 28, 2013 at 3:11 AM
People with old PCL projects could just limit the NuGet package version, correct? i.e. 4 <= x < 5
Feb 28, 2013 at 3:16 AM
That's correct.