Skip to content

Latest commit

 

History

History
65 lines (50 loc) · 5.42 KB

README.md

File metadata and controls

65 lines (50 loc) · 5.42 KB

XPlatformCloudKit

A Hands-on lab for creating your very own multi-platform app with Azure Mobile Services as a backend. Simply follow along with the included Powerpoint file located in the root of the project. The XPlatformCloudKit supports displaying grouped items retrieved from an Azure Mobile Service, Rss Data Services, and/or Local file. It can aesthetically organize grouped objects of Type Item with property of Title, Subtitle, Description, Image, and Group to produce a Windows Phone, Windows 8, and Android application by means of Portable Class Libraries, Xamarin Studio, and MVVMCross.
The value of the Description property is rendered as HTML, meaning you can do some rather interesting things, for example see:

Examples of Applications Built with the XPlatformCloudKit

Video Tutorials

Getting Started

After obtaining and installing the prerequisites, download the .zip of this project (link on the bottom right of The XPlatformCloudKit Project Home) Save the .zip, then right-click=>Properties=>Unblock=>Apply then extract the contents of the .zip file

You will then want to open the XPlatformCloudKit.sln located in the XPlatformCloudKit folder
(If you recieve a warning about being bound to Team Foundation Server or inability to open the .Droid project, simply ignore)

Follow along with the XPlatformCloudKit.pptx lab located in the root of the XPlatformCloudKit-master folder.

Prerequisites for all projects

Notes on getting Windows Phone 8 project to run:

Notes on getting Android Project to run

  • To build in Visual Studio will require a Xamarin Business License.
  • You will need to copy the folder and all contents of XPlatformCloudKit/SupportedFrameworks to:
C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\.NETPortable\v4.5\Profile\Profile78\SupportedFrameworks

This allows PCLs which target Profile78 to be consumed by Xamarin IOS/Android projects.

  • You must apply the Xamarin hotfix. This fixes an issue in the System.Linq.Expressions.dll facade used by Xamarin