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)

Chapter 3. Building a Windows Phone 8 Application using MVVM

In this chapter, we will put our attention to more technical cases than those that were described in the two previous chapters. As a result of this chapter, we will start working on an application that will be extended in the next chapters. Model-View-ViewModel (MVVM) is a pattern that separates a view's logic from an application's logic and allows us to create highly maintainable and testable applications. It sounds good, doesn't it?

An easy (and lazy) way of creating Silverlight applications was by dragging the control from the toolbox to the design surface and then handling user interactions in the code behind. It can be a good solution for very small one screen applications with poor business logic. Problems can appear when we will like to extend such applications to improve and introduce features or just make some changes to the layout. When we have the view separated from application logic, we can modify the user interface...