NinjectDependencyResolver fails binding ModelValidatorProvider
Asked Answered
D

10

33

I'm developing an ASP.NET Web Api 2.2 with C#, .NET Framework 4.5.1.

After updating my Web.Api to Ninject 3.2.0 I get this error:

Error activating ModelValidatorProvider using binding from ModelValidatorProvider to NinjectDefaultModelValidatorProvider
A cyclical dependency was detected between the constructors of two services.

Activation path:
  3) Injection of dependency ModelValidatorProvider into parameter defaultModelValidatorProviders of constructor of type DefaultModelValidatorProviders
  2) Injection of dependency DefaultModelValidatorProviders into parameter defaultModelValidatorProviders of constructor of type NinjectDefaultModelValidatorProvider
  1) Request for ModelValidatorProvider

Suggestions:
  1) Ensure that you have not declared a dependency for ModelValidatorProvider on any implementations of the service.
  2) Consider combining the services into a single one to remove the cycle.
  3) Use property injection instead of constructor injection, and implement IInitializable
     if you need initialization logic to be run after property values have been injected.

I get the exception in NinjectWebCommon:

public static class NinjectWebCommon 
{
    private static readonly Bootstrapper bootstrapper = new Bootstrapper();

    /// <summary>
    /// Starts the application
    /// </summary>
    public static void Start() 
    {
        DynamicModuleUtility.RegisterModule(typeof(OnePerRequestHttpModule));
        DynamicModuleUtility.RegisterModule(typeof(NinjectHttpModule));
        bootstrapper.Initialize(CreateKernel);
    }

    /// <summary>
    /// Stops the application.
    /// </summary>
    public static void Stop()
    {
        bootstrapper.ShutDown();
    }

    /// <summary>
    /// Creates the kernel that will manage your application.
    /// </summary>
    /// <returns>The created kernel.</returns>
    private static IKernel CreateKernel()
    {
        var kernel = new StandardKernel();
        try
        {
            kernel.Bind<Func<IKernel>>().ToMethod(ctx => () => new Bootstrapper().Kernel);
            kernel.Bind<IHttpModule>().To<HttpApplicationInitializationHttpModule>();

            RegisterServices(kernel);
            return kernel;
        }
        catch
        {
            kernel.Dispose();
            throw;
        }
    }

    /// <summary>
    /// Load your modules or register your services here!
    /// </summary>
    /// <param name="kernel">The kernel.</param>
    private static void RegisterServices(IKernel kernel)
    {
        var containerConfigurator = new NinjectConfigurator();
        containerConfigurator.Configure(kernel);
    }        
}

NinjectDependencyResolver class:

using Ninject;
using System;
using System.Collections.Generic;
using System.Web.Http.Dependencies;

namespace Matt.SocialNetwork.Web.Common
{
    public class NinjectDependencyResolver : IDependencyResolver
    {
        private readonly IKernel _container;

        public IKernel Container
        {
            get { return _container; }
        }

        public NinjectDependencyResolver(IKernel container)
        {
            _container = container;
        }

        public object GetService(Type serviceType)
        {
            return _container.TryGet(serviceType);
        }

        public IEnumerable<object> GetServices(Type serviceType)
        {
            return _container.GetAll(serviceType);
        }

        public IDependencyScope BeginScope()
        {
            return this;
        }

        public void Dispose()
        {
            // noop
        }
    }
}

NinjectConfigurator class:

public class NinjectConfigurator
{
    public void Configure(IKernel container)
    {
        // Add all bindings/dependencies
        AddBindings(container);

        // Use the container and our NinjectDependencyResolver as
        // application's resolver
        var resolver = new NinjectDependencyResolver(container);
        GlobalConfiguration.Configuration.DependencyResolver = resolver;
    }

    // Omitted for brevity.
}

The strange thing is it compiles and works perfectly, but after update it doesn't work.

