WebForms InRequestScope not working

[BloodBaz]

Hi,
I've raised this on Stack Overflow a couple of weeks ago but its not really drawing attention of anyone who knows what this issue is occurring. However, I do believe that InRequestScope isn't working for pages that implement IHttpHandler, [Inject] attributed properties or service locator injections.

The attached sample demonstrates a clean single page classic ASP.NET web application which uses Ninject.Web.Common.WebHost to bind a number of services using InRequestScope (see App_Start\NinjectWebCommon.cs) .

When the test page (TestPage.aspx) is requested and the root service (IServiceA) is requested, the downstream services are instantiated multiple times (see output log).

The same issue occurs for the test handler (TestHandler.ashx).

Furthermore, the [Inject] attribute on the property is not being set in the test page (TestPage.aspx).

NOTE: RegisterServices() is as follows:

	private static void RegisterServices(IKernel kernel)
	{
		kernel.Bind<Func<IKernel>>().ToMethod(ctx => () => new Bootstrapper().Kernel);
		kernel.Bind<IHttpModule>().To<HttpApplicationInitializationHttpModule>();

		kernel.Bind<IServiceA>().To<Services>().InRequestScope();
		kernel.Bind<IServiceB>().To<ServiceB>().InRequestScope();
		kernel.Bind<IServiceC>().To<ServiceC>().InRequestScope();
		kernel.Bind<IServiceD>().To<ServiceD>().InRequestScope();
		kernel.Bind<IServiceE>().To<ServiceE>().InRequestScope();
		kernel.Bind<IServiceF>().To<ServiceF>().InRequestScope();
	}

Requests for IServiceA reports this in the output log:

Constructing Service F
Constructing Service D
Constructing Service F
Constructing Service E
Constructing Service B
Constructing Service F
Constructing Service D
Constructing Service F
Constructing Service E
Constructing Service C
Constructing Service A

Expected output:

Constructing Service F
Constructing Service D
Constructing Service E
Constructing Service B
Constructing Service C
Constructing Service A

TestInRequestScopeWeb.zip

[scott-xu]

Did you try latest Ninject.Web?

[BloodBaz]

Interesting. I am using:

• Ninject.Web.Common.WebHost 3.3.2 (published 8th Febrary 2020)
• Ninject.Web.Common 3.3.2 (published 8th February 2020)
• Ninject 3.3.4 (published 13th November 2017)

Ninject.Web doesn't feature in this list although I can see version 3.3.0 (published 21st June 2020). If I install this one then which of the above package(s) does it replace? (I assume I don't just "add" this module. It would be super useful for the README.md (https://github.com/ninject/Ninject.Web) to include some information on what this packagemight replace or what service this package provides (currently just says "ASP.NET application bootstrapper for Ninject").

I'll have a look into this package and see if I can get it working. Thanks

Update
So, I've tried creating a new ASP.NET Framework Web Forms application and just add Ninject.Web 3.3.0 nuget package. I compile and run in debug mode (no binds yet) but

1. It executes the WebActivatorEx Start() method in App_Start\NinjectWebCommon.cs as expected; but then (and this is that bit that makes no sense to me on a number of levels...)
2. It attempts to run a second copy of Start() method in \obj\Release\net45\NuGet\C2BCC551415FC0CF557304FB71F1DCCF64D0EE64\Ninject.Web.Common.WebHost\3.3.2\App_Start\NinjectWebCommon.cs! This verison is in namespace Ninject.Web.App_Start instead of my project's namespace.App_start. I'm not even running in release mode!

The exception raised is (understandably) "System.NotSupportedException": 'The static container already has a kernel associated with it!'.

This is just an initial Web Forms application with Ninject.Web added via NuGet, so:

• Why would it be running code out of obj\Release?
• Why would it be trying to run a second copy of NinjectWebCommon.cs?
• What on earth is the C2BCC551415FC0CF557304FB71F1DCCF64D0EE64 folder about and what package put it there?
  I've never seen this before in a Web Forms application. Thanks.

[scott-xu]

Try Ninject.Web v3.3.1 please. Just like System.Web, Ninject.Web is primarily targeted to classic ASP.NET web application, which is web forms application.