<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.com/utility/FeedStylesheets/atom.xsl" media="screen"?><feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en-US"><title type="html">Francis K. Cheung</title><subtitle type="html">The journey of an agile programmer...</subtitle><id>http://blogs.msdn.com/b/francischeung/atom.aspx</id><link rel="alternate" type="text/html" href="http://blogs.msdn.com/b/francischeung/" /><link rel="self" type="application/atom+xml" href="http://blogs.msdn.com/b/francischeung/atom.aspx" /><generator uri="http://telligent.com" version="5.6.50428.7875">Telligent Evolution Platform Developer Build (Build: 5.6.50428.7875)</generator><updated>2011-06-15T19:58:10Z</updated><entry><title>Prism for Windows Runtime: Validating User Input</title><link rel="alternate" type="text/html" href="http://blogs.msdn.com/b/francischeung/archive/2013/05/07/prism-for-windows-runtime-validating-user-input.aspx" /><id>http://blogs.msdn.com/b/francischeung/archive/2013/05/07/prism-for-windows-runtime-validating-user-input.aspx</id><published>2013-05-07T18:23:26Z</published><updated>2013-05-07T18:23:26Z</updated><content type="html">This is the fifth post in a series that walks you through creating a simple Windows Store app using the Prism for Windows Runtime library. Please review the fourth post in the series for the steps necessary to create the basic app based on MvvmAppBase. One feature that is missing from Windows Store app sdk is control support for user input validation. In WPF and Silverlight, you would expect to implement INotifyDataErrorInfo/IDataErrorInfo and controls such as TextBox and ComboBox would show an error...(&lt;a href="http://blogs.msdn.com/b/francischeung/archive/2013/05/07/prism-for-windows-runtime-validating-user-input.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=10416755" width="1" height="1"&gt;</content><author><name>fcheung</name><uri>http://blogs.msdn.com/fcheung/ProfileUrlRedirect.ashx</uri></author></entry><entry><title>Prism for Windows Runtime: Integrating a Dependency Injection Container</title><link rel="alternate" type="text/html" href="http://blogs.msdn.com/b/francischeung/archive/2013/04/26/prism-for-windows-runtime-integrating-a-dependency-injection-container.aspx" /><id>http://blogs.msdn.com/b/francischeung/archive/2013/04/26/prism-for-windows-runtime-integrating-a-dependency-injection-container.aspx</id><published>2013-04-26T22:13:35Z</published><updated>2013-04-26T22:13:35Z</updated><content type="html">This is the fourth post in a series that walk you through creating a simple Windows Store app using the Prism for Windows Runtime library. Please review the third post in the series for the steps necessary to create the basic MVVM style app based on MvvmAppBase. You can get the latest source on CodePlex . The following procedure shows how to integrate a dependency injection container into a Windows Store app that leverages MvvmAppBase from the Microsoft.Practices.Prism.StoreApps library. Add a reference...(&lt;a href="http://blogs.msdn.com/b/francischeung/archive/2013/04/26/prism-for-windows-runtime-integrating-a-dependency-injection-container.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=10414402" width="1" height="1"&gt;</content><author><name>fcheung</name><uri>http://blogs.msdn.com/fcheung/ProfileUrlRedirect.ashx</uri></author></entry><entry><title>Prism for Windows Runtime: Creating and showing a Flyout using the FlyoutService class</title><link rel="alternate" type="text/html" href="http://blogs.msdn.com/b/francischeung/archive/2013/04/25/prism-for-windows-runtime-creating-and-showing-a-flyout-using-the-flyoutservice-class.aspx" /><id>http://blogs.msdn.com/b/francischeung/archive/2013/04/25/prism-for-windows-runtime-creating-and-showing-a-flyout-using-the-flyoutservice-class.aspx</id><published>2013-04-25T22:46:49Z</published><updated>2013-04-25T22:46:49Z</updated><content type="html">This is the third post in a series that walk you through creating a simple Windows Store app using the Prism for Windows Runtime library. Please review the second post in the series for the steps necessary to create the basic MVVM style app based on MvvmAppBase. You can get the latest source on CodePlex . The following procedure shows how to create and show a Flyout by using the Microsoft.Practices.Prism.StoreApps library. You will discover how to use the FlyoutService class within a view model to...(&lt;a href="http://blogs.msdn.com/b/francischeung/archive/2013/04/25/prism-for-windows-runtime-creating-and-showing-a-flyout-using-the-flyoutservice-class.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=10414112" width="1" height="1"&gt;</content><author><name>fcheung</name><uri>http://blogs.msdn.com/fcheung/ProfileUrlRedirect.ashx</uri></author></entry><entry><title>Prism for Windows Runtime: Creating a basic implementation of the MVVM pattern</title><link rel="alternate" type="text/html" href="http://blogs.msdn.com/b/francischeung/archive/2013/04/25/prism-for-windows-runtime-creating-a-basic-implementation-of-the-mvvm-pattern.aspx" /><id>http://blogs.msdn.com/b/francischeung/archive/2013/04/25/prism-for-windows-runtime-creating-a-basic-implementation-of-the-mvvm-pattern.aspx</id><published>2013-04-25T18:38:56Z</published><updated>2013-04-25T18:38:56Z</updated><content type="html">This is the second blog post in a series that walk you through creating a simple Windows Store app using the Prism for Windows Runtime library. Please review the first post in the series for the steps necessary to create the basic app based on MvvmAppBase. MvvmAppBase exposes several services including the FrameNavigationService which is necessary for both navigation and view model state persistence. You can get the latest source on CodePlex . The following procedure shows how to create a basic implementation...(&lt;a href="http://blogs.msdn.com/b/francischeung/archive/2013/04/25/prism-for-windows-runtime-creating-a-basic-implementation-of-the-mvvm-pattern.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=10414052" width="1" height="1"&gt;</content><author><name>fcheung</name><uri>http://blogs.msdn.com/fcheung/ProfileUrlRedirect.ashx</uri></author></entry><entry><title>Prism for Windows Runtime</title><link rel="alternate" type="text/html" href="http://blogs.msdn.com/b/francischeung/archive/2013/04/25/prism-for-windows-runtime.aspx" /><id>http://blogs.msdn.com/b/francischeung/archive/2013/04/25/prism-for-windows-runtime.aspx</id><published>2013-04-24T23:15:28Z</published><updated>2013-04-24T23:15:28Z</updated><content type="html">As Blaine Wastell posted , we are about to release the patterns &amp;amp; practices guidance for building Windows Store business apps. You may be thinking… “What is a business app?” and “How is a business app different than any other app?”. Well the simple answer is that a “business” app is expected to be well architected, maintainable, testable, and have high quality. Business apps may differ from simple content consumption apps in many ways. Business apps are more likely to need data validation. There...(&lt;a href="http://blogs.msdn.com/b/francischeung/archive/2013/04/25/prism-for-windows-runtime.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=10413826" width="1" height="1"&gt;</content><author><name>fcheung</name><uri>http://blogs.msdn.com/fcheung/ProfileUrlRedirect.ashx</uri></author></entry><entry><title>SHIPPED!!! Windows Phone Developer Guidance updated for Mango (WP SDK 7.1)</title><link rel="alternate" type="text/html" href="http://blogs.msdn.com/b/francischeung/archive/2012/04/03/shipped-windows-phone-developer-guidance-updated-for-mango-wp-sdk-7-1.aspx" /><id>http://blogs.msdn.com/b/francischeung/archive/2012/04/03/shipped-windows-phone-developer-guidance-updated-for-mango-wp-sdk-7-1.aspx</id><published>2012-04-03T05:30:38Z</published><updated>2012-04-03T05:30:38Z</updated><content type="html">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...(&lt;a href="http://blogs.msdn.com/b/francischeung/archive/2012/04/03/shipped-windows-phone-developer-guidance-updated-for-mango-wp-sdk-7-1.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=10290199" width="1" height="1"&gt;</content><author><name>fcheung</name><uri>http://blogs.msdn.com/fcheung/ProfileUrlRedirect.ashx</uri></author></entry><entry><title>Running Windows Phone Unit Tests via MSBuild</title><link rel="alternate" type="text/html" href="http://blogs.msdn.com/b/francischeung/archive/2012/01/03/running-windows-phone-unit-tests-via-msbuild.aspx" /><id>http://blogs.msdn.com/b/francischeung/archive/2012/01/03/running-windows-phone-unit-tests-via-msbuild.aspx</id><published>2012-01-03T23:10:24Z</published><updated>2012-01-03T23:10:24Z</updated><content type="html">I’m a big fan of TDD and continuous integration, so when I first started development on Windows Phone 7, I quickly found Jeff Wilcox’s Silverlight Unit Test Framework . This unit testing framework provides a nice way to write MSTest style unit tests and have them run on a device/emulator. The piece that was missing for me was the ability to capture the results of the unit test run and include these results with an automated run of MSBuild. If any unit tests fail, the MSBuild run should fail. I’ve...(&lt;a href="http://blogs.msdn.com/b/francischeung/archive/2012/01/03/running-windows-phone-unit-tests-via-msbuild.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=10252857" width="1" height="1"&gt;</content><author><name>fcheung</name><uri>http://blogs.msdn.com/fcheung/ProfileUrlRedirect.ashx</uri></author></entry><entry><title>Tombstoning in Windows Phone 7.5</title><link rel="alternate" type="text/html" href="http://blogs.msdn.com/b/francischeung/archive/2011/12/08/tombstoning-in-windows-phone-7-5.aspx" /><id>http://blogs.msdn.com/b/francischeung/archive/2011/12/08/tombstoning-in-windows-phone-7-5.aspx</id><published>2011-12-08T00:54:22Z</published><updated>2011-12-08T00:54:22Z</updated><content type="html">There is quite a bit written on how to handle tombstoning on a Windows Phone. Most of the guidance is for code-behind developers. Here is an MSDN article ( How to: Preserve and Restore Page State for Windows Phone ) that shows how to use the Page’s OnNavigatedTo and OnNavigatedFrom methods to preserve and restore page state. This article proposes using an instance variable (_isNewPageInstance) to distinguish between navigating to the page due to dormancy or tombstoning. protected override void OnNavigatedTo...(&lt;a href="http://blogs.msdn.com/b/francischeung/archive/2011/12/08/tombstoning-in-windows-phone-7-5.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=10245344" width="1" height="1"&gt;</content><author><name>fcheung</name><uri>http://blogs.msdn.com/fcheung/ProfileUrlRedirect.ashx</uri></author></entry><entry><title>Case Study: TailSpin Windows Phone Survey Application</title><link rel="alternate" type="text/html" href="http://blogs.msdn.com/b/francischeung/archive/2011/12/07/case-study-tailspin-windows-phone-survey-application.aspx" /><id>http://blogs.msdn.com/b/francischeung/archive/2011/12/07/case-study-tailspin-windows-phone-survey-application.aspx</id><published>2011-12-07T21:16:01Z</published><updated>2011-12-07T21:16:01Z</updated><content type="html">We are just about to release an update to the Windows Phone 7 Developer Guide that p&amp;amp;p shipped one year ago. The updated guidance takes the same scenario but updates the phone client application leveraging features in the Windows Phone 7.1 OS Mango release. We will ultimately publish the final bits and docs on MSDN in January but you can find it on CodePlex with in the next few weeks. Here are some topics we tackled in this new release: Support for Fast App Switching as well as Tombstoning Improved...(&lt;a href="http://blogs.msdn.com/b/francischeung/archive/2011/12/07/case-study-tailspin-windows-phone-survey-application.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=10245285" width="1" height="1"&gt;</content><author><name>fcheung</name><uri>http://blogs.msdn.com/fcheung/ProfileUrlRedirect.ashx</uri></author></entry><entry><title>Composite Services Guidance: External Routing Configuration sample</title><link rel="alternate" type="text/html" href="http://blogs.msdn.com/b/francischeung/archive/2011/06/15/composite-services-guidance-external-routing-configuration-sample.aspx" /><id>http://blogs.msdn.com/b/francischeung/archive/2011/06/15/composite-services-guidance-external-routing-configuration-sample.aspx</id><published>2011-06-15T18:58:10Z</published><updated>2011-06-15T18:58:10Z</updated><content type="html">Let me give you a little background on this sample. If you look at the WCF Routing Service , you can quickly and easily configure a router with endpoints and message filters in the web.config. This is a great way to set up context based routing. You can configure a message filter that identifies messages that call specific methods, have certain information in the header. You can then forward messages that match this filter to a specific endpoint. The External Routing Configuration sample simply illustrates...(&lt;a href="http://blogs.msdn.com/b/francischeung/archive/2011/06/15/composite-services-guidance-external-routing-configuration-sample.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=10174982" width="1" height="1"&gt;</content><author><name>fcheung</name><uri>http://blogs.msdn.com/fcheung/ProfileUrlRedirect.ashx</uri></author></entry></feed>