CAB is an unsupported Patterns and Practices guideline which is destined
for the scrap-heap.

Before you cry out in pain don't despair. CAB promotes many excellent
practices including a great deal of architectural and pattern usage
guidance. In particular the Dependency Injection system.

The lessons learned from CAB are currently being built into the new
application framework Acropolis which is in an early CTP form at the
moment but which will have great influence on future application
development systems, especially in the Orcas time-frame.

In my day job we have used CAB extensively and are currently studying
the Acropolis migration path which, Microsoft assures me, will be
relatively painless.