NinjectDependencyResolver无法绑定ModelValidatorProvider

我正在使用C#,.NET Framework 4.5.1开发ASP.NET Web Api 2.2。

更新我的Web.Api到Ninject 3.2.0后,我收到此错误:

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. 

我在NinjectWebCommon得到了exception:

 public static class NinjectWebCommon { private static readonly Bootstrapper bootstrapper = new Bootstrapper(); ///  /// Starts the application ///  public static void Start() { DynamicModuleUtility.RegisterModule(typeof(OnePerRequestHttpModule)); DynamicModuleUtility.RegisterModule(typeof(NinjectHttpModule)); bootstrapper.Initialize(CreateKernel); } ///  /// Stops the application. ///  public static void Stop() { bootstrapper.ShutDown(); } ///  /// Creates the kernel that will manage your application. ///  /// The created kernel. private static IKernel CreateKernel() { var kernel = new StandardKernel(); try { kernel.Bind<Func>().ToMethod(ctx => () => new Bootstrapper().Kernel); kernel.Bind().To(); RegisterServices(kernel); return kernel; } catch { kernel.Dispose(); throw; } } ///  /// Load your modules or register your services here! ///  /// The kernel. private static void RegisterServices(IKernel kernel) { var containerConfigurator = new NinjectConfigurator(); containerConfigurator.Configure(kernel); } } 

NinjectDependencyResolver类:

 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 GetServices(Type serviceType) { return _container.GetAll(serviceType); } public IDependencyScope BeginScope() { return this; } public void Dispose() { // noop } } } 

NinjectConfigurator类:

 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. } 

奇怪的是它编译并完美地工作,但更新后它不起作用。

我已经更改了这个public class NinjectDependencyResolver : IDependencyResolver, System.Web.Mvc.IDependencyResolver但它仍然不起作用。

任何的想法?

UPDATE

调试我看到NinjectDependencyResolver抛出了exception:

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

它跑了两次。 第一个serviceTypeIFilterProvider ,第二次serviceTypeModelValidatorProvider ,之后我得到了exception。

这些是我正在使用的Ninject包:

      

这些程序集的先前版本是:

      

第二次更新

我发现问题出现在这个类中:

 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() { return GetContainer().Get(); } } 

我在这里设置了Dependency Resolver

 public class NinjectConfigurator { ///  /// 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. ///  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; } 

我在一个inheritance自ExceptionFilterAttribute的类中使用WebContainerManager

 public class UnhandledExceptionFilter : ExceptionFilterAttribute { private readonly IExceptionLogHelper excepLogHelper; public UnhandledExceptionFilter() : this(WebContainerManager.Get()) {} public UnhandledExceptionFilter(IExceptionLogHelper exceptionLogHelper) { this.excepLogHelper = exceptionLogHelper; } public override void OnException(HttpActionExecutedContext actionExecutedContext) { this.excepLogHelper.LogException(actionExecutedContext); } } 

所以,如果我删除WebContainerManager我不会得到那个循环。

在升级Ninject软件包(甚至卸载和删除旧软件包)后,我对WebApi2和Ninject初始化产生了各种各样的悲痛。

特别是在你的情况下,我会删除这些代码行:

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

因为它们可能是错误的原因(NinjectWebCommon.cs和Ninject库现在处理初始化依赖项解析器)。


对于那些跟随类似升级路径的人来说。 对我有用的是:

  • 删除旧的DependencyResolver初始化代码(对我而言,这导致您在Ninject / WebApi2的早期版本中提到的特定错误,将这些行放在WebApiConfig.cs Register()方法中就是如何初始化DependencyResolver …这不再是是这样的):

     var kernel = new StandardKernel(); config.DependencyResolver = new NinjectDependencyResolver(kernel); 
  • 安装Ninject.Web.WebApi.WebHost包。 这安装了NinjectWebCommon.cs文件。 对我来说,只是拥有Ninject.Web.WebApi和它的依赖项并没有创建这个文件。

我安装和工作的Ninject包供参考:

      

确保bin文件夹中不存在任何旧的NinjectNinject.Web.Common.* dll。

我从Nuget卸载了Ninject.Web.CommonNinject.Web.Common.WebHostNinject.Web.WebApi和Ninject.MVC5并安装了WebApiContrib.IoC.Ninject以便使用GlobalConfiguration.Configuration.DependencyResolver后,我的解决方案出现了同样的问题。 GlobalConfiguration.Configuration.DependencyResolver在你的例子中。 我保留了我已安装的Ninject版本(确实是3.2.2 )。

我第一次进行更改时没有出现错误。 然而,在从几个git分支移动到我当前的工作后,我看到了错误。 上周运行良好的代码现在抛出了同样的错误。

似乎我的bin文件夹引用了我删除的旧Ninject.*包。 删除这些文件后,我的项目按预期工作。

循环依赖在类“NinjectDefaultModelValidatorProvider”和“DefaultModelValidatorProviders”之间。在您的启动中为“DefaultModelValidatorProviders”添加一个绑定,如下所示:

 _kernel.Bind ()。ToConstant(new DefaultModelValidatorProviders(config.Services.GetServices(typeof(ModelValidatorProvider))。Cast ()));

在我的情况下,它在Owin Selfhost上下文中运行得很好,但在IIS中托管时却没有。 我的解决方案是从nuget包中删除除Ninject本身之外的所有Ninject相关程序集。

然后我编写了自己的DependencyResolver类,随意在评论中留下改进。

 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 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 GetServices(Type serviceType) => _depsolver.GetServices(serviceType); } } 

然后在你的Owin配置方法中:

 var kernel = new StandardKernel(); kernel.Load(); var httpConfig = new HttpConfiguration(); var httpConfig.DependencyResolver = new NinjectDepsolver(kernel); var httpConfig.MapHttpAttributeRoutes(); app.UseWebApi(httpConfig); 

这对我有用。

uninstall-package Ninject.Web.WebApi.WebHost

上面的命令卸载了版本’Ninject.Web.WebApi.WebHost 3.2.4.0’,错误消失了!!

请再次确认,我已使用该命令安装了相同的软件包

install-package Ninject.Web.WebApi.WebHost

并且命令安装了包’Ninject.Web.WebApi.WebHost 3.2.4.0’并且错误再次出现。

 var _surveyBusiness = _kernel.Get(); _surveyBusiness.SomeFunc(user.CompanyId, user.UserId); 

这也有效。