Caliburn/Caliburn micro http://caliburn.codeplex.com/ imho: Magellan has a nice mix between MVC (navigation) and MVVM (UI/binding). Caliburn has great tooling (events/module discovery). Prism is not flexible enough and has a lot of bootstrapping... Regards,Nic Roche
From: [email protected] To: [email protected] Subject: RE: Anyone using Prism? Date: Sat, 27 Aug 2011 15:05:40 +1000 Hi All Thanks for the in depth discussion on IOC containers. I am also wondering about composite application patterns /navigation frameworks So far I understand there is Prism and Magellan to look at. Any others? Thanks Kirsten From: [email protected] [mailto:[email protected]] On Behalf Of Jake Ginnivan Sent: Thursday, 25 August 2011 1:07 PM To: ozDotNet Subject: RE: Anyone using Prism? I would vote against using it, it is very closely tied to Unity which is not a very good IoC container. We removed Unity and majority of our use of prism from a large app I was working on. We dropped our startup time from 30-40 seconds to about 10 seconds by rolling our own, and switching to Autofac. Plus the code was a heap cleaner and easier to maintain. Because of the legacy of prism there were areas of the codebase that we had no alternative other than using the ServiceLocator =( My vote would be to use MEF and Autofac to bring the modules together then do the composition yourself. Or use Magellan to do the composition (http://www.paulstovell.com/magellan-composite-wpf). Regards, Jake Ginnivan Readify | Senior Developer | MVP (VSTO) M: +61 403 846 400 | E: [email protected] | W: www.readify.net From: [email protected] [mailto:[email protected]] On Behalf Of Kirsten Greed Sent: Thursday, 25 August 2011 10:53 AM To: 'ozDotNet' Subject: Anyone using Prism? Hi All Anyone using Prism in anger? I would like to know your experience. Are there other composite application frameworks ( apart from CAB ) that are alternatives to it? Thanks Kirsten
