I’ve been looking at Unity a little lately. I appreciate that this doesn’t necessarily fall into the category of “new” as it’s been around for a while but I’m meeting more and more developers who are using it ( or other comparable frameworks ) and it also crops up in frameworks like Prism which, again, I’m seeing more and more people either using or referencing as they do work with WPF and/or Silverlight. What’s Unity? It’s a “dependency injection container”. Now, at that point a bunch of folks reading this will say “Yes, we know and we’re already using it for reasons A, B, C or we’ve elected not to use it for reasons X,Y,Z ” and I imagine a bunch of other folks might say; “Huh? What’s a dependency injection container?” This post is for the latter people – it’s not meant to be exhaustive but hopefully it’s not completely unhelpful either :-) The key word here is dependency . In software, we all know what it means to take dependencies on other components. Examples; The other component ships late and breaks your...