From: Rob V. <rv...@do...> - 2014-04-09 13:23:07
|
Hi All So the discussions in the last week or two about issues with NuGet dependency conflicts involving Json.Net highlights that our choice of .Net profiles is somewhat behind the times. The Json.Net folks have moved to only supporting standard .Net plus PCL I.e. they¹ve dropped Windows Phone and Silverlight specific builds The problem for us is this means we can¹t upgrade dependencies for our Windows Phone and Silverlight builds so first question is should we drop those builds entirely? Particularly since we¹re targeting deprecated versions of those platforms (Windows Phone 7) in some cases. The next problem is that our PCL build targets an older PCL profile that no longer aligns with Json.Net so we can¹t upgrade dependencies for that build either currently. So the second question is should we update our PCL profile to align with more recent profiles? For reference the current Json.Net builds support the following PCL profiles: * portable-net40+sl5+wp80+win8+monotouch+monoandroid * portable-net45+wp80+win8 Would there be any objections to moving our PCL targets to align with these? Another longer term point, on the 1.9 branch I¹m already working on modularising the code so some of the new modules will no longer need to be Full Profile since they won¹t need anything not in Client Profile. Therefore I¹m also thinking we should start to only target Client Profile where possible which will require fewer builds to be maintained What do people think of these ideas? Cheers, Rob |