I have changed this public class NinjectDependencyResolver : IDependencyResolver, System.Web.Mvc.IDependencyResolver but it still doesn't work.

Any idea?

UPDATE

Debugging I see that the exception is thrown in NinjectDependencyResolver here:

public IEnumerable<object> GetServices(Type serviceType)
{
    return _container.GetAll(serviceType);
}

It runs twice. First serviceType is IFilterProvider and second time serviceType is ModelValidatorProvider, and after that I get the exception.

These are the Ninject packages that I'm using:

<package id="Ninject" version="3.2.2.0" targetFramework="net451" />
<package id="Ninject.MVC5" version="3.2.1.0" targetFramework="net45" />
<package id="Ninject.Web.Common" version="3.2.3.0" targetFramework="net451" />
<package id="Ninject.Web.Common.WebHost" version="3.2.3.0" targetFramework="net451" />
<package id="Ninject.Web.WebApi" version="3.2.2.0" targetFramework="net451" />

The previous version for these assemblies were:

<package id="Ninject" version="3.2.2.0" targetFramework="net45" />
<package id="Ninject.MVC5" version="3.2.1.0" targetFramework="net45" />
<package id="Ninject.Web.Common" version="3.2.2.0" targetFramework="net451" />
<package id="Ninject.Web.Common.WebHost" version="3.2.0.0" targetFramework="net45" />
<package id="Ninject.Web.WebApi" version="3.2.0.0" targetFramework="net451" />

SECOND UPDATE

I have found that the problem is in this class:

public static class WebContainerManager
{
    public static IKernel GetContainer()
    {
        var resolver = GlobalConfiguration.Configuration.DependencyResolver as NinjectDependencyResolver;
        if (resolver != null)
        {
            return resolver.Container;
        }

        throw new InvalidOperationException("NinjectDependencyResolver not being used as the MVC dependency resolver");
    }

    public static T Get<T>()
    {
        return GetContainer().Get<T>();
    }
}

I set Dependency Resolver here:

public class NinjectConfigurator
{
    /// <summary>
    /// Entry method used by caller to configure the given 
    /// container with all of this application's 
    /// dependencies. Also configures the container as this
    /// application's dependency resolver.
    /// </summary>
    public void Configure(IKernel container)
    {
        // Add all bindings/dependencies
        AddBindings(container);

        // Use the container and our NinjectDependencyResolver as
        // application's resolver
        var resolver = new NinjectDependencyResolver(container);
        GlobalConfiguration.Configuration.DependencyResolver = resolver;
    }

And I use WebContainerManager in a class that inherits from ExceptionFilterAttribute:

public class UnhandledExceptionFilter : ExceptionFilterAttribute
{
    private readonly IExceptionLogHelper excepLogHelper;

    public UnhandledExceptionFilter()
        : this(WebContainerManager.Get<IExceptionLogHelper>()) {}

    public UnhandledExceptionFilter(IExceptionLogHelper exceptionLogHelper)
    {
        this.excepLogHelper = exceptionLogHelper;
    }

    public override void OnException(HttpActionExecutedContext actionExecutedContext)
    {
        this.excepLogHelper.LogException(actionExecutedContext);
    }
}

So, if I remove WebContainerManager I don't get that cycle.

Dolichocephalic answered 11/10, 2014 at 7:29 Comment(4)
have you tried uninstalling all the ninject packages and reinstalling them? Make sure you really got the newest version?Kerr
Yes, I did that and I got the same error.Dolichocephalic
can you upload the mcve as visual studio project on gist/github repo or something like that? I'd like to take a stab at it.Kerr
as a side note, instead of using WebContainerManager to statically capture the kernel and use as service locator, i would use this approach which supports ctor-injection into the IActionFilter. Also see hereKerr
L
15

I was having all sorts of grief with the WebApi2 and Ninject initialization after upgrading the Ninject packages (even uninstalling and deleting the old ones).

Specifically in your case I would remove these lines of code:

// Use the container and our NinjectDependencyResolver as
// application's resolver
var resolver = new NinjectDependencyResolver(container);
GlobalConfiguration.Configuration.DependencyResolver = resolver;

as they are probably the cause of the error (the NinjectWebCommon.cs and Ninject libraries deal with initializing the dependency resolver now).


For others out there who followed a similar upgrade path to me. What worked for me was the following:

