Book Image

Windows Phone 8 Application Development Essentials

By : Tomasz Szostak
Book Image

Windows Phone 8 Application Development Essentials

By: Tomasz Szostak

Overview of this book

<p>Windows Phone 8 replaces Windows Phone 7 devices with the Windows NT kernel found on many Windows 8 components. Windows 8 will give you more options to develop better and more visually appealing PC and Tablet applications.</p> <p>A practical guide that will show you how you how to create testable MVVM applications keeping in mind the best UI practices. You will learn how to integrate peripheral sensors and social portals like Facebook and Twitter into your applications. This book shows the advantages of using modern patterns instead of the traditional way of programming.</p> <p>Starting with a Windows Phone UI description, the guide then takes you through the world of fast and fluid design guidelines. After that, you will be shown the beauty of C# and MVVM advantages, finishing with clear descriptions of mobile-application integration with peripherals and social media. Clear and well-described examples throughout will help you become a WP8 developer.</p> <p>You will also learn how to test your applications using Unit Test cut dependencies in your methods using Mocks, and use the newest features of C# such as asynchronous methods. If you are more of a designer than a developer, then there is also an explanation on how to create a consistent look and feel for Windows Phone applications.</p>
Table of Contents (12 chapters)

Folder structure

Proper organization of files within the project is necessary to keep things clear. If we come back to our project after a year or two, we will know where to find each part of the application. The first few steps after the creation of the new project are the best time to add the three folders—Model, View, and ViewModel. Each of them will contain the corresponding part of MVVM.


A view in an application defines a layout, positioning of controls, animations, and everything that a user can see on the screen. The main goal for a view is to represent data and functionality in a user-friendly way. The ideal situation is when a view is defined completely in XAML and very briefly in the code behind. Some code-behind code is required, so we cannot completely omit it.

Windows Phone applications have some typical views that are usually used, such as page or user controls. You can ask, if we have the view separated from other layers, how can we introduce interactions or populate data...