Does unity just make clasess with out needing anything registered?

Question

I am watching Mike Tautly's awesome intro to Prism. It was all making sense, but I got a bit confused in the sixth video.

He has his view class's constructor take a parameter of the ViewModel. He then says that unity will fill this in for us (ie construct it).

In the past he has had to register this kind of thing (ie IMyClass registered to MyClass). But he did not do that for the ViewModel.

The only difference I can see is that the dependency to the ViewModel was not an interface, but rather a direct class. Does unity see that and just try to construct the ViewModel or did I miss a step? (And if the ViewModel had parameters would it try to make those too?)

Answer 1

When a type can be instantiated (i.e. not a base class nor an interface) unity can figure out how that type is created without the need of registering a type mapping.

Mappings are useful when the type to be injected is not instantiatable on its own.

I hope this helps.

Thanks, Damian

Answer 2

Unity tries to construct the class injecting resolved dependencies in the biggest constructor (with the maximum number of parameter).

So, if you have such a view model:

public class ViewModel
{
    public ViewModel(IMyDependency dependency) { .. }
    ...
}

you only need to register IMyDependency.