Kiran BalijepalliToday's post is written by Kiran Balijepalli, a Microsoft Technical Evangelist for Windows Phone. He has more than 16 years of global technology leadership experience in desktop, web, cloud and mobile platforms. You can find all of Kiran's Microsoft Student blogs here, and he can be found on Twitter as @KiranKBee.

 

 

 

Open myDataBoundApp.sln that you created as discussed in the previous blog. The solution has two .XAML pages, two view models as highlighted in the illustration.

MVVM

Model: a set of classes or objects that you can load onto memory and represents the state of the app.

View: what you present to the user that is in most cases is a page (please refer to the previous blog post on the pages and navigation models)

View-model: a state more than the view.

So in essence, when you set data context on the elements of your view to be the view model and you set properties of these through data binding (I will talk more about data binding in the feature later, there is more to learn about the depth of data binding in WP 8 SDK).

For now let us focus on the current example context. In the previous blogs we talked about Windows Phone XAML’s “Blendability,” what It means is Blend, which comes installed as part of the Windows Phone SDK provides an ability to create design time data and visualize in XAML without having even running the app.

See you in the next blog.