Model-View-Controller Architectural Pattern

User Interface Process Application Block for .NET*
http://msdn2.microsoft.com/en-us/library/ms998252.aspx

Summary: *The User Interface Process Application Block provides a simple
yet extensible framework for developing user interface processes. It is
designed to abstract the control flow and state management out of the user
interface layer into a user interface process layer. This enables you to
write generic code for the control flow and state management of different
types of applications (for example, Web applications and Windows-based
applications) and helps you write applications that manage users’ tasks in
complex scenarios (for example, suspending and resuming stateful tasks).
This leads to simpler development and maintenance of complex applications.
The User Interface Process Application Block can easily be used as a
building block in your own .NET application. (11 printed pages)


*Model-view-controller (MVC) Architectural Pattern*

http://en.wikipedia.org/wiki/Model-view-controller

It is common to split an application into separate layers: presentation
(UI), domain logic, and data access. In MVC the presentation layer is
further separated into view and controller . MVC encompasses more
of the architecture of an application than is typical for a design pattern.
Model The *domain*-specific representation of the information on which the
application operates. Domain logic adds meaning to raw data (e.g.,
calculating whether today is the user’s birthday, or the totals, taxes and
shipping charges for shopping cart items). Many applications use a
persistent storage mechanism (such as a database)
to store data. MVC does not specifically mention the data access layer
because it is understood to be underneath or encapsulated by the Model. View
Renders the model into a form suitable for interaction, typically a user
interface element. Multiple views can exist for a single model for different purposes. Controller Processes and responds to events, typically user actions, and may invoke changes on
the model.

 

 

MVVM cs MVP vs MVC: The differences explained
http://joel.inpointform.net/software-development/mvvm-vs-mvp-vs-mvc-the-differences-explained/

Understanding MVC, MVP and MVVM Design Patterns
http://www.dotnet-tricks.com/Tutorial/designpatterns/2FMM060314-Understanding-MVC,-MVP-and-MVVM-Design-Patterns.html

MVC,MVP and MVVM: A Comparison of Architectural Patterns
http://channel9.msdn.com/Events/TechEd/NorthAmerica/2011/DPR305

MVVM Compared To MVC and MVP
http://geekswithblogs.net/dlussier/archive/2009/11/21/136454.aspx