patterns & practices Web Client Developer Guidance

I created a web UI solution using WCSF. This solution consists of aspx pages hosted on IIS. This works fine.

On this web solution, I created another webapplication I want to create a user control available for a MOSS smartpart and then publish to the MOSS server.

There are 2 questions:
1. What do I have to do to Copy/Move this user control to another web application. What other dependencys are there?
2. Is it possible to create more than 1 web application that share the same business module? WCSF 2.0 does not allow me to add new web application.

Any guidance or best practice ?

Environment
VS 2008
WCSF 2.0

In fact thats the issue. Other web applications may not be WCSF app . (It contains only the usercontrols to be exported to MOSS)

When I make it WCSF app it causes the error converting Microsoft.SharePoint.ApplicationRuntime.SPHttpApplication to CompositeWeb.WebClientApplication

and the other issue is the global.asax file, I cannot add this to MOSS:
@ Application Language="C#" Inherits="Microsoft.Practices.CompositeWeb.WebClientApplication"

After trying several methods getting another error at MOSS webpart: Unable to cast object of type 'ASP.global_asax' to type 'Microsoft.Practices.CompositeWeb.WebClientApplication'

Hi

 

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

http://blogs.southworks.net/mconverti