WCSF with SharePoint

Topics: Web Client Software Factory, UIP Application Block discussion
Feb 22, 2008 at 11:17 AM
Hi All!
I have installed and successfuly run quick sample for pageflow in VS2005.
But I am not being able to implement WCSF 2007 in SharePoint 3.0.
i also added the necessary elements in share point web.config for application blocks and added required binaries in GAC.
Everything is compilable but on debuging I found the controller and presenter to be null. I suspect that the ObjectBuilder block is not injecting these objects when i run the pages from sharepoint sites.

Is it possible to run only pageflow without using view-presenter and controller objects in sharepoint?

I would appreciate if you peple help me out.

Imran Ashraf
Software Engineer
Feb 29, 2008 at 5:56 AM
We did not design nor test around this scenario. I have had people tell me that they got parts of WCSF to work under SharePoint, and others tell me it is impossible.

With a bit of work, and stealing a bit of code from the PageFlow block, you should be able to get something PageFlow-like working under Sharepoint. My question is would it be better to use the Workflow capabilites built into Sharepoint instead?
Good luck.

Michael Puleio - patterns & practices
Mar 13, 2008 at 4:50 PM
I've had to think about this a bit more recently, and I am revising my comments a bit. The fact that I have no experience doing MOSS development does not help things at all.

As far as sharepoint + WCSF, there are issues in that both have customized Application classes (defined in Global.asax) that conflict. This would require hacking the Composite Web Application Block (CWAB) (the heart of a lot of WCSF functionality), but may be doable.

Sharepoint + Pageflow may work, but it is not something we considered in development. Thankfully, PageFlow is independent of the rest of WCSF, so you could try to integrate it. There was a Quickstart in the January 2007 and June(?) 2007 releases that had Pageflow working independent of CWAB. Using that as a starting point might be a good idea. However, since Sharepoint does things differently than your typical ASP.NET application, there are no guarantees.

Michael Puleio - patterns & practices
Sep 9, 2008 at 2:17 PM



We published two new releases that provides guidance on:

·         Enabling CWAB in a SharePoint Application

·         Enabling Unity in a SharePoint Application


These releases include the following elements:

·         A PDF document with guidance to enable CWAB/Unity in a SharePoint application to make Web Parts more testable.

·         Extensions for CWAB/Unity to work on a SharePoint application

o   CompositeWeb.SharePoint solution: it includes a class that implements the IWebClientApplication interface and inherits from SPHttpApplication class.

o   Unity.SharePoint solution: it includes a class that inherits from SPHttpApplication and hosts a Unity container.

·         A sample implementation that uses the extensions for CWAB/Unity This solution includes a web part that injects dependencies (also has a Unit Test project).

·         Sample files like the global.asax and web.config for a SharePoint application enabled with CWAB/Unity.


We also published the documentation guidance in the WCSF KB as wiki pages. You can find them here:

·         How To: Enable CWAB in a SharePoint Application

·         How To: Enable Unity in a SharePoint Application to make Web Parts more testable


Please, let me know if it helps.


Mariano Converti