This is my second article for Windows Presentation Foundation (WPF) and Silverlight developers who want to start creating Windows Store apps without compromising on architecture. I assume you've read Part 1; this article continues where that one left off and is a lot more practical than the first. The bulk of this article consists of two tutorials: one for setting up a new project using the Model-View-ViewModel (MVVM) pattern and one for using MVVM navigation. Before getting to the tutorials, however, I want to briefly review some of the key concepts of the MVVM pattern. To get the most out of this article, you should have some knowledge of the MVVM pattern. (Those of you familiar with MVVM can skip right to the tutorials.) If you want to know about MVVM in more detail than what I provide, you can easily find a wealth of information on the Web. MVVM is a common and popular pattern used in developing apps for WPF/Silverlight, Windows Phone 7 and Windows Store. The MVVM pattern is all about cleanly separating the view, its logic and the model in order to create an architecture that is maintainable, scalable and testable. The following sections describe the various components of MVVM.


I guess you came to this post by searching similar kind of issues in any of the search engine and hope that this resolved your problem. If you find this tips useful, just drop a line below and share the link to others and who knows they might find it useful too.

Stay tuned to my blog, twitter or facebook to read more articles, tutorials, news, tips & tricks on various technology fields. Also Subscribe to our Newsletter with your Email ID to keep you updated on latest posts. We will send newsletter to your registered email address. We will not share your email address to anybody as we respect privacy.

This article is related to

</ span>C#,.NET,Architect,Intermediate,VS2010,.Net,Articles,Computer Tutorials,Windows Store Apps,WPF,Silverlight