Options lifecycle in ASP.NET Core dependency injection

Question

Which lifetime cycle has the configuration object got when it's registered the following way? Is it a singleton, transient or scoped?

  {
      services.Configure<SomeConfiguration>(configuration.GetSection(nameof(SomeConfiguration)));
  }

This is how I get the configuration into my service class

public class SomeService: ISomeService
{
    public SomeService(IOptionsMonitor<SomeConfiguration> configuration)
    {
         _configuration = configuration.CurrentValue;
    }
}

Its is very to hard know from debugging it if its a singleton or not. Because IOptionsMonitor is able to detect changes on run time by running a watcher on appsettings.json changed

Answer 1

IOptions

• Is registered as a Singleton and can be injected into any service lifetime.

IOptionsSnapshot:

• Is useful in scenarios where options should be recomputed on every request.
• Is registered as Scoped and therefore cannot be injected into a Singleton service.

IOptionsMonitor:

• Is used to retrieve options and manage options notifications for TOptions instances.
• Is registered as a Singleton and can be injected into any service lifetime.

Reference