Answered by:
MVVM Beginner

Question
-
What is MVVM on Windows Store App briefly Explain please (Including RealyCommand ) , I am Beginner
Wednesday, May 28, 2014 9:22 AM
Answers
-
21 minutes, 52 seconds
Jeff Sanders (MSFT)
@jsandersrocks - Windows Store Developer Solutions @WSDevSol
Getting Started With Windows Azure Mobile Services development? Click here
Getting Started With Windows Phone or Store app development? Click here
My Team Blog: Windows Store & Phone Developer Solutions
My Blog: Http Client Protocol Issues (and other fun stuff I support)- Proposed as answer by Jeff SandersMicrosoft employee, Moderator Wednesday, May 28, 2014 12:45 PM
- Marked as answer by Jeff SandersMicrosoft employee, Moderator Monday, June 2, 2014 3:02 PM
Wednesday, May 28, 2014 12:45 PMModerator -
- Proposed as answer by Jeff SandersMicrosoft employee, Moderator Wednesday, May 28, 2014 1:47 PM
- Marked as answer by Jeff SandersMicrosoft employee, Moderator Monday, June 2, 2014 3:02 PM
Wednesday, May 28, 2014 12:47 PMModerator -
This is a brief overview:
View
-
Describes the user interface using a declarative markup such as XAML.
-
Presents information to the user (data-binding).
-
Responds to the user input (commands and keyboard shortcuts).
-
Composed of the following elements:
-
XAML elements
-
value converters
-
data templates
-
visual state groups
-
storyboards
-
behaviours - pieces of packaged code that is used to add interactivity to the app
-
triggers - DataTriggers have been replaced with Visual State Manager
-
code - additional UI-related logic
-
ViewModel
-
Responsible for interaction between the View and the Model.
-
Provides presentation logic for one or multiple Views.
-
Has three ways of communicating with the View:
-
data-binding
-
visual states
-
commands and method calls
-
-
Implements the property change notification interface.
Model
-
Describes business entities (e.g. Publisher, Book, Order) usually implemented as classes.
-
Describes business logic operating on the entities without involving UI (View) and presentation logic (ViewModel).
-
Describes relations between the entities.
-
Contains state of the entities.
-
Accesses entity data from local or remote sources.
-
Includes any data caching mechanism if needed.
I also found this link helpful:
Getting Started with MVVM: http://channel9.msdn.com/Shows/Visual-Studio-Toolbox/Getting-Started-with-MVVM
Leszek
Wiki: wbswiki.com
Website: www.wisenheimerbrainstorm.com- Proposed as answer by Jeff SandersMicrosoft employee, Moderator Wednesday, May 28, 2014 1:48 PM
- Marked as answer by Jeff SandersMicrosoft employee, Moderator Monday, June 2, 2014 3:02 PM
Wednesday, May 28, 2014 1:39 PM -
All replies
-
21 minutes, 52 seconds
Jeff Sanders (MSFT)
@jsandersrocks - Windows Store Developer Solutions @WSDevSol
Getting Started With Windows Azure Mobile Services development? Click here
Getting Started With Windows Phone or Store app development? Click here
My Team Blog: Windows Store & Phone Developer Solutions
My Blog: Http Client Protocol Issues (and other fun stuff I support)- Proposed as answer by Jeff SandersMicrosoft employee, Moderator Wednesday, May 28, 2014 12:45 PM
- Marked as answer by Jeff SandersMicrosoft employee, Moderator Monday, June 2, 2014 3:02 PM
Wednesday, May 28, 2014 12:45 PMModerator -
- Proposed as answer by Jeff SandersMicrosoft employee, Moderator Wednesday, May 28, 2014 1:47 PM
- Marked as answer by Jeff SandersMicrosoft employee, Moderator Monday, June 2, 2014 3:02 PM
Wednesday, May 28, 2014 12:47 PMModerator -
This is a brief overview:
View
-
Describes the user interface using a declarative markup such as XAML.
-
Presents information to the user (data-binding).
-
Responds to the user input (commands and keyboard shortcuts).
-
Composed of the following elements:
-
XAML elements
-
value converters
-
data templates
-
visual state groups
-
storyboards
-
behaviours - pieces of packaged code that is used to add interactivity to the app
-
triggers - DataTriggers have been replaced with Visual State Manager
-
code - additional UI-related logic
-
ViewModel
-
Responsible for interaction between the View and the Model.
-
Provides presentation logic for one or multiple Views.
-
Has three ways of communicating with the View:
-
data-binding
-
visual states
-
commands and method calls
-
-
Implements the property change notification interface.
Model
-
Describes business entities (e.g. Publisher, Book, Order) usually implemented as classes.
-
Describes business logic operating on the entities without involving UI (View) and presentation logic (ViewModel).
-
Describes relations between the entities.
-
Contains state of the entities.
-
Accesses entity data from local or remote sources.
-
Includes any data caching mechanism if needed.
I also found this link helpful:
Getting Started with MVVM: http://channel9.msdn.com/Shows/Visual-Studio-Toolbox/Getting-Started-with-MVVM
Leszek
Wiki: wbswiki.com
Website: www.wisenheimerbrainstorm.com- Proposed as answer by Jeff SandersMicrosoft employee, Moderator Wednesday, May 28, 2014 1:48 PM
- Marked as answer by Jeff SandersMicrosoft employee, Moderator Monday, June 2, 2014 3:02 PM
Wednesday, May 28, 2014 1:39 PM -