Web Client Software Factory

UPDATED WIKI: Model-View-Presenter pattern

BillKrat — Fri, 04 Jul 2008 16:52:05 GMT

Understanding MVP/MVC is crucial to effectively understanding and using WCSF

Reference 1
Interactive Application Architecture Patterns - perhaps the most comprehensive document on the matter of the Model-View-Controller (MVC) pattern and Model-View-Presenter (MVP) pattern. For accuracy purposes I used the images from the referenced document below.

Reference 2
Designing Smart Clients Based on CAB and SCSF by Mario Szpuszta, Architect | Microsoft Austria.

Reference 3
MVP: Model-View-Presenter, The Taligent Programming Model for C++ and Java by Mike Potel, VP & CTO, Taligent, Inc

Had I read the above documents (and understood them) prior to starting with CAB, and later SCSF, I would have understood what was going on, the learning curve wouldn't have been so steep and I wouldn't have made so many mistakes in how I utilized CAB/SCSF.

MODEL .... Data and Business Rules

VIEW ...... User Interface (visual representation of the Model)

CONTROLLER/ PRESENTER .... Communicate with the Model and the View (distinction - levels of abstraction)

Those of you that are familiar with MVP and MVC are probably thinking - Ah-HA! he doesn't know what he's talking about - everyone knows that "the big difference between MVC and MVP is that with MVP, the view is completely controlled by the Presenter, whereas in MVC, the controller and the model can update the view". I quote Reference 2 on the top of page 11.

You have to consider the source - literally ;) The MVC pattern originated in 1978-79 (Smalltalk-80); you can read reference 1 for the details. MVP was first formally described by Mike Potel in 1996 (Taligent, Inc) reference 3. Studying the founding father's documents on MVP and MVC you start to see that the big difference is misunderstood... The distinction is in the "Benefits of Abstractions" (see this section in reference 3)

As you look at the image above you'll see that the following is accurate:

CONTROLLER/ PRESENTER .... Communicate with the Model and the View (distinction - levels of abstraction)

In the shadow of this knowledge I would think ... Ah-Ha! They don't know what they are talking about - as I researched MVP and found that a large majority of people shared the misconception that the primary difference is that with MVP only the presenter communicates with the view.

So where did this notion come from and why is it so widely accepted as the "big difference"? You have to consider the source:

Martin Fowler Wikipedia on Martin Fowler anyone who has studied architecture, MVC and MVP will know who he is; almost any reliable source that I have used in my architecture research has referenced him. In 2006 Martin Fowler split the MVP pattern into two, the Supervising Controller and Passive View. The Supervising Controller is the SmallTalk 80 MVC pattern referenced above and the Passive View pattern is the pattern that is widely accepted as MVP even though Fowler suggest that passive MVP does not apply if databinding is used.

The Microsoft MVP patterns conceptually lean towards the Fowler Passive MVP Pattern - I say conceptually because if you use databinding then you broke the mold - via the observer pattern you have established an indirect link between the view and the model where the view observes the model for data changes. More on this by Fowler reference paragraph under figure 6

Reference 1 is perhaps the most comprehensive document that I've come across (wish I had seen it first a long time ago). Unlike any of the others it incorporates the following which shows (Passive MVP) the Application Controller or Presenter updating the view upon model data changes:

So do you see the pattern? If so, then can appreciate CAB/SCSF for what it is, and what your programs can become, an example of architectural excellence. As for the learning curve - all you have to teach folks is how to right click, select a "recipe" and where to put their business logic :)

UPDATED WIKI: Home

BillKrat — Thu, 15 May 2008 18:53:59 GMT

Resource Page Description
The Web Client Software Factory (WCSF) provides a set of guidance for architects and developers building enterprise Web applications. The factory includes samples, reusable code and a guidance package which automates key development tasks from within Visual Studio.

Using the Web Client Software Factory assets, developers can create Composite Web applications composed of independently developed and deployed modules. These modules are dynamically brought together at runtime into a common shell. Additionally the factory includes support for ASP.NET AJAX thus providing users with a richer and more responsive user experience.

This site hopes to centralize important information of value to the Web Client Software Factory community.
Click here for official site Questions, Comments, Suggestions Contact BillKrat

WCSF will be more difficult for you to grasp if you are not familiar with the Model-View-Presenter pattern - the learning can be steep If you don't see the pattern (pun intended).

