Skip to main content

Unity vs MEF in Prism

Prism offering two injection containers named Unity and MEF. Both the containers have their own capabilities. Before choosing the container decide your environment needs.

Some of the capabilities provided by both (Unity & MEF) containers include the following:
Both register types with the container.
Both register instances with the container.
Both imperatively create instances of registered types.
Both inject instances of registered types into constructors.
Both inject instances of registered types into properties.
Both have declarative attributes for marking types and dependencies that need to be managed.
Both resolve dependencies in an object graph.

Unity provides several capabilities that MEF does not:
Unity resolves concrete types without registration.
Unity resolves open generics.
Unity uses interception to capture calls to objects and add additional functionality to the target object.

MEF provides several capabilities that Unity does not:
MEF discovers assemblies in a directory.
MEF uses XAP file download and assembly discovery.
MEF recomposes properties and collections as new types are discovered.
MEF automatically exports derived types.
MEF is deployed with the .NET Framework.

While choosing which container to use, keep in mind the preceding capabilities and determine which fits your environment/scenario/application/architecture better.

Comments

Popular posts from this blog

Javascript - Unanswered questions - Part 1

What is Event delegation? Event delegation is Javascript as it relates to the DOM. It basically means that if you attach an event listener to a DOM element that listener is not only firing on that DOM element. It's actually firing on every children in that. So, for instance if you have a navigation and so you've got an unordered list you've got list items and then you've got anchor tags inside that navigation what you have. If you add an event listener to the ul element in essence you're actually adding event listener to all of the children as well. In short, JS event listeners fir not only on a single DOM element but on all its descendants. What is Event Bubbling? It's actually inverse of Event delegation. Also known as propagation, events on an DOM element will bubble up and also fire on all parents.  What's the difference between "target" and "currentTarget"? target is the actual element that triggered the event for example clicked, wh...

What's Virtual DOM?

There’s no big difference between the regular DOM and the virtual DOM. It’s better to think of the virtual DOM as React’s local and simplified copy of the HTML DOM. It allows React to do its computations within this abstract world and skip the real DOM operations, often slow and browser-specific. Real DOM operations are really really expensive. The Virtual DOM is an abstraction of the HTML DOM. It is lightweight and detached from the browser-specific implementation details.  One thing you should remember that the DOM itself was already an abstraction. So, Virtual DOM is an abstraction of an abstraction. :)