Is this the right way to register types in Unity using a convention-based approach?

Question

I am registering my types by convention, but some types from my other assemblies are not registering consistently. Sometimes they are registered, while other times they aren't. It's not consistently failing. Here's some trace data:

...is an interface and cannot be constructed. Are you missing a type mapping?

I want to eliminate 3rd party dlls and such from my registration process. Is this the right way to do this?

public static class UnityConfig
{
    public static void RegisterComponents()
    {
        var container = new UnityContainer();

        container.RegisterTypes(
         AllClasses.FromLoadedAssemblies().Where(t => t.Namespace != null && t.Namespace.StartsWith("MY NAMESPACEs ONLY")),
         WithMappings.FromMatchingInterface,
         WithName.Default);

        GlobalConfiguration.Configuration.DependencyResolver = new UnityDependencyResolver(container);
    }
}

EDIT: This also randomly happens when I remove the "Where" filter. I've used this registration methodology before and this NEVER happened. What's going on?

score 1 · Answer 1 · edited May 23 '17 at 11:59

I stumpled upon this myself and realised that it was AllClasses.FromLoadedAssemblies() that didn't work as expected (It probably worked as intended, just not how I expected it). It seemed as it was loading the assemblies in a different order in different environments. I wasn't able to figure out the solution for this, but I found a workaround.

The solution in my case was to avoid AllClasses.FromLoadedAssemblies() by using BuildManager.GetReferencedAssemblies().

.RegisterTypes(
    AllClasses.FromAssemblies(
             BuildManager.GetReferencedAssemblies().Cast<Assembly>()),
    WithMappings.FromMatchingInterface,
    WithName.Default,
    overwriteExistingMappings: true);

See the original question that solved it in my case here: Unity registration fails after iisreset

Please let me know. It can very well be some other issue. But this was the issue in my case. Good luck! — smoksnes, Mar 15 '16 at 11:42

Is this the right way to register types in Unity using a convention-based approach?

1 Answers1