Perhaps you may want to review the following article that explains the scenarios where you should consider using each of the Composite UI deliverables from Patterns & Practices. This could
help in your current debate about using Prism or CAB:
Guidelines for Choosing Composite UI Deliverables from patterns & practices
The Composite Application Guidance
for WPF - June 2008 release was not shipped with a guidance package. If you consider that this feature would be helpful for the community, feel free to suggest it in the
Issue Tracker and it might be taken into account for future releases.
I believe the idea behind not shipping a guidance package is to allow the class library to mature, and get feedback from the community, before starting to add tooling that may hide defects in the
API or may bias the way that the library could be used (for example by embracing a particular UI pattern) and so on. They constantly pushed for the “Simple first” approach while designing the API, in order to avoid the need for tooling in the first place,
so you may find that the lack of tooling is something that may not be missed.
FYI: In the
Composite WPF Contrib project there are available Visual Studio templates for the Composite Application Library for WPF:
Download the last change
set of the Composite WPF Contrib source code.
Check the Composite Application Guidance for WPF Visual Studio Templates
Please let me know if this helps.