If you’re using ListViews and are targeting Android then read on. There are some things that may be impacting you, namely: “ListView blank cells when CachingStrategy=”RetainElement” on Android: https://github.com/xamarin/Xamarin.Forms/issues/6721 …which has been closed by this one: https://github.com/xamarin/Xamarin.
A short while back, fellow Xamarin MVP Michael Ridland (@rid00z) published a great post here: http://www.michaelridland.com/xamarin/taskcompletionsource-xamarin-beautiful-async/ on using TaskCompletionSource to 'mimic' async functionality and allow you to await things that you otherwise wouldn't be able to. If you're using this to wrap calls to web
If you're trying to do this as per my previous post here GHOST_URL /post/2014/07/26/using-messageingcenter-in-xamarin-forms-for-viewmodel-to-viewmodel-navigation.aspx and are getting this error: *System.InvalidOperationException: Collection was modified; enumeration operation may not execute. * ...then you may be tripping over this: https://bugzilla.xamarin.com/show_bug.cgiand ?id=
So here are today's announcements, along with links to find out more about each. Partnership with IBM Fruits of this partnership include: * IBM MobileFirst SDK for Xamarin, a pre-built library that Xamarin and IBM devs can include in their apps to connect, secure and manage apps using IBM Worklight * IBM
Today's sessions went into a lot more detail, which was great. Several of them were standing room only. The Enterprise Track talks on cloud services, data synchronisation and mobile security were particularly useful, as were the corridor / breakfast / lunch chats with Xamarin techies and other users. There's nothing like having
This post: http://blog.alectucker.com/post/2014/05/02/cross-platform-azure-mobile-services-with-xamarin-and-mvvmcross.aspx [https://blog.alectucker.com/post/2014/05/02/cross-platform-azure-mobile-services-with-xamarin-and-mvvmcross.aspx] detailed how to set up and use Azure Mobile Services from a portable class library (PCL) in a Xamarin project with the help of MvvmCross. Since I wrote
When following the MVVM pattern your viewmodels should not communicate with each other directly, meaning no interdependencies. Navigation on the different platforms is from one view to another but we generally want to take control of the navigation structure at viewmodel level when coding cross platform apps (although admittedly, Xamarin