This question is locked. New answers and comments are not allowed.
Hi,
I am trying to get Ninject and Telerik MVC Grid (ajax mode) working together. I am binding DbContext (Entity Framework) using Ninject kernel in request scope so that it can be resolved and used throughout the application for a particular request. The problem is that the Ninject deactivator code starts executing even before the [GridAction] attribute handler gets a chance to handle the response. Typically this occurs when the "return View(new GridModel())" is executed.
I looked up the ninject code and it hooks the Ninject Deactivation code to the HttpApplication.EndRequest event, which seems logical. Why is the [GridAction] attribute handler called after the firing of EndRequest event of HttpApplication.
regards,
Nirvan.
I am trying to get Ninject and Telerik MVC Grid (ajax mode) working together. I am binding DbContext (Entity Framework) using Ninject kernel in request scope so that it can be resolved and used throughout the application for a particular request. The problem is that the Ninject deactivator code starts executing even before the [GridAction] attribute handler gets a chance to handle the response. Typically this occurs when the "return View(new GridModel())" is executed.
I looked up the ninject code and it hooks the Ninject Deactivation code to the HttpApplication.EndRequest event, which seems logical. Why is the [GridAction] attribute handler called after the firing of EndRequest event of HttpApplication.
regards,
Nirvan.