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.
Labels:

Comments

Post a Comment

Popular posts from this blog

Microservices vs. APIs

It still surprises me just how many times I come across misconceptions around Micro Services and APIs. Often hearing phrases like micro services are fine grained web services or API is themselves are equivalent to micro services. These all sort of show fundamental misconceptions under the covers. So, I've written this just to really break that out and explain about what the key differences are in those two concepts. What is an API? An API, fundamentally Application Programming Interface, that is an interface. It's a way of making requests into a component. So it's the route that you go in to make those requests. In modern use that typically means a REST API, that's a call made using HTTP protocol using JSON data as the payload. What are Micro Services? So let's ensure we also have a clear crisp definition on what a micro service architecture really is. Micro-Services architecture is about breaking down large silo applications into smalle...
Post a Comment
Read more

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. :)
Post a Comment
Read more