Microsoft have recently announced Visual Studio 2013. As part of this announcement it appears that WP7 has now fully been tombstoned - any WP7 project loaded into VS2013 will be converted to WP8 - and you will not be able to deploy it back to a WP7 device.
Further, the brilliant work that Microsoft and Xamarin are doing together for cross-platform Portable Class Library functionality will be based on the VS2013 reference assemblies - and these will not include the older WP7 compatible profiles like 104.
Because of this, I'm sorry to say that MvvmCross will very soon be dropping support for WP7.
In the period of the next 1 to 3 months:
- all MvvmCross Portable Class Libraries will shift to Profile 78
- only WP8 and later will be supported by MvvmCross
I appreciate that many MvvmCross users and many of my customers have been great supporters of WP7, and I also appreciate that 50% of currently active WP phones are 'stuck' on WP7.
However, I'm afraid that it's simply no longer possible to support WP7 given the death of tooling support in PCLs and Visual Studio.
I hope this isn't too big a problem for anyone - I will branch the code so that a WP7 archive exists, but beyond this, we will look forwards to a bright, portable future with WP8 and beyond.
It won't be a problem for me. Thanks for all the hard work you put into this product!
ReplyDeleteDoes this mean that the files "MonoAndroid,Version=v1.6+.xml" and "VSMonoTouch,Version=v1.0+.xml" will need to be copied to the Profile78/SupportedFrameworks directory?
ReplyDeleteYou can do that whenever you want to (and you can copy them rather than moving too).
DeleteBut when the official Xamarin release happens, then I think you'll need to delete our unofficial files - I think there will then be official ones instead.
What exactly do you mean by "the death of tooling support in PCLs and Visual Studio"? How does this impact the hopefully-soon release of PCL-support for Xamarin developers who use both VS and XS?
ReplyDeleteVS2013 will have no WP7 support - any WP7 project loaded into VS2013 will get one-way converted to WP8. For PCL, Microsoft have allowed Xamarin to ships with the Microsoft reference assemblies... but only the ones from VS2013 - which from what I've managed to find out so far means that Xamarin cannot support older profiles like 104.
DeleteFor more on this, please take it to a more public forum (stackoverflow, xamarin or twitter?) as I really don't hold much power here - I'm just trying to get stuff building :/
Slodge, any reason for not supporting Silverlight 5 also? Since Vs.net 2013 will support SL5 projects also.
ReplyDeletehttp://stackoverflow.com/questions/16386228/using-mvvmcross-in-a-web-project/16386386#16386386
Delete