  • Remove the old DependencyResolver initialization code (for me this was causing the specific error you mention as in earlier versions of Ninject/WebApi2, putting these lines in the WebApiConfig.cs Register() method was how you initialized the DependencyResolver...this no longer is the case):

    var kernel = new StandardKernel();
    config.DependencyResolver = new NinjectDependencyResolver(kernel);
    
  • Install the Ninject.Web.WebApi.WebHost package. This installed the NinjectWebCommon.cs file. For me, just having the Ninject.Web.WebApi and it's dependencies didn't create this file.

My installed and working Ninject Packages for reference:

<package id="Ninject" version="3.2.2.0" targetFramework="net452" />
<package id="Ninject.Web.Common" version="3.2.3.0" targetFramework="net452" />
<package id="Ninject.Web.Common.WebHost" version="3.2.0.0" targetFramework="net452" />
<package id="Ninject.Web.WebApi" version="3.2.3.0" targetFramework="net452" />
<package id="Ninject.Web.WebApi.WebHost" version="3.2.3.0" targetFramework="net452" />
Lukey answered 10/12, 2014 at 11:7 Comment(6)
where does the 'config' in the config.DependencyResolver come from?Reames
@Reames WebApiConfig.cs will have a method public static void Register(HttpConfiguration config) which is where the above 2 lines of code should go.Lukey
When I didn't have the Ninject.Web.WebApi.WebHost dependency, it would work locally but not when I published. Thanks!Shroud
Are you saying we should not set DependencyResolver at all? Looking at your "I would remove these lines of code" and "this no longer is the case". Does the dependency resolver get set automatically or some other way?Cobbie
I can confirm that adding these lines caused the problem to start happening. On the other hand, without these lines, dependency injection isn't even working: #30958889. Are you even using Ninject?Dessert
Regarding my comment above: I can definitely confirm that Ninject works without the bogus line (in one working application I have), but I no longer know why it works. Removing this line and installing all the packages mentioned in this post at least helped with making some progress (in a different application).Dessert
W
7

Be sure that any old Ninject or Ninject.Web.Common.* dlls aren't present in your bin folder.

I had the same issue in my solution after I had uninstalled Ninject.Web.Common, Ninject.Web.Common.WebHost, Ninject.Web.WebApi, and Ninject.MVC5 from Nuget and installed WebApiContrib.IoC.Ninject in order to use GlobalConfiguration.Configuration.DependencyResolver as in your example. I kept the version of Ninject that I already had installed (which was indeed 3.2.2).

The error did not appear when I first made my changes. However, after moving around from a few git branches and back to my current work, I saw the error. The code that had run fine last week was now throwing the same exact error.

It seems that my bin folder had references to the old Ninject.* packages I had removed. Upon deleting those files, my project worked as expected.

Win answered 5/7, 2016 at 16:27 Comment(1)
wow, i kept coming back to this SO until I realized that in publishing to Azure I was not removing the old dlls! Under Publish->Settings->File Publish Options you must check "Remove additional files at destination". Otherwise you'll find that everything works in localhost but not on Azure because the Ninject.Web.* are still there.Colunga
D
5

The cyclic dependency is between the classes "NinjectDefaultModelValidatorProvider" and "DefaultModelValidatorProviders".Simply add a binding for "DefaultModelValidatorProviders" on your startup like below:

_kernel.Bind<DefaultModelValidatorProviders>().ToConstant(new DefaultModelValidatorProviders(config.Services.GetServices(typeof (ModelValidatorProvider)).Cast<ModelValidatorProvider>()));
Dumbstruck answered 14/9, 2015 at 15:26 Comment(2)
where is config comming from ?Peppers
config is GlobalConfiguration.ConfigurationFulvia
S
3

In my case it was working just fine in Owin Selfhost context, but not when hosted in IIS. My solution was to remove all Ninject related assemblies from nuget packages except Ninject itself.

Then I wrote my own DependencyResolver class, feel free to leave improvements in the comments.

public class NinjectDepsolver : IDependencyResolver
{
    private IKernel _kernel;

