Posted by: MarkWPF
WPF, XAML, Xbap
Just what are Composite applications, and why do they apply to WPF?
The principal behind Composite applications is that you want to break down a large application into small pieces, and then those pieces are glued back together.
The advantages of doing such are so taken for granted that we all do it anyway in just about any application of any size.
We’ve all created UserControls or Custom controls that encapsulate the logic and process needed – without the need for any frameworks.
The big thing about Composite applications (and the frameworks therein) is that they allow you to concentrate on building the application piece by piece without worrying about how to glue it together. The glue just works!
One other big advantage is that you don’t need to worry about whether to use SDI or MDI or Tabbed MDI, as with Composite frameworks you can switch very easily. Also in building your View or form, you don’t need to add plumbing code for the MDI or SDi stuff.
Are there any composite frameworks for WPF?
There are three that I know of: Caliburn, SCSF and Composite WPF (previously called Prism)