It seems that building a solution with two PCL projects and one iOS project in Xamarin Studio or Visual Studio and attempting to load them in the other tool leads to a broken build.
I've been recently trying to roll out an application with a pretty simple structure, it contains the following:
-- iOS project for view -- PCL project for service layer -- PCL project for data access
The PCL projects are utilizing the Microsoft.Bcl, Microsoft.Bcl.Build, Microsoft.Bcl.Async and Microsoft.Net Portable libraries. Regardless of which Studio I'm using, I utilize Nuget to grab and install those packages for me.
In the case of the Xamarin Studio project, when I build it in Visual Studio, I get a lot of errors like:
"Warning 10 The primary reference "System.Net.Http" could not be resolved because it has an indirect dependency on the framework assembly "System.Runtime, Version=1.5.11.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" which could not be resolved in the currently targeted framework. ".NETPortable,Version=v4.0,Profile=Profile136". To resolve this problem, either remove the reference "System.Net.Http" or retarget your application to a framework version which contains "System.Runtime, Version=1.5.11.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a"."
In the case of the Visual Studio originated project, when I build it in Xamarin Studio, I get a warning that I need to add the Microsoft.Bcl.Build nuget package to any that reference it even though I've included them to remove that same warning from Visual Studio.
In both cases, the referenced PCL projects in the iOS project appear as being missing assemblies.
Thanks in advance, let me know if there's any details I need to fill in.