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

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

ASP.NET Dynamic Compilation

In ASP.NET Web Applications, When we request a page it must parse and compile the code of Web Application into one or more assemblies. When the code is compiled, it's translated into a language independent and CPU independent code, that's MSIL code. When we create an ASP.NET page, actually creating the source code for a .NET class. We are creating a new instance of the System.Web.UI.Page class.The entire contents of an ASP.NET page, including all script and HTML content, are compiled into a .NET class. When request an ASP.NET page, ASP.NET Framework checks for a .NET class that corresponds to that page. If a corresponding class does not exist, the Framework automatically compiles the page into a new class and stores the compiled class (the assembly) in the Temporary ASP.NET Files folder. The Temporary ASP.NET files folder located at : \WINDOWS\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files The next time anyone requests the same page in the future, the page is not co...
Post a Comment
Read more