Web Client Topics

.................~~~~~~~~~....................	....................~~~~~~~~.......................
Active Directory Services	Presenter
Authentication	QueryString
Cache	ShellController
Foundation Module	SiteMapProvider
GridView / DetailView	StateValueT
HttpContext	Themes
HttpSessionState	Type Mapping
ObjectContainerDataSource	Unity
Master Pages	User Control
Page Flow	WCF

Unit Test

Policy Injection Application Block (PIAB)

Model-View-Presenter pattern * Using the QuickStarts W/AjaxcontrolToolkit

Designer issues * IIS 7 * Load Balanced environment * SharePoint * WCSF Solution

Other Sites

If you are seeking help on Web Client Software Factory topics that are not covered here please visit the official Web Client Software Factory at http://www.Codeplex.com/Websf. This resource is a "solution" oriented site that will focus on answers to known issues and undocumented features.

-------------------================================================---------------------
Microsoft does not control, review, revise, endorse or distribute the resources on this site. Microsoft is hosting the MSDN Code Gallery site solely as a web storage site as a service to the developer community. For more information, read the Terms Of Use.

What are the differences between CodePlex and Code Gallery? (this site)

Code Gallery is a community-enabled Web site where you can share developer information and resources such as sample applications and code snippets. CodePlex is Microsoft's open source project hosting Web site.

Code Gallery is a pure storage site, with no project management capabilities. If you need to manage a live code project, CodePlex is a better choice.

UPDATED WIKI: Home

BillKrat — Thu, 15 May 2008 18:53:17 GMT

Web Client Topics

.................~~~~~~~~~....................	....................~~~~~~~~.......................
Active Directory Services	Presenter
Authentication	QueryString
Cache	ShellController
Foundation Module	SiteMapProvider
GridView / DetailView	StateValueT
HttpContext	Themes
HttpSessionState	Type Mapping
ObjectContainerDataSource	Unity
Master Pages	User Control
Page Flow	WCF

Unit Test

Policy Injection Application Block (PIAB)

Model-View-Presenter pattern * Using the QuickStarts W/AjaxcontrolToolkit

Designer issues * IIS 7 * Load Balanced environment * SharePoint * WCSF Solution

Other Sites

UPDATED WIKI: Home

BillKrat — Thu, 15 May 2008 18:48:38 GMT

Resource Page Description
The Web Client Software Factory (WCSF) provides a set of guidance for architects and developers building enterprise Web applications. The factory includes samples, reusable code and a guidance package which automates key development tasks from within Visual Studio.

Using the Web Client Software Factory assets, developers can create Composite Web applications composed of independently developed and deployed modules. These modules are dynamically brought together at runtime into a common shell. Additionally the factory includes support for ASP.NET AJAX thus providing users with a richer and more responsive user experience.

This site hopes to centralize important information of value to the Web Client Software Factory community.
Click here for official site

WCSF will be more difficult for you to grasp if you are not familiar with the Model-View-Presenter pattern - the learning can be steep If you don't see the pattern (pun intended).

Web Client Topics

.................~~~~~~~~~....................	....................~~~~~~~~.......................
Active Directory Services	Presenter
Authentication	QueryString
Cache	ShellController
Foundation Module	SiteMapProvider
GridView / DetailView	StateValueT
HttpContext	Themes
HttpSessionState	Type Mapping
ObjectContainerDataSource	Unity
Master Pages	User Control
Page Flow	WCF

Unit Test

Policy Injection Application Block (PIAB)

Model-View-Presenter pattern * Using the QuickStarts W/AjaxcontrolToolkit

Designer issues * IIS 7 * Load Balanced environment * SharePoint * WCSF Solution

Other Sites

UPDATED WIKI: Home

BillKrat — Fri, 09 May 2008 15:21:24 GMT

Resource Page Description
The Web Client Software Factory (WCSF) provides a set of guidance for architects and developers building enterprise Web applications. The factory includes samples, reusable code and a guidance package which automates key development tasks from within Visual Studio.

Using the Web Client Software Factory assets, developers can create Composite Web applications composed of independently developed and deployed modules. These modules are dynamically brought together at runtime into a common shell. Additionally the factory includes support for ASP.NET AJAX thus providing users with a richer and more responsive user experience.

