IApplicationBuilder.ApplicationServices instance, returns different scoped services/objects from 'HttpContext.RequestServices instance

[jlVidal]

Suppose that I registered a scoped service.

services.AddScoped<IMyService, MyService>();

Now, consider the following scenario... On startup class:

app.Map("/test", level2 =>
{
    level2.Use(
                    a =>
                    {
                        return (b =>
                        {
                                var instance = context.RequestServices.GetService<IMyService>();
                                DoSomething(instance);

                            return a.Invoke(b);
                        });
                    });
    });

     level2.UseStaticFiles(new StaticFileOptions
                   {
                       FileProvider = new MyFileProvider(level2.ApplicationServices);
                   });
}

Consider that I'm trying to use IMyService implementation inside of MyFileProvider, but that would happen just when a request comes in. During the same request as the "Use" method, the MyService instance is being created again (same request/same thread, just accessed by IServiceProvider (from IApplicationBuilder.ApplicationServices) instead of IServiceProvider (from HttpContext.RequestServices).

Anyway, since the service was defined scoped. Is that supposed to be a normal behavior?

[muratg]

I believe this is the current design. Services taken from ApplicationServices is not scoped. Does it break any common scenario for you?

[khellang]

Actually, the service resolved from ApplicationServices ends up being a singleton, because the container is never disposed (before app shutdown). This is called a captive dependency and will throw an exception in v1.1. See aspnet/DependencyInjection#430

A scoped instance is always resolved from the provider you're asking, and disposed when the same provider is disposed. There's no shared, scoped instances between providers.

[Eilon]

We are closing this issue because no further action is planned for this issue. If you still have any issues or questions, please log a new issue with any additional details that you have.