Addin and CompositeWPF (Prism)

Sep 9, 2008 at 3:24 PM
Hi all,
could someone explain the key differences between Addin and CompositeWPF?
They seem very close each other, could they be used together?
If so, in which way?

We are starting a composite desktop application in WPF, we don't want to miss anything of this cool features.

Thank you very much!

- Riccardo
Sep 9, 2008 at 9:24 PM
I'm not an expert on CompositeWPF, but at a glance it looks like it's designed to build components for an application that ships in whole.

MAF is designed to build an application that is extensible after shipping, even by third parties. This means it supports easy discovery of components at run-time, run-time isolation of components (in the case where extensions are written by a third party), and version resilience.

CompositeWPF will not give you the features I mentioned for MAF above, but it might provide you with a richer experience developing WPF components.

Hope that helps you reach a decision,

Sep 10, 2008 at 3:16 PM
Thx mSid,
I think MAF and Prism could coexist.
You develop your composite application using Prism pattern and offer extensibility through MAF, specially to third party addin (gain the advantage of isolation that Prism doesn't offer).
I think It would be overkill to build a whole composite application using MAF.

- Riccardo