No parametless constructor defined Hangfire Ninject











up vote
0
down vote

favorite












I'm having a problem activating instance of my class with no parametless constructor defined.



The constructor:



public HangfireExecutor(ICommandDispatcher commandDispatcher, IQueryDispatcher queryDispatcher, IMapper mapper)


How I register and configure Hangfire (three dots are used instead of sensitive info):



[assembly: OwinStartupAttribute(typeof(Web2.Startup))]
public partial class Startup

private IAppBuilder _app;
public void Configuration(IAppBuilder app)
{
ConfigureAuth(app);
_app = app;

GlobalConfiguration.Configuration.UseSqlServerStorage("...");

_app.UseHangfireDashboard("/...", new DashboardOptions
{
Authorization = new { new HangfireDashboardAuthorizationFilter() },
AppPath = "/Identity/Create"
});

_app.UseHangfireServer();

_app.UseNinjectMiddleware(CreateKernel);
}


Registration in IoC container:



public partial class Startup
{
...
protected IKernel CreateKernel()
{
var kernel = new StandardKernel();
...
kernel.Bind<HangfireExecutor>().ToSelf().InBackgroundJobScope();
GlobalConfiguration.Configuration.UseNinjectActivator(kernel);
return kernel;


The error:



System.MissingMethodException
No parameterless constructor defined for this object hangfire ninject System.RuntimeTypeHandle.CreateInstance
System.MissingMethodException: No parameterless constructor defined for this object
at System.RuntimeTypeHandle.CreateInstance(RuntimeType type, Boolean publicOnly, Boolean noCheck, Boolean& canBeCached, RuntimeMethodHandleInternal& ctor, Boolean& bNeedSecurityCheck)
at System.RuntimeType.CreateInstanceSlow(Boolean publicOnly, Boolean skipCheckThis, Boolean fillCache, StackCrawlMark& stackMark)
at System.RuntimeType.CreateInstanceDefaultCtor(Boolean publicOnly, Boolean skipCheckThis, Boolean fillCache, StackCrawlMark& stackMark)
at System.Activator.CreateInstance(Type type, Boolean nonPublic)
at System.Activator.CreateInstance(Type type)
at Hangfire.JobActivator.ActivateJob(Type jobType)
at Hangfire.JobActivator.SimpleJobActivatorScope.Resolve(Type type)
at Hangfire.Server.CoreBackgroundJobPerformer.Perform(PerformContext context)


For me it looks like the Hangfire does not use Ninject activator (?) but I don't know why.



I've followed both tutorials: on Hangfire site and Hangfire.Ninject github and several github repos and SO questions.



Instatiating other classes not used by Hangfire works well; also instatiating Hangfire executor with parametless constructor works properly.



I'm using:




  • ASP .NET MVC 5

  • .NET Framework 4.6.1,

  • Hangfire 1.6.21

  • Hangfire.Ninject 1.2










share|improve this question


























    up vote
    0
    down vote

    favorite












    I'm having a problem activating instance of my class with no parametless constructor defined.



    The constructor:



    public HangfireExecutor(ICommandDispatcher commandDispatcher, IQueryDispatcher queryDispatcher, IMapper mapper)


    How I register and configure Hangfire (three dots are used instead of sensitive info):



    [assembly: OwinStartupAttribute(typeof(Web2.Startup))]
    public partial class Startup

    private IAppBuilder _app;
    public void Configuration(IAppBuilder app)
    {
    ConfigureAuth(app);
    _app = app;

    GlobalConfiguration.Configuration.UseSqlServerStorage("...");

    _app.UseHangfireDashboard("/...", new DashboardOptions
    {
    Authorization = new { new HangfireDashboardAuthorizationFilter() },
    AppPath = "/Identity/Create"
    });

    _app.UseHangfireServer();

    _app.UseNinjectMiddleware(CreateKernel);
    }


    Registration in IoC container:



    public partial class Startup
    {
    ...
    protected IKernel CreateKernel()
    {
    var kernel = new StandardKernel();
    ...
    kernel.Bind<HangfireExecutor>().ToSelf().InBackgroundJobScope();
    GlobalConfiguration.Configuration.UseNinjectActivator(kernel);
    return kernel;


    The error:



    System.MissingMethodException
    No parameterless constructor defined for this object hangfire ninject System.RuntimeTypeHandle.CreateInstance
    System.MissingMethodException: No parameterless constructor defined for this object
    at System.RuntimeTypeHandle.CreateInstance(RuntimeType type, Boolean publicOnly, Boolean noCheck, Boolean& canBeCached, RuntimeMethodHandleInternal& ctor, Boolean& bNeedSecurityCheck)
    at System.RuntimeType.CreateInstanceSlow(Boolean publicOnly, Boolean skipCheckThis, Boolean fillCache, StackCrawlMark& stackMark)
    at System.RuntimeType.CreateInstanceDefaultCtor(Boolean publicOnly, Boolean skipCheckThis, Boolean fillCache, StackCrawlMark& stackMark)
    at System.Activator.CreateInstance(Type type, Boolean nonPublic)
    at System.Activator.CreateInstance(Type type)
    at Hangfire.JobActivator.ActivateJob(Type jobType)
    at Hangfire.JobActivator.SimpleJobActivatorScope.Resolve(Type type)
    at Hangfire.Server.CoreBackgroundJobPerformer.Perform(PerformContext context)


    For me it looks like the Hangfire does not use Ninject activator (?) but I don't know why.



    I've followed both tutorials: on Hangfire site and Hangfire.Ninject github and several github repos and SO questions.



    Instatiating other classes not used by Hangfire works well; also instatiating Hangfire executor with parametless constructor works properly.



    I'm using:




    • ASP .NET MVC 5

    • .NET Framework 4.6.1,

    • Hangfire 1.6.21

    • Hangfire.Ninject 1.2










    share|improve this question
























      up vote
      0
      down vote

      favorite









      up vote
      0
      down vote

      favorite











      I'm having a problem activating instance of my class with no parametless constructor defined.



      The constructor:



      public HangfireExecutor(ICommandDispatcher commandDispatcher, IQueryDispatcher queryDispatcher, IMapper mapper)


      How I register and configure Hangfire (three dots are used instead of sensitive info):



      [assembly: OwinStartupAttribute(typeof(Web2.Startup))]
      public partial class Startup

      private IAppBuilder _app;
      public void Configuration(IAppBuilder app)
      {
      ConfigureAuth(app);
      _app = app;

      GlobalConfiguration.Configuration.UseSqlServerStorage("...");

      _app.UseHangfireDashboard("/...", new DashboardOptions
      {
      Authorization = new { new HangfireDashboardAuthorizationFilter() },
      AppPath = "/Identity/Create"
      });

      _app.UseHangfireServer();

      _app.UseNinjectMiddleware(CreateKernel);
      }


      Registration in IoC container:



      public partial class Startup
      {
      ...
      protected IKernel CreateKernel()
      {
      var kernel = new StandardKernel();
      ...
      kernel.Bind<HangfireExecutor>().ToSelf().InBackgroundJobScope();
      GlobalConfiguration.Configuration.UseNinjectActivator(kernel);
      return kernel;


      The error:



      System.MissingMethodException
      No parameterless constructor defined for this object hangfire ninject System.RuntimeTypeHandle.CreateInstance
      System.MissingMethodException: No parameterless constructor defined for this object
      at System.RuntimeTypeHandle.CreateInstance(RuntimeType type, Boolean publicOnly, Boolean noCheck, Boolean& canBeCached, RuntimeMethodHandleInternal& ctor, Boolean& bNeedSecurityCheck)
      at System.RuntimeType.CreateInstanceSlow(Boolean publicOnly, Boolean skipCheckThis, Boolean fillCache, StackCrawlMark& stackMark)
      at System.RuntimeType.CreateInstanceDefaultCtor(Boolean publicOnly, Boolean skipCheckThis, Boolean fillCache, StackCrawlMark& stackMark)
      at System.Activator.CreateInstance(Type type, Boolean nonPublic)
      at System.Activator.CreateInstance(Type type)
      at Hangfire.JobActivator.ActivateJob(Type jobType)
      at Hangfire.JobActivator.SimpleJobActivatorScope.Resolve(Type type)
      at Hangfire.Server.CoreBackgroundJobPerformer.Perform(PerformContext context)


      For me it looks like the Hangfire does not use Ninject activator (?) but I don't know why.



      I've followed both tutorials: on Hangfire site and Hangfire.Ninject github and several github repos and SO questions.



      Instatiating other classes not used by Hangfire works well; also instatiating Hangfire executor with parametless constructor works properly.



      I'm using:




      • ASP .NET MVC 5

      • .NET Framework 4.6.1,

      • Hangfire 1.6.21

      • Hangfire.Ninject 1.2










      share|improve this question













      I'm having a problem activating instance of my class with no parametless constructor defined.



      The constructor:



      public HangfireExecutor(ICommandDispatcher commandDispatcher, IQueryDispatcher queryDispatcher, IMapper mapper)


      How I register and configure Hangfire (three dots are used instead of sensitive info):



      [assembly: OwinStartupAttribute(typeof(Web2.Startup))]
      public partial class Startup

      private IAppBuilder _app;
      public void Configuration(IAppBuilder app)
      {
      ConfigureAuth(app);
      _app = app;

      GlobalConfiguration.Configuration.UseSqlServerStorage("...");

      _app.UseHangfireDashboard("/...", new DashboardOptions
      {
      Authorization = new { new HangfireDashboardAuthorizationFilter() },
      AppPath = "/Identity/Create"
      });

      _app.UseHangfireServer();

      _app.UseNinjectMiddleware(CreateKernel);
      }


      Registration in IoC container:



      public partial class Startup
      {
      ...
      protected IKernel CreateKernel()
      {
      var kernel = new StandardKernel();
      ...
      kernel.Bind<HangfireExecutor>().ToSelf().InBackgroundJobScope();
      GlobalConfiguration.Configuration.UseNinjectActivator(kernel);
      return kernel;


      The error:



      System.MissingMethodException
      No parameterless constructor defined for this object hangfire ninject System.RuntimeTypeHandle.CreateInstance
      System.MissingMethodException: No parameterless constructor defined for this object
      at System.RuntimeTypeHandle.CreateInstance(RuntimeType type, Boolean publicOnly, Boolean noCheck, Boolean& canBeCached, RuntimeMethodHandleInternal& ctor, Boolean& bNeedSecurityCheck)
      at System.RuntimeType.CreateInstanceSlow(Boolean publicOnly, Boolean skipCheckThis, Boolean fillCache, StackCrawlMark& stackMark)
      at System.RuntimeType.CreateInstanceDefaultCtor(Boolean publicOnly, Boolean skipCheckThis, Boolean fillCache, StackCrawlMark& stackMark)
      at System.Activator.CreateInstance(Type type, Boolean nonPublic)
      at System.Activator.CreateInstance(Type type)
      at Hangfire.JobActivator.ActivateJob(Type jobType)
      at Hangfire.JobActivator.SimpleJobActivatorScope.Resolve(Type type)
      at Hangfire.Server.CoreBackgroundJobPerformer.Perform(PerformContext context)


      For me it looks like the Hangfire does not use Ninject activator (?) but I don't know why.



      I've followed both tutorials: on Hangfire site and Hangfire.Ninject github and several github repos and SO questions.



      Instatiating other classes not used by Hangfire works well; also instatiating Hangfire executor with parametless constructor works properly.



      I'm using:




      • ASP .NET MVC 5

      • .NET Framework 4.6.1,

      • Hangfire 1.6.21

      • Hangfire.Ninject 1.2







      asp.net-mvc-5 ninject hangfire .net-4.6.1 hangfire.ninject






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Nov 21 at 12:26









      ignacy130

      1821115




      1821115
























          1 Answer
          1






          active

          oldest

          votes

















          up vote
          0
          down vote



          accepted










          As method _app.UseNinjectMiddleware(CreateKernel); does not create kernel (just keeps delegate to the metod creating the kernel) the correct order of commands in Hangfire configuration in my case should be:



          public void Configuration(IAppBuilder app)
          {
          ConfigureAuth(app);
          _app = app;

          GlobalConfiguration.Configuration.UseSqlServerStorage("...");

          _app.UseHangfireDashboard("/...", new DashboardOptions
          {
          Authorization = new { new HangfireDashboardAuthorizationFilter() },
          AppPath = "/Identity/Create"
          });

          _app.UseNinjectMiddleware(CreateKernel);
          }


          and then at the end of CreateKernel method:



          kernel.Bind<HangfireExecutor>().ToSelf().InBackgroundJobScope();

          GlobalConfiguration.Configuration.UseNinjectActivator(kernel);

          _app.UseHangfireServer();

          return kernel;


          Now Hangfire started resolving dependencies. I think that it is important to create kernel as soon after starting the app as possible - otherwise Hangfire may not be initialized and background jobs will not be executed.






          share|improve this answer























            Your Answer






            StackExchange.ifUsing("editor", function () {
            StackExchange.using("externalEditor", function () {
            StackExchange.using("snippets", function () {
            StackExchange.snippets.init();
            });
            });
            }, "code-snippets");

            StackExchange.ready(function() {
            var channelOptions = {
            tags: "".split(" "),
            id: "1"
            };
            initTagRenderer("".split(" "), "".split(" "), channelOptions);

            StackExchange.using("externalEditor", function() {
            // Have to fire editor after snippets, if snippets enabled
            if (StackExchange.settings.snippets.snippetsEnabled) {
            StackExchange.using("snippets", function() {
            createEditor();
            });
            }
            else {
            createEditor();
            }
            });

            function createEditor() {
            StackExchange.prepareEditor({
            heartbeatType: 'answer',
            convertImagesToLinks: true,
            noModals: true,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: 10,
            bindNavPrevention: true,
            postfix: "",
            imageUploader: {
            brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
            contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
            allowUrls: true
            },
            onDemand: true,
            discardSelector: ".discard-answer"
            ,immediatelyShowMarkdownHelp:true
            });


            }
            });














            draft saved

            draft discarded


















            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53412014%2fno-parametless-constructor-defined-hangfire-ninject%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown

























            1 Answer
            1






            active

            oldest

            votes








            1 Answer
            1






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes








            up vote
            0
            down vote



            accepted










            As method _app.UseNinjectMiddleware(CreateKernel); does not create kernel (just keeps delegate to the metod creating the kernel) the correct order of commands in Hangfire configuration in my case should be:



            public void Configuration(IAppBuilder app)
            {
            ConfigureAuth(app);
            _app = app;

            GlobalConfiguration.Configuration.UseSqlServerStorage("...");

            _app.UseHangfireDashboard("/...", new DashboardOptions
            {
            Authorization = new { new HangfireDashboardAuthorizationFilter() },
            AppPath = "/Identity/Create"
            });

            _app.UseNinjectMiddleware(CreateKernel);
            }


            and then at the end of CreateKernel method:



            kernel.Bind<HangfireExecutor>().ToSelf().InBackgroundJobScope();

            GlobalConfiguration.Configuration.UseNinjectActivator(kernel);

            _app.UseHangfireServer();

            return kernel;


            Now Hangfire started resolving dependencies. I think that it is important to create kernel as soon after starting the app as possible - otherwise Hangfire may not be initialized and background jobs will not be executed.






            share|improve this answer



























              up vote
              0
              down vote



              accepted










              As method _app.UseNinjectMiddleware(CreateKernel); does not create kernel (just keeps delegate to the metod creating the kernel) the correct order of commands in Hangfire configuration in my case should be:



              public void Configuration(IAppBuilder app)
              {
              ConfigureAuth(app);
              _app = app;

              GlobalConfiguration.Configuration.UseSqlServerStorage("...");

              _app.UseHangfireDashboard("/...", new DashboardOptions
              {
              Authorization = new { new HangfireDashboardAuthorizationFilter() },
              AppPath = "/Identity/Create"
              });

              _app.UseNinjectMiddleware(CreateKernel);
              }


              and then at the end of CreateKernel method:



              kernel.Bind<HangfireExecutor>().ToSelf().InBackgroundJobScope();

              GlobalConfiguration.Configuration.UseNinjectActivator(kernel);

              _app.UseHangfireServer();

              return kernel;


              Now Hangfire started resolving dependencies. I think that it is important to create kernel as soon after starting the app as possible - otherwise Hangfire may not be initialized and background jobs will not be executed.






              share|improve this answer

























                up vote
                0
                down vote



                accepted







                up vote
                0
                down vote



                accepted






                As method _app.UseNinjectMiddleware(CreateKernel); does not create kernel (just keeps delegate to the metod creating the kernel) the correct order of commands in Hangfire configuration in my case should be:



                public void Configuration(IAppBuilder app)
                {
                ConfigureAuth(app);
                _app = app;

                GlobalConfiguration.Configuration.UseSqlServerStorage("...");

                _app.UseHangfireDashboard("/...", new DashboardOptions
                {
                Authorization = new { new HangfireDashboardAuthorizationFilter() },
                AppPath = "/Identity/Create"
                });

                _app.UseNinjectMiddleware(CreateKernel);
                }


                and then at the end of CreateKernel method:



                kernel.Bind<HangfireExecutor>().ToSelf().InBackgroundJobScope();

                GlobalConfiguration.Configuration.UseNinjectActivator(kernel);

                _app.UseHangfireServer();

                return kernel;


                Now Hangfire started resolving dependencies. I think that it is important to create kernel as soon after starting the app as possible - otherwise Hangfire may not be initialized and background jobs will not be executed.






                share|improve this answer














                As method _app.UseNinjectMiddleware(CreateKernel); does not create kernel (just keeps delegate to the metod creating the kernel) the correct order of commands in Hangfire configuration in my case should be:



                public void Configuration(IAppBuilder app)
                {
                ConfigureAuth(app);
                _app = app;

                GlobalConfiguration.Configuration.UseSqlServerStorage("...");

                _app.UseHangfireDashboard("/...", new DashboardOptions
                {
                Authorization = new { new HangfireDashboardAuthorizationFilter() },
                AppPath = "/Identity/Create"
                });

                _app.UseNinjectMiddleware(CreateKernel);
                }


                and then at the end of CreateKernel method:



                kernel.Bind<HangfireExecutor>().ToSelf().InBackgroundJobScope();

                GlobalConfiguration.Configuration.UseNinjectActivator(kernel);

                _app.UseHangfireServer();

                return kernel;


                Now Hangfire started resolving dependencies. I think that it is important to create kernel as soon after starting the app as possible - otherwise Hangfire may not be initialized and background jobs will not be executed.







                share|improve this answer














                share|improve this answer



                share|improve this answer








                edited Nov 22 at 14:49

























                answered Nov 22 at 8:50









                ignacy130

                1821115




                1821115






























                    draft saved

                    draft discarded




















































                    Thanks for contributing an answer to Stack Overflow!


                    • Please be sure to answer the question. Provide details and share your research!

                    But avoid



                    • Asking for help, clarification, or responding to other answers.

                    • Making statements based on opinion; back them up with references or personal experience.


                    To learn more, see our tips on writing great answers.





                    Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


                    Please pay close attention to the following guidance:


                    • Please be sure to answer the question. Provide details and share your research!

                    But avoid



                    • Asking for help, clarification, or responding to other answers.

                    • Making statements based on opinion; back them up with references or personal experience.


                    To learn more, see our tips on writing great answers.




                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function () {
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53412014%2fno-parametless-constructor-defined-hangfire-ninject%23new-answer', 'question_page');
                    }
                    );

                    Post as a guest















                    Required, but never shown





















































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown

































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown







                    Popular posts from this blog

                    Berounka

                    Sphinx de Gizeh

                    Different font size/position of beamer's navigation symbols template's content depending on regular/plain...