Book Image

Mastering Xamarin.Forms - Second Edition

By : Ed Snider
Book Image

Mastering Xamarin.Forms - Second Edition

By: Ed Snider

Overview of this book

Discover how to extend and build upon the components of the Xamarin.Forms toolkit to develop effective, robust mobile app architecture. Starting with an app built with the basics of the Xamarin.Forms toolkit, we'll go step by step through several advanced topics to create a solution architecture rich with the benefits of good design patterns and best practices. We'll start by introducing a core separation between the app's user interface and the app's business logic by applying the MVVM pattern and data-binding. Then we will focus on building out a layer of plugin-like services that handle platform-specific utilities such as navigation and geo-location, as well as how to loosely use these services in the app with inversion of control and dependency injection. Next we'll connect the app to a live web-based API and set up offline synchronization. Then, we'll dive into testing the app logic through unit tests. Finally, we will setup Visual Studio App Center to automate building, testing, distributing and monitoring the app.
Table of Contents (11 chapters)

To get the most out of this book

To get the most out of this book, you should have a working knowledge of the Xamarin platform and Xamarin.Forms toolkit as well as experience with .NET.

In order to follow along with the code throughout this book, you will need to have Visual Studio and Xamarin installed on your Windows or Mac machine. Although the examples throughout this book are shown in Visual Studio for Mac, everything shown can also be done in Visual Studio for Windows. If you are using a Windows machine, you will need a Mac running Xamarin on your network to serve as a build host to build and deploy iOS apps. For details on setting up a Mac build host or any other requirements for setting up a Xamarin development environment, visit

In Chapter 6, API Data Access, you will need a Microsoft Azure account in order to follow along with the examples to create a basic API using an Azure App Service.

Throughout this book, there are several tools and libraries used, which are obtained from NuGet via the Visual Studio package manager.

Download the example code files

You can download the example code files for this book from your account at If you purchased this book elsewhere, you can visit and register to have the files emailed directly to you.

You can download the code files by following these steps:

  1. Log in or register at
  2. Select the SUPPORT tab.
  3. Click on Code Downloads & Errata.
  4. Enter the name of the book in the Search box and follow the onscreen instructions.

Once the file is downloaded, please make sure that you unzip or extract the folder using the latest version of:

  • WinRAR/7-Zip for Windows
  • Zipeg/iZip/UnRarX for Mac
  • 7-Zip/PeaZip for Linux

The code bundle for the book is also hosted on GitHub at We also have other code bundles from our rich catalog of books and videos available at Check them out!

Conventions used

There are a number of text conventions used throughout this book.

CodeInText: Indicates code words in text, class names, property names, field names, folder names, filenames, file extensions, pathnames, URLs, and user input. Here is an example: "Create a new folder in the core project named Models."

A block of code is set as follows:

public abstract class BaseViewModel
protected BaseViewModel ()
{ }

When we wish to draw your attention to a particular part of a code block, the relevant lines or items are set in bold:

public App()
MainPage = new NavigationPage(new TripLog.MainPage());

Bold: Indicates a new term, an important word, or words that you see onscreen. For example, words in menus or dialog boxes appear in the text like this. Here is an example: "In Visual Studio, click on File | New Solution."

Warnings or important notes appear like this.

Tips and tricks appear like this.