This site hopes to centralize important information of value to the Web Client Software Factory community.
Click here for official site

WCSF will be more difficult for you to grasp if you are not familiar with the Model-View-Presenter pattern - the learning can be steep If you don't see the pattern (pun intended).

Web Client Topics

.................~~~~~~~~~....................	....................~~~~~~~~.......................
Active Directory Services	Presenter
Authentication	QueryString
Cache	ShellController
Foundation Module	SiteMapProvider
GridView / DetailView	StateValueT
HttpContext	Themes
HttpSessionState	Type Mapping
ObjectContainerDataSource	Unity
Master Pages	User Control
Page Flow	WCF

Unit Test

Policy Injection Application Block (PIAB)

Model-View-Presenter pattern * Using the QuickStarts W/AjaxcontrolToolkit

Designer issues * IIS 7 * Load Balanced environment * SharePoint * WCSF Solution

UPDATED WIKI: Unit Test

BillKrat — Fri, 09 May 2008 15:20:11 GMT

How do I get access to HttpContext in my presenter?

HttpContext in Presenter

UPDATED WIKI: Home

BillKrat — Fri, 09 May 2008 15:19:55 GMT

Resource Page Description
The Web Client Software Factory (WCSF) provides a set of guidance for architects and developers building enterprise Web applications. The factory includes samples, reusable code and a guidance package which automates key development tasks from within Visual Studio.

Using the Web Client Software Factory assets, developers can create Composite Web applications composed of independently developed and deployed modules. These modules are dynamically brought together at runtime into a common shell. Additionally the factory includes support for ASP.NET AJAX thus providing users with a richer and more responsive user experience.

This site hopes to centralize important information of value to the Web Client Software Factory community.
Click here for official site

WCSF will be more difficult for you to grasp if you are not familiar with the Model-View-Presenter pattern - the learning can be steep If you don't see the pattern (pun intended).

Web Client Topics

.................~~~~~~~~~....................	....................~~~~~~~~.......................
Active Directory Services	Presenter
Authentication	QueryString
Cache	ShellController
Foundation Module	SiteMapProvider
GridView / DetailView	StateValueT
HttpContext	Themes
HttpSessionState	Type Mapping
ObjectContainerDataSource	Unity * Unit Test
Master Pages	User Control
Page Flow	WCF

Policy Injection Application Block (PIAB)

Model-View-Presenter pattern * Using the QuickStarts W/AjaxcontrolToolkit

Designer issues * IIS 7 * Load Balanced environment * SharePoint * WCSF Solution

UPDATED WIKI: Cache

BillKrat — Fri, 09 May 2008 15:19:35 GMT

I wonder what is best practice when it comes to cache data that is relatively static during the lifetime of an application. Some data are completely static like the list of Countries, Currencies etc.

Cache relatively static data using Application State?

How do I get access to HttpContext in my presenter?

HttpContext in Presenter

UPDATED WIKI: Home

BillKrat — Sat, 26 Apr 2008 04:19:27 GMT

Resource Page Description
The Web Client Software Factory (WCSF) provides a set of guidance for architects and developers building enterprise Web applications. The factory includes samples, reusable code and a guidance package which automates key development tasks from within Visual Studio.

Using the Web Client Software Factory assets, developers can create Composite Web applications composed of independently developed and deployed modules. These modules are dynamically brought together at runtime into a common shell. Additionally the factory includes support for ASP.NET AJAX thus providing users with a richer and more responsive user experience.

This site hopes to centralize important information of value to the Web Client Software Factory community.
Click here for official site

WCSF will be more difficult for you to grasp if you are not familiar with the Model-View-Presenter pattern - the learning can be steep If you don't see the pattern (pun intended).

Web Client Topics

.................~~~~~~~~~....................	....................~~~~~~~~.......................
Active Directory Services	Presenter
Authentication	QueryString
Cache	ShellController
Foundation Module	SiteMapProvider
GridView / DetailView	StateValueT
HttpContext	Themes
HttpSessionState	Type Mapping
ObjectContainerDataSource	Unity
Master Pages	User Control
Page Flow	WCF

Policy Injection Application Block (PIAB)

Model-View-Presenter pattern * Using the QuickStarts W/AjaxcontrolToolkit

Designer issues * IIS 7 * Load Balanced environment * SharePoint * WCSF Solution

