Next, go ahead and add a reference to the Mvvm Cross package to all projects.
Before we can start building out our application there are a few more administrative changes we need to make in order to take advantage of Mvvm Cross.
Forms app and one that uses Mvvm Cross is that with Mvvm Cross the navigation is controlled at a View Model level.
This includes the starting point, which in this case we're setting to be the Main View Model.
Next, we need to change the base class of the Main Page from Content Page to Mvx Content Page.
This is where cross-platform frameworks offer the ability to build an application once and have it target multiple platforms. Forms, a framework that sits on top of the cross-platform tooling offered by Xamarin, and how it can be used in conjunction with Mvvm Cross to rapidly develop applications for i OS, Android and Universal Windows Platform (UWP). Forms also supports Mac OS, Tizen and Windows Presentation Foundation (WPF), giving it one of the widest ranges of platforms of any cross-platform framework.
When you use an instance of Data Service Collection for data binding, the WCF Data Services client libraries handle these events to ensure that objects tracked by the Data Service Context remain synchronized with the data in the bound UI element.
The Data Service Collection class (indirectly) implements the INotify Collection Changed interface to alert the context when objects are added to or removed from the collection.
In this case we'll go with the Blank App, since we're going to create the pages and navigation ourselves; we'll select all three platforms and we'll use the . Before talking about the choice of code-sharing strategy, let's quickly look at what Xamarin. Xamarin, now part of Microsoft, identified that a large proportion of applications being built would benefit from the layout being defined once in a platform-agnostic way, with it being rendered on each supported platform.
While it is possible to define the layout of your application in code, most Xamarin.