Service Fabric中ASP.NET Core配置注入不完全问题求助

Let's break down why your configuration isn't fully integrating with the ASP.NET Core framework in Service Fabric, and how to fix it:

Root Cause #

Your Service Fabric service's WebHostBuilder is built from scratch instead of using WebHost.CreateDefaultBuilder(), which skips all the default configuration and logging setup that standard ASP.NET Core projects rely on.

In your standalone test project, WebHost.CreateDefaultBuilder() handles:

• Loading default configuration sources (appsettings.json, environment variables, command line args)
• Configuring the logging system to read settings from the Logging configuration node
• Auto-configuring Application Insights if an instrumentation key is present in configuration

Without this foundation, your custom ServiceFabricConfigurationProvider adds settings, but the framework doesn't have the built-in logic to pick them up for components like logging or Application Insights.

Fix: Use WebHost.CreateDefaultBuilder() as Your Base #

Modify your CreateServiceInstanceListeners method to use the default builder, then layer your Service Fabric configuration on top:

protected override IEnumerable<ServiceInstanceListener> CreateServiceInstanceListeners()
{
    return new[]
    {
        new ServiceInstanceListener(serviceContext =>
            new KestrelCommunicationListener(serviceContext, "ServiceEndpoint", (url, listener) =>
            {
                ServiceEventSource.Current.ServiceMessage(serviceContext, $"Starting Kestrel on {url}");
                
                return WebHost.CreateDefaultBuilder()
                    .UseKestrel()
                    .ConfigureServices(services => services.AddSingleton(serviceContext))
                    .ConfigureAppConfiguration(builder =>
                    {
                        // Add Service Fabric configuration AFTER default sources to let it override defaults
                        builder.AddServiceFabricConfiguration(serviceContext);
                    })
                    .UseContentRoot(Directory.GetCurrentDirectory())
                    .UseStartup<Startup>()
                    .UseServiceFabricIntegration(listener, ServiceFabricIntegrationOptions.UseReverseProxyIntegration)
                    .UseUrls(url)
                    .Build();
            }))
    };
}

Key Changes Explained #

1. WebHost.CreateDefaultBuilder(): This brings back all the standard ASP.NET Core configuration and logging setup. Your Service Fabric settings will now merge with these defaults.
2. Order of Configuration Sources: By adding AddServiceFabricConfiguration after the default sources, any duplicate keys in your Service Fabric config will override values from appsettings or environment variables (adjust the order if you need the reverse behavior).
3. Automatic Component Configuration:
   • Logging levels from your Service Fabric config will now be picked up automatically by the framework's logging system.
   • Application Insights will use the instrumentation key from your config without needing an explicit services.AddApplicationInsightsTelemetry(Configuration) call.

Debugging Tip #

If you still run into issues, verify that your Service Fabric configuration is being loaded correctly by dumping the full configuration set in your Startup.Configure method:

public void Configure(IApplicationBuilder app, IWebHostEnvironment env, IConfiguration configuration)
{
    // Debug: Print all configuration key-value pairs
    foreach (var configEntry in configuration.AsEnumerable())
    {
        ServiceEventSource.Current.ServiceMessage(null, $"{configEntry.Key}: {configEntry.Value}");
    }

    // Rest of your Configure logic...
}

This will help you confirm if your Service Fabric settings are actually present in the configuration collection.

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