Composite WPF vs Caliburn

Jan 18, 2009 at 6:52 PM
I was wondering if someone could shed some light on the differences between these 2 frameworks.
For instance, can / should they ever be used together. If so, is there a lot of similar concerns addressed by both, or do they really address a unique set of concerns.


Jan 19, 2009 at 1:50 AM
I learned a long time ago it doesn't pay to get off the Microsoft's "Yellow Brick Road"; 3rd parties are just not going to be able to keep up with the technologies (so you get locked out of cool new stuff).   The CompositeWPF/Prism is supported by a Microsoft Practices & Patterns team which is going to be very difficult to compete with.   With Multi-targeting (support for both Silverlight and Desktop) and a the notion that a future release could have MEF and MAF integrated into it suggest you would have to be real careful about going elsewhere; when that package comes out you will have a very powerful infrastructure that is tied into the next version of .NET.  

Jan 22, 2009 at 2:59 AM
  Thanks for the reply.
  Yeah, I'm defnitely on board with Composite WPF, but just wanted to throw the question out there to see if someone who has had experience with both can shed any light on whether or not there are aspects of Caliburn that might be worth using with Composite WPF.