MEF vs. PRISM. What is the difference? What will be supported in the future? -

I have read the same posts but I am not clear

What I want to make , It's a silverlight app with some tabs / modules that all have different DLLs.

I think the Prism has shell / module concepts which have been shown in the direction of UI and I am getting a good demo (shows how to find Digg / Twitter).

But it seems like MEF will be included in VS2010 so that I would like to go with that option.

Can anyone clearly explain the differences? (I'm not an advanced programmer)

(Update 1) So the MEF and Unity are basically the same ... and the prism is at the top of those concepts and this UI is specific ...

The answer seems to be using PRIsM because what I'm asking is breaking a silverlight app into different UI pieces ..

Does any PRISM know the future of development? Is it done or is it going on?

MEF and PRISM fulfill two special goals.

Prism is basically a guide to designing composite applications - where you have shell and "areas" that are dynamically assigned, and integrated. It contains an IOC container which uses it for its injection.

MEF is a dependency injection framework - its main goal is to "fill" colonists at runtime for the application. In this regard, it is to fill the same goal as unity can easily recruit the prism in the prism (and, in fact, you use MEF instead of unity).

In some cases, the prism fills a wide range, but it is actually limited to GUI applications. MEF is doing only one thing (DP injection), but is ready for more general purpose for any type of application.

---

Edit in response to updates:

As for the lifespan of these products - there is no answer here, but how it is being developed:

Prism patterns and practices were developed by the team, not to make the target software necessary, but to provide guidance. As such, those updates (although sometimes to some extent sometimes) update the Prism Library and the sample, but the prism is not the main part of the framework sent by Microsoft. It is actually a third party library (even if MS makes a lot of money Most P & P people are not MS SS).

MEF, from a blog post, looks like it has been integrated into the framework, and should be used directly within MS projects, such as directly from Microsoft, heavy development, and its products Is being used in

I have personally, read through the prism documentation (and book), and have gone through the sample. It is very helpful to understand the method of breaking an application, but it is actually more guidance than a complete, useful structure. They are very good at working with samples, who educate an architect in the way of designing an overall application.

If your goal is to separate only one concerns in the Silverlight application, I just focus more on learning MVVM than using the prism.

If you want to use MEF, other good options are, for example, a complete MVVM framework has been built on top of using MEF, and is quite good.