Apr 10, 2012 at 11:47 AM
Edited Apr 10, 2012 at 11:47 AM
I was unable to get to that portion of the guidance you mentioned in your post. Your link points somewhere else.
I don't think you can hook your seperate web applications as modules within an asp.net solution.
This wireing up is provided within the CWAB via the objectbuilder infrastructure.(as of now). There are folks working on using Unity (http://http://unity.codeplex.com/) as the Dependency Injection mechanism for WCSF. This should greatly reduce the code required.
To specifically answer your question,
What the WCSF/CWAB affords you is to build modules as seperate folders in your web application with their own dlls that will reside in the bin folder as well. These modules can still interact with each other via services. Your web pages/master pages/user
controls must be written in such a way that the objectbuilder knows what to inject at runtime.
I suggest you start with the WCSF hands on labs. Go to the MSDN page at
http://msdn.microsoft.com/en-us/library/ff648752.aspx and look for the hands on lab link. (It's for a previous release).
I think that this guidance has now really turned into a community effort and a new guidance (silk.codeplex.com) seems to have subsumed it.
I haven't had the time to look at it. But it looks promising and is based on asp.net mvc3.