The Composite UI Application Block (or CAB) is an addition to Microsoft's.NET Framework for creating complex user interfaces made of loosely coupled components. Developed by Microsoft's patterns & practices team, CAB is used exclusively for developing Windows Forms.
Active8 years, 1 month ago
Oct 04, 2019 Traditionally, the Composite UI Application Block (or CAB, for short) has been used by Windows Forms (WinForms) developers, but as WPF applications are becoming more common, the block has been expanded to support WPF applications as well. Feb 02, 2007 Composite UI Application Block (CAB) Basically it provides the following: A framework that promotes a structured approach to building line of business applications. Dynamically loading, independent yet interoperating modules hosted in a common shell. Event broker for loosely coupled communication between modules and parts of modules. Composite UI Application Block (CAB) Basically it provides the following: A framework that promotes a structured approach to building line of business applications. Dynamically loading, independent yet interoperating modules hosted in a common shell. Event broker for loosely coupled communication between modules and parts of modules. The Composite UI Application Block (CAB) and Smart Client Software Factory (SCSF) are powerful frameworks from Microsoft that are essential for building real.
I have two very large WinForm applications built on the now dead Composite Application Block ('CAB') from Microsoft Patterns & Practices. I was an earlier adopter and jumped in first to embrace and use CAB. Well, now that it's truly dead I'm starting to think more and more about the future and what framework I can migrate to.
What I like about CAB:* Structure, structure, structure - I lose focus easily and tend to suffer from 'analysis paralysis'. CAB introduces a 'way to do things' and that keeps me on track and developing the application instead of worrying 'how to wire up events, or what the best IoC is, etc.* Actually.. I think that's about all that I really like about CAB ;0)
I have seen articles about 'build your own CAB' but I'm not interested in that. I'd really like to jump ship to a similar framework that is solid and actively supported. My web searches have not turned up anything that seems to serve the same needs as the CAB did. Maybe it's that everyone DOES build their own and that's why there isn't another framework out there.
If you have some guidance or advice I'd really like to hear it.
ioWint
1,04911 gold badge1313 silver badges3232 bronze badges
Steve KSteve K
1,32722 gold badges2424 silver badges4444 bronze badges
2 Answers
You can check out the
OR the Compaq updates and drivers.
I am not sure about specific features / patterns that are targeted by especially the SCSF v/s the CAB but i have been using WCSF for a while now and it definitely provides the structure that you like about CAB.
I believe these two do constitute the prescribed guidance from P&P and are definitely being updated.
JagmagJagmag
9,40211 gold badge2828 silver badges5454 bronze badges
![]()
I would suggest you porting your app into WPF - PRISM. I wish they had a PRISM way for Winforms too, but sadly they dont. We had two of our last enterprise level applications migrated using SCSF, now we have switched over to PRISM for the obvious reason. It does include initial learning curve, i knew wat WPF was and had my Helloworld app done with few extras. but now since we had to switch to PRISM WPF, i am having the steep learning on both! Good luck!
Microsoft Composite Ui Application Block TutorialioWintNg Block UiioWint
1,04911 gold badge1313 silver badges3232 bronze badges
Composite Ui Application Block In C#Not the answer you're looking for? Browse other questions tagged c#frameworksdesign-patternscabscsf or ask your own question.Comments are closed.
|
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |