Live on MSDN!
We dramatically updated our
guidance around Windows Phone development
. Beyond recompiling our previous guidance against the Mango SDK, the latest guidance takes advantage of many Mango features such as fast app switching, background tasks, and new sensor APIs. We also did a fair amount
of work showing how to create a layer of abstraction on top of the Windows Phone APIs that facilitates unit testing.
We split up our guidance into three parts:
- Developing a Windows Phone Application using the MVVM Pattern
This guidance walks you through building a simple Windows Phone application using CodeBehind files. The guidance then shows you how the same app can be much more unit testable when built using the MVVM pattern.
- A Case Study for Building Advanced Windows Phone Applications
This guidance takes an in-depth look at how to write an advanced Windows Phone application, using many features of Mango. Unit testability was an important factor that guided the design of this application.
- Building Testable Windows Phone Applications
Taking the work on unit testability from the above guidance, this guidance provides shorter samples of how to build unit testable Windows Phone applications.
Windows Phone 7 Mango provides an exciting opportunity for companies and developers to build applications that travel with users, are interactive and attractive, and are available whenever and wherever users want to work with them.
By combining Windows Phone 7 Mango applications with on-premises services and applications, or remote services and applications that run in the cloud (such as those using the Windows Azure™ technology platform), developers can create highly scalable, reliable,
and powerful applications that extend the functionality beyond the traditional desktop or laptop; and into a truly portable and much more accessible environment.
This guide describes a scenario around a fictitious company named Tailspin that has decided to encompass Windows Phone 7 Mango as a client device for their existing cloud-based application. Their Windows Azure-based application named Surveys is described in
detail in a previous book in this series, Developing Applications for the Cloud on the Microsoft Windows Azure Platform. For more information about that book, see the page by the same name on MSDN® at
Windows Phone 7 Developer Guide
In addition to describing the client application, its integration with the remote services, and the decisions made during its design and implementation, this book discusses related factors, such as the design patterns used, the capabilities and use of Windows
Phone 7, and the ways that the application could be extended or modified for other scenarios.
The result is that, after reading this case study, you will be familiar with how to design and implement applications for Windows Phone 7 Mango that take advantage of remote services to obtain and upload data while providing a great user experience on the device.
Windows Phone 7 Test Guidance Survey
The Windows Phone 7 Guidance team has posted a very short, 10 question survey that centers on testing of Windows Phone 7 applications.
This survey will be used to drive the second phase of our current project.
This project updates the current Windows® Phone 7.0 Guidance published on MSDN at
Windows Phone 7 Developer Guide
to Windows Phone 7.5 Mango while at the same time reducing the written guidance down to a case study of the TailSpin application. This case study will also examine
and provide additional guidance for unit testing Windows Phone 7 applications.
This project and the written guidance have been renamed to Case Study: TailSpin Windows Phone 7 Survey Application.
The key themes for these projects are:
1. A Windows Phone 7 Mango client application
2. A Windows Azure backend for the system
3. Unit testing for Windows Phone 7 Mango client applications