Just want to know, why your solution with Portable Class Libraries is not still a part of main branch? Is it just an experiment, do you have plans to continue work on it?
The vNext branch usind portable libraries is still I believe the future and the best way forwards.
However, I've still got some outstanding problems to solve with monotouch - requiring some changes with xamarin - monotouch and monodevelop PCL support is still quite basic v1 support and I need some v2 features. I've talked with a couple of engineers about this since April and looked at the monodevelop source myself, but there's no firm timeline on this yet. The rtm of .net 4.5 and vs11 (including PCL v2) may help get this moving.
Until I get PCL working in monotouch, then I must keep the master branch as the non-portable version.
Hello, Stuart
ReplyDeleteJust want to know, why your solution with Portable Class Libraries is not still a part of main branch? Is it just an experiment, do you have plans to continue work on it?
Thanks for the question.
DeleteThe vNext branch usind portable libraries is still I believe the future and the best way forwards.
However, I've still got some outstanding problems to solve with monotouch - requiring some changes with xamarin - monotouch and monodevelop PCL support is still quite basic v1 support and I need some v2 features. I've talked with a couple of engineers about this since April and looked at the monodevelop source myself, but there's no firm timeline on this yet. The rtm of .net 4.5 and vs11 (including PCL v2) may help get this moving.
Until I get PCL working in monotouch, then I must keep the master branch as the non-portable version.
Hope that explanation helps.
If it helps, here's some technical info - https://bugzilla.xamarin.com/show_bug.cgi?id=5346
ReplyDelete