ASP.NET Core 2.0：如何无需构造函数模式访问IOptions实例？

Great question! I’ve been in this exact spot before—needing to grab config values in an existing method without touching the class constructor. Here are a couple of practical approaches you can use:

1. Use IServiceProvider Directly in Your Method #

If your class has access to an IServiceProvider instance (super common in ASP.NET Core apps), you can resolve the IOptions<SomeOptions> directly in your method. For example, in an MVC controller:

public IActionResult YourExistingMethod()
{
    // Grab the options from the service provider
    var someOptions = HttpContext.RequestServices.GetRequiredService<IOptions<SomeOptions>>().Value;
    
    // Use your options here
    var apiUrl = someOptions.ApiBaseUrl;
    // ... rest of your logic
}

If you’re not in a controller, check if your class has access to a RequestServices property or can get an IServiceProvider instance from another injected dependency (even if it’s not explicitly declared in your constructor).

2. Static Service Provider Reference (Use Sparingly!) #

If you can’t get an IServiceProvider directly in your method, you can store a static reference to it during app startup. Note: This is a service locator anti-pattern, so only use this if you have no other choice.

First, update your startup code to save the provider:

public void ConfigureServices(IServiceCollection services)
{
    // Register your configuration section
    services.Configure<SomeOptions>(Configuration.GetSection("SomeOptions"));
    
    // Store the built service provider (only do this if absolutely necessary)
    var provider = services.BuildServiceProvider();
    YourTargetClass.ServiceProvider = provider;
}

Then in your existing class:

public class YourTargetClass
{
    // Static reference to the service provider
    public static IServiceProvider ServiceProvider { get; set; }

    public void YourExistingMethod()
    {
        var someOptions = ServiceProvider.GetRequiredService<IOptions<SomeOptions>>().Value;
        // Your logic here
    }
}

Just keep in mind this makes your code harder to test and couples it tightly to the DI container, so use it as a last resort.

3. Use IOptionsMonitor for Reloadable Configs #

If you need config values that can reload when the config file changes, you can resolve IOptionsMonitor<SomeOptions> instead of IOptions<T> using the same approaches above. It works the same way but gives you access to updated values without restarting the app:

var optionsMonitor = HttpContext.RequestServices.GetRequiredService<IOptionsMonitor<SomeOptions>>();
var currentOptions = optionsMonitor.CurrentValue;

内容的提问来源于stack exchange，提问作者schauhan