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

Multiplication Table in SQL Server

Multiplication Table in SQL Server This query gives the multiplication table from 1 to 10. DECLARE @A INT,                   @B INT,                   @C INT,                   @D VARCHAR (100)                   SELECT @A=1                  PRINT ' MULTIPLICATION TABLE 1-10' /****************************************/ /* Created By : Loganathan V */ /* Created On: 20-Sep-2010, Monday */ /* Purpose : Multiplication Table */ /* How to : RUN THE QUERY */ /****************************************/ WHILE (@A<=10) BEGIN         ...

Virtual machines vs. Containers

One of the questions that often comes up to anybody who's in the cloud space is, what are the differences between virtual machines and container? When should use one versus the other? Unfortunately the answer is not so simple clear-cut. We can't say you should always use containers or always use virtual machines. But, there are some things to keep in mind. There are certain kinds of applications which benefit from running in containers or using micro services in general. Microservices means taking an application and decomposing it into smaller parts. This is really good if you need to build a web scale application and you need to have the ability to turn up different dials of performance somewhat independent of each other. For example, take the middleware piece or the front end or the database piece and you need to scale them individually. The other benefit of containers is a consistency between the development environment and the production environment where you can take thing...

Node.js for Everything

Lots of web applications using Javascript for front end for a long time. Javascript enabling people to build really really interactive great products, we can use Javascript on the front end and on the back end. So, what do we do on the back end? Node.js is the answer. Here we'll see some of the npm packages that'll help us to enable Javascript in back end as well. Load balancing is the main one when you plan to host your application server environment. Node offers pm2 package to easy your job. It's modern CLI process manager for Node apps with a builtin load-balancer. npm install pm2@latest -g pm2 start app.js Next thing is running applications continuously. Yeah, we've a node package named forever. It's a simple CLI tool for ensuring that a given node script runs continuously. npm install forever -g forever start app.js Enabling debugging in Javascript client applications are easy. Debugging a node application is sometimes a black box sometimes not, but one of the ...