UPDATED WIKI: Model-View-Presenter pattern

BillKrat — Sat, 26 Apr 2008 04:19:06 GMT

Understanding MVP/MVC is crucial to effectively understanding and using WCSF

Reference 1
Interactive Application Architecture Patterns - perhaps the most comprehensive document on the matter of the Model-View-Controller (MVC) pattern and Model-View-Presenter (MVP) pattern. For accuracy purposes I used the images from the referenced document below.

Reference 2
Designing Smart Clients Based on CAB and SCSF by Mario Szpuszta, Architect | Microsoft Austria.

Reference 3
MVP: Model-View-Presenter, The Taligent Programming Model for C++ and Java by Mike Potel, VP & CTO, Taligent, Inc

Had I read the above documents (and understood them) prior to starting with CAB, and later SCSF, I would have understood what was going on, the learning curve wouldn't have been so steep and I wouldn't have made so many mistakes in how I utilized CAB/SCSF.

MODEL .... Data and Business Rules

VIEW ...... User Interface (visual representation of the Model)

CONTROLLER/ PRESENTER .... Communicate with the Model and the View (distinction - levels of abstraction)

Those of you that are familiar with MVP and MVC are probably thinking - Ah-HA! he doesn't know what he's talking about - everyone knows that "the big difference between MVC and MVP is that with MVP, the view is completely controlled by the Presenter, whereas in MVC, the controller and the model can update the view". I quote Reference 2 on the top of page 11.

You have to consider the source - literally ;) The MVC pattern originated in 1978-79 (Smalltalk-80); you can read reference 1 for the details. MVP was first formally described by Mike Potel in 1996 (Taligent, Inc) reference 3. Studying the founding father's documents on MVP and MVC you start to see that the big difference is misunderstood... The distinction is in the "Benefits of Abstractions" (see this section in reference 3)

As you look at the image above you'll see that the following is accurate:

CONTROLLER/ PRESENTER .... Communicate with the Model and the View (distinction - levels of abstraction)

In the shadow of this knowledge I would think ... Ah-Ha! They don't know what they are talking about - as I researched MVP and found that a large majority of people shared the misconception that the primary difference is that with MVP only the presenter communicates with the view.

So where did this notion come from and why is it so widely accepted as the "big difference"? You have to consider the source:

Martin Fowler Wikipedia on Martin Fowler anyone who has studied architecture, MVC and MVP will know who he is; almost any reliable source that I have used in my architecture research has referenced him. In 2006 Martin Fowler split the MVP pattern into two, the Supervising Controller and Passive View. The Supervising Controller is the SmallTalk 80 MVC pattern referenced above and the Passive View pattern is the pattern that is widely accepted as MVP (did I emphasize that he did this in 2006?).

The Microsoft MVP patterns conceptually lean towards the Fowler Passive MVP Pattern - I say conceptually because if you use databinding then you broke the mold - via the observer pattern you have established an indirect link between the view and the model where the view observes the model for data changes. More on this by Fowler reference paragraph under figure 6

Reference 1 is perhaps the most comprehensive document that I've come across (wish I had seen it first a long time ago). Unlike any of the others it incorporates the following which shows (Passive MVP) the Application Controller or Presenter updating the view upon model data changes:

So do you see the pattern? If so, then can appreciate CAB/SCSF for what it is, and what your programs can become, an example of architectural excellence. As for the learning curve - all you have to teach folks is how to right click, select a "recipe" and where to put their business logic :)

UPDATED WIKI: Home

BillKrat — Sat, 26 Apr 2008 04:18:33 GMT

Web Client Topics

WCSF will be more difficult for you to grasp if you are not familiar with the Model-View-Presenter pattern - the learning can be steep If you don't see the pattern (pun intended).

.................~~~~~~~~~....................	....................~~~~~~~~.......................
Active Directory Services	Presenter
Authentication	QueryString
Cache	ShellController
Foundation Module	SiteMapProvider
GridView / DetailView	StateValueT
HttpContext	Themes
HttpSessionState	Type Mapping
ObjectContainerDataSource	Unity
Master Pages	User Control
Page Flow	WCF

Policy Injection Application Block (PIAB)

Model-View-Presenter pattern * Using the QuickStarts W/AjaxcontrolToolkit

