Steven

And don't forget to post a full stack trace

Can you debug through your application and determine exactly after which line of code the scope is gone? e.g. is that after: * `var response = await this._client.ExecuteAsync(request).ConfigureAwait(false);` * or...

Sorry, that's not what I meant. It's clear to me where the exception is thrown, but there is a point in the application that Simple Injector's `Scope` is gone. This...

That likely means that there is something happening within RestSharp.RestClient that causes the asynchronous context not to flow. The most likely case is that it is using an `async foreach`...

> I've removed .ConfigureAwait(false) I didn't expect this. > However, I don't feel I should do it as it may cause deadlock at some background tasks that consumes this same...

[The discussion](https://github.com/simpleinjector/SimpleInjector.Integration.AspNetCore/issues/25) that you mentioned last actually contains code that, according to the OP, works.

> I just curios why it is not part of SimpleInjector default integration with .NET Core MVC? Mainly because of two reasons: 1. Due to the lack of good interception...

From the stack trace I understand that your custom `SimpleInjectorRazorpageActivator` calls into the `Microsoft.AspNetCore.Mvc.Razor.RazorPagePropertyActivator` class. This means that your custom `SimpleInjectorRazorpageActivator` does not correctly differentiate between dependencies that should be...

I think I'm starting to see the problem here. The implementation I proposed in [25](https://github.com/simpleinjector/SimpleInjector.Integration.AspNetCore/issues/25#issuecomment-1042932696), calls into the core behavior and let Simple Injector inject properties that are marked with...

As a matter of fact, Simple Injector already uses [DebuggerDisplay] [extensively](https://github.com/search?q=repo%3Asimpleinjector%2FSimpleInjector+%5BDebuggerDisplay&type=code). But I do agree with you, that a `DebuggerDisplayAttribute` would be a better fit here.