You might want to look at part 2 http://philipm.at/2011/0819/
On 25 August 2011 13:50, Jake Ginnivan <[email protected]> wrote: > Quite good timing actually, here is a post which backs up my point about > staying away from unity if you want a well performing app:**** > > ** ** > > http://philipm.at/2011/0808/**** > > ** ** > > Another negative side effect of Prism is that modules have a single Run > method. Which you have to do your container registrations and resolve your > dependencies.**** > > ** ** > > Internally when you resolve, if you have performed any registrations since > you last resolved the container has to rebuild it’s dependency tree, which > is costly. Autofac forces you to create a ContainerBuilder then build the > container from that, so you mentally separate registration and resolutions, > this has the advantage that Autofac does not have to lock the container when > you perform a Resolve, reducing contention and once again speeding the > container up. Unity has to lock on all operations.**** > > ** ** > > 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 *Jake Ginnivan > *Sent:* Thursday, 25 August 2011 11:07 AM > *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**** > -- Cheers, Shane DISCLAIMER NOTICE The contents of this email are confidential. If you are not the intended recipient, you must not disclose, copy or use the contents in anyway. If you have received this email in error, please delete it and notify us by reply email. It is the recipient's responsibility to screen this message and any attachments for computer viruses. Thank you.