    public NinjectDepsolver(IKernel kernel)
    {
        _kernel = kernel;
    }

    public void Dispose()
    {
        _kernel = null;
    }

    public object GetService(Type serviceType) => _kernel.TryGet(serviceType);

    public IEnumerable<object> GetServices(Type serviceType) => _kernel.GetAll(serviceType).ToArray();

    public IDependencyScope BeginScope() => new DepScope(this);

    class DepScope : IDependencyScope
    {
        private NinjectDepsolver _depsolver;

        public DepScope(NinjectDepsolver depsolver)
        {
            _depsolver = depsolver;
        }

        public void Dispose()
        {
            _depsolver = null;
        }

        public object GetService(Type serviceType) => _depsolver.GetService(serviceType);

        public IEnumerable<object> GetServices(Type serviceType) => _depsolver.GetServices(serviceType);
    }
}

And then in your Owin Configuration method:

var kernel = new StandardKernel();
kernel.Load(<your module classes>);
var httpConfig = new HttpConfiguration();
var httpConfig.DependencyResolver = new NinjectDepsolver(kernel);
var httpConfig.MapHttpAttributeRoutes();

app.UseWebApi(httpConfig);
Stemma answered 14/6, 2017 at 7:29 Comment(0)
B
2

I fixed this by adding the following line in Global.asax (where my StandardKernel was being initialized):

kernel.Bind<DefaultModelValidatorProviders>().ToConstant(new DefaultModelValidatorProviders(GlobalConfiguration.Configuration.Services.GetModelValidatorProviders()));
Baucom answered 10/5, 2019 at 14:54 Comment(0)
S
0

This is what worked for me.

uninstall-package Ninject.Web.WebApi.WebHost

The above command uninstalled the version 'Ninject.Web.WebApi.WebHost 3.2.4.0' and the error is gone!!

Just reconfirm, I have installed the same package using the command

install-package Ninject.Web.WebApi.WebHost

and the command installed the package 'Ninject.Web.WebApi.WebHost 3.2.4.0' and the error reappeared.

Scopula answered 6/7, 2017 at 6:26 Comment(0)
B
0
var _surveyBusiness = _kernel.Get<ISurveyBusiness>();
_surveyBusiness.SomeFunc(user.CompanyId, user.UserId);

This is working also.

Bradway answered 14/6, 2018 at 5:36 Comment(1)
Hello welcome to SO, can you clarify the logic behind your solution and why it works?Liripipe
A
-1

I have struggled with this in OWIN for a while and always ended up reverting to previous version. But nothing like checking the example application on their github.

First make sure you get rid of any manual Dependency Resolver you may be adding to the configuration, and then just do the following during your startup:

appBuilder.UseNinjectMiddleware(() => yourKernel); // or a function that returns your kernel
appBuilder.UseNinjectWebApi(yourHttConfiguration);

That should work fine.

Assurance answered 19/12, 2019 at 14:59 Comment(0)
A
-2

I uninstalled the package Ninject.Web.WebApi.WebHost and error is no more exists or occurred.

Acicular answered 26/6, 2020 at 4:56 Comment(0)
A
-2

I was getting same error and uninstalled package Ninject.Web.WebApi.WebHost and error removed.

Acicular answered 26/6, 2020 at 5:1 Comment(0)

© 2022 - 2024 — McMap. All rights reserved.