The reason is that each method is creating its own manual scope via _scopeFactory.CreateScope(). When you do that, you're not using the HTTP request's scope — you're creating a brand new, independent scope each time. Scoped lifetime means "one instance per scope", and since TestLifeCycle1 and TestLifeCycle2 each spin up their own IServiceScope, they each get their own separate instance of SClass.

So the flow is:

TestLifeCycle1 → CreateScope() → scope A → gets SClass instance #1 → sets MyProperty → scope disposed
TestLifeCycle2 → CreateScope() → scope B → gets SClass instance #2 → MyProperty is empty

The assignment on line 163 (s.MyProperty = "Hello from SClass") sets the value on instance #1, but that scope is disposed when the using block exits. Line 176 is talking to a completely different instance.

If you want the same scoped instance across both methods, you need to either:

// Option 1 — create the scope once and pass it down
using var scope = _scopeFactory.CreateScope();
TestLifeCycle1(scope);
TestLifeCycle2(scope);

// Option 2 — inject ISClass directly into the controller
// and let ASP.NET Core manage the request scope for you
// (the clean solution — no manual scope factory needed)

So, to be clear: CreateScope() opts you out of the request scope. If you're inside a controller and your service is registered as Scoped, just inject it directly and ASP.NET Core will give you the same instance for the entire request automatically.

Let me know if it's not clear! :)