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]<mailto:[email protected]> | W: www.readify.net<http://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
