如何在不覆盖.NET Core内置配置的情况下启动自定义配置？

我在Visual Studio 2022中创建了launchSettings.json文件，通过启动设置下拉菜单快速切换数据库连接字符串等配置。

当前配置文件内容 #

launchSettings.json

{
  "iisSettings": {
    "iisExpress": {
      "applicationUrl": "http://localhost",
      "sslPort": 44392
    }
  },
  "profiles": {
    "Client_1": {
      "commandName": "IISExpress",
      "launchBrowser": true,
      "environmentVariables": {
        "ASPNETCORE_ENVIRONMENT": "Client_1_ENV"
      }
    },
    "Client_2": {
      "commandName": "Project",
      "launchBrowser": true,
      "applicationUrl": "https://localhost:5001;http://localhost:5000",
      "environmentVariables": {
        "ASPNETCORE_ENVIRONMENT": "Client_2_ENV"
      }
    }
  }
}

appsettings.client_1_ENV.json

{
  "ConnectionStrings": "db.client_1.com",
  "ASPNETCORE_ENVIRONMENT": "Development"
}

appsettings.client_2_ENV.json

{
  "ConnectionStrings": "db.client_2.com",
  "ASPNETCORE_ENVIRONMENT": "Production"
}

当前问题：由于launchsettings.json用ASPNETCORE_ENVIRONMENT作为关联appsettings的键，导致无法使用.NET Core内置的Development、Staging、Production等配置，代码及依赖无法响应这些内置环境设置，求解决办法。

方案一：新增自定义变量分离客户端与内置环境 #

保留ASPNETCORE_ENVIRONMENT为内置环境值，新增CLIENT_ENV变量区分客户端，扩展配置加载逻辑实现双维度配置叠加。

1. 修改launchSettings.json，调整环境变量配置：

{
  "iisSettings": {
    "iisExpress": {
      "applicationUrl": "http://localhost",
      "sslPort": 44392
    }
  },
  "profiles": {
    "Client_1 (Development)": {
      "commandName": "IISExpress",
      "launchBrowser": true,
      "environmentVariables": {
        "ASPNETCORE_ENVIRONMENT": "Development",
        "CLIENT_ENV": "Client_1"
      }
    },
    "Client_2 (Production)": {
      "commandName": "Project",
      "launchBrowser": true,
      "applicationUrl": "https://localhost:5001;http://localhost:5000",
      "environmentVariables": {
        "ASPNETCORE_ENVIRONMENT": "Production",
        "CLIENT_ENV": "Client_2"
      }
    }
  }
}

2. 重命名客户端配置文件为appsettings.Client_1.json、appsettings.Client_2.json。

3. 在Program.cs中扩展配置加载逻辑：

var builder = WebApplication.CreateBuilder(args);

// 读取自定义客户端环境变量并加载对应配置
var clientEnv = builder.Configuration["CLIENT_ENV"];
if (!string.IsNullOrEmpty(clientEnv))
{
    builder.Configuration.AddJsonFile(
        $"appsettings.{clientEnv}.json", 
        optional: true, 
        reloadOnChange: true
    );
}

// 后续服务注册与应用启动逻辑
var app = builder.Build();

配置优先级：客户端配置 > 内置环境配置（如appsettings.Development.json） > 基础appsettings.json，既保留客户端切换能力，又能让代码响应内置环境。

方案二：直接在launchSettings中覆盖客户端配置 #

无需额外配置文件，直接在launchSettings.json的环境变量中覆盖客户端特定配置，同时保留内置环境值。

修改后的launchSettings.json：

{
  "iisSettings": {
    "iisExpress": {
      "applicationUrl": "http://localhost",
      "sslPort": 44392
    }
  },
  "profiles": {
    "Client_1 (Development)": {
      "commandName": "IISExpress",
      "launchBrowser": true,
      "environmentVariables": {
        "ASPNETCORE_ENVIRONMENT": "Development",
        "ConnectionStrings:DefaultConnection": "db.client_1.com"
      }
    },
    "Client_2 (Production)": {
      "commandName": "Project",
      "launchBrowser": true,
      "applicationUrl": "https://localhost:5001;http://localhost:5000",
      "environmentVariables": {
        "ASPNETCORE_ENVIRONMENT": "Production",
        "ConnectionStrings:DefaultConnection": "db.client_2.com"
      }
    }
  }
}

这种方式无需修改代码，环境变量的配置优先级最高，直接覆盖基础配置中的连接字符串，同时ASPNETCORE_ENVIRONMENT保持内置值，代码依赖可正常响应。

方案三：自定义环境映射（兼容原有配置结构） #

如果想保留原有自定义环境名称（如Client_1_ENV），可在程序启动时将其映射为内置环境值，同时加载对应客户端配置。

修改Program.cs：

// 读取当前环境变量并映射为内置环境
var currentEnv = Environment.GetEnvironmentVariable("ASPNETCORE_ENVIRONMENT");
var envMapping = new Dictionary<string, string>
{
    {"Client_1_ENV", "Development"},
    {"Client_2_ENV", "Production"}
};

if (envMapping.TryGetValue(currentEnv, out var mappedEnv))
{
    Environment.SetEnvironmentVariable("ASPNETCORE_ENVIRONMENT", mappedEnv);
}

// 初始化构建器并加载自定义环境配置
var builder = WebApplication.CreateBuilder(args);
builder.Configuration.AddJsonFile(
    $"appsettings.{currentEnv}.json", 
    optional: true, 
    reloadOnChange: true
);

// 后续应用逻辑
var app = builder.Build();

此方案兼容原有launchSettings的切换方式，同时让代码识别到内置环境值，兼顾客户端配置与内置环境的响应能力。

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