Designer issues * IIS 7 * Load Balanced environment * SharePoint * WCSF Solution

UPDATED WIKI: Home

BillKrat — Sat, 26 Apr 2008 04:03:12 GMT

Web Client Topics

.................~~~~~~~~~....................	....................~~~~~~~~.......................
Active Directory Services	Presenter
Authentication	QueryString
Cache	ShellController
Foundation Module	SiteMapProvider
GridView / DetailView	StateValueT
HttpContext	Themes
HttpSessionState	Type Mapping
ObjectContainerDataSource	Unity
Master Pages	User Control
Page Flow	WCF

Policy Injection Application Block (PIAB)

Model-View-Presenter pattern * Using the QuickStarts W/AjaxcontrolToolkit

Designer issues * IIS 7 * Load Balanced environment * SharePoint * WCSF Solution

UPDATED WIKI: Home

BillKrat — Sat, 26 Apr 2008 04:02:50 GMT

Web Client Topics

.................~~~~~~~~~....................	....................~~~~~~~~.......................
Active Directory Services	Presenter
Authentication	QueryString
Cache	ShellController
Foundation Module	SiteMapProvider
GridView / DetailView	StateValueT
HttpContext	Themes
HttpSessionState	Type Mapping
ObjectContainerDataSource	Unity
Master Pages	User Control
Page Flow	WCF

Policy Inection Application Block (PIAB)

Model-View-Presenter pattern * Using the QuickStarts W/AjaxcontrolToolkit

Designer issues * IIS 7 * Load Balanced environment * SharePoint * WCSF Solution

UPDATED WIKI: Home

BillKrat — Sat, 26 Apr 2008 04:02:11 GMT

Web Client Topics

......................~~~~~~~~~............................	......................~~~~~~~~........................
Active Directory Services	Presenter
Authentication	QueryString
Cache	ShellController
Foundation Module	SiteMapProvider
GridView / DetailView	StateValueT
HttpContext	Themes
HttpSessionState	Type Mapping
ObjectContainerDataSource	Unity
Master Pages	User Control
Page Flow	WCF

Policy Inection Application Block (PIAB)

Model-View-Presenter pattern * Using the QuickStarts W/AjaxcontrolToolkit

Designer issues * IIS 7 * Load Balanced environment * SharePoint * WCSF Solution

UPDATED WIKI: Home

BillKrat — Sat, 26 Apr 2008 04:01:42 GMT

Web Client Topics

..................................................	.................................................
Active Directory Services	Presenter
Authentication	QueryString
Cache	ShellController
Foundation Module	SiteMapProvider
GridView / DetailView	StateValueT
HttpContext	Themes
HttpSessionState	Type Mapping
ObjectContainerDataSource	Unity
Master Pages	User Control
Page Flow	WCF

Policy Inection Application Block (PIAB)

Model-View-Presenter pattern * Using the QuickStarts W/AjaxcontrolToolkit

Designer issues * IIS 7 * Load Balanced environment * SharePoint * WCSF Solution

UPDATED WIKI: Home

BillKrat — Sat, 26 Apr 2008 03:57:34 GMT

Web Client Topics

Active Directory Services	Presenter
Authentication	QueryString
Cache	ShellController
Foundation Module	SiteMapProvider
GridView / DetailView	StateValueT
HttpContext	Themes
HttpSessionState	Type Mapping
ObjectContainerDataSource	Unity
Master Pages	User Control
Page Flow	WCF
Policy Inection Application Block (PIAB)
--	--
Model-View-Presenter pattern	Using the QuickStarts W/AjaxcontrolToolkit
Designer issues * IIS 7 * Load Balanced environment * SharePoint * WCSF Solution

UPDATED WIKI: Home

BillKrat — Sat, 26 Apr 2008 03:56:58 GMT

Web Client Topics

Active Directory Services	Presenter
Authentication	QueryString
Cache	ShellController
Foundation Module	SiteMapProvider
GridView / DetailView	StateValueT
HttpContext	Themes
HttpSessionState	Type Mapping
ObjectContainerDataSource	Unity
Master Pages	User Control
Page Flow	WCF
Policy Inection Application Block (PIAB)
--	--
Model-View-Presenter pattern	Using the QuickStarts W/AjaxcontrolToolkit
Designer issues * IIS 7 * Load Balanced environment	SharePoint * WCSF Solution