This project has moved and is read-only. For the latest updates, please go here.

PCL profiles are not targeting .NET 4; why?

Aug 4, 2014 at 2:13 PM
What is the rationale for using Profile 344 for the PCL project? This profile is for .NET 4.5 and higher, thus neither of the PCL libraries (profiles 344 and 47) can be consumed by another PCL library targeting .NET 4.

I have tried to switch to Profile 328 instead (supports the same targets as 344, except that it targets .NET 4 and higher). I have no problems building the project with this profile, and the unit tests in the associated test project pass even after having switched to profile 328.

Unless you have future plans for this library that prohibit re-targeting, do you think you could consider switching the 344 PCL project to profile 328 for the next release?

Many thanks in advance!
Anders @ Cureos
Aug 4, 2014 at 3:29 PM
Hi Anders,

This is most likely an oversight or small misunderstanding. The NuGet package itself contains a full .Net 4.0 build, so the PCL builds could certainly support it as well. It seems to me we could indeed replace 344 with 328 in the core package without any issues.

Marked as answer by cdrnet on 8/4/2014 at 6:21 PM
Aug 4, 2014 at 3:32 PM
PS: we need to verify it would not cause problems in mono and the Xamarin tools.
Aug 4, 2014 at 3:36 PM

Many thanks for the quick and positive reply, Christoph.

Best regards,
Aug 5, 2014 at 2:09 AM
Edited Aug 5, 2014 at 2:09 AM
Should be fixed with just released v3.2.0.

Marked as answer by cdrnet on 8/4/2014 at 6:21 PM