AutoMapper 4.2 and Ninject 3.2 : <p>I'm updating a project of mine to use AutoMapper 4.2, and I'm running into breaking changes. While I <em>seem</em> to have resolved said changes, I'm not entirely convinced I've done so in the most appropriate way.</p>

<p>In the old code, I have a <code>NinjectConfiguration</code>, and an <code>AutoMapperConfiguration</code> class that are each loaded by WebActivator. In the new version the <code>AutoMapperConfiguration</code> drops out and I instead instance a <code>MapperConfiguration</code> directly in the <code>NinjectConfiguration</code> class where the bindings are happening, like so:</p>

<pre><code>private static void RegisterServices(
    IKernel kernel) {
    var profiles = AssemblyHelper.GetTypesInheriting&lt;Profile&gt;(Assembly.Load("???.Mappings")).Select(Activator.CreateInstance).Cast&lt;Profile&gt;();
    var config = new MapperConfiguration(
        c =&gt; {
            foreach (var profile in profiles) {
                c.AddProfile(profile);
            }
        });

    kernel.Bind&lt;MapperConfiguration&gt;().ToMethod(
        c =&gt;
            config).InSingletonScope();

    kernel.Bind&lt;IMapper&gt;().ToMethod(
        c =&gt;
            config.CreateMapper()).InRequestScope();

    RegisterModules(kernel);
}
</code></pre>

<p>So, is this the appropriate way of binding AutoMapper 4.2 using Ninject? It seems to be working so far, but I just want to make sure.</p>
