Hi All, I am trying to work out the setup to build to run on a staging server vs local development and a production server.

The Staging server will have a different database (SQL Server) connection to a Production server.

I have a an appsettings.json and.. appsettings.Staging.json appsettings.Production.json With a different connection string in other two files.

I learned in the csproj file you can add the following code...

<Choose>
<When Condition="'$(Configuration)' == 'Staging'">
  <ItemGroup>
    <None Include="appsettings.Staging.json" CopyToOutputDirectory="Always" CopyToPublishDirectory="Always" />
    <None Include="appsettings.json" CopyToOutputDirectory="Never" CopyToPublishDirectory="Never" />
    <Content Remove="appsettings.*.json;appsettings.json" />
  </ItemGroup>
</When>
<When Condition="'$(Configuration)' == 'Production'">
  <ItemGroup>
    <None Include="appsettings.Production.json" CopyToOutputDirectory="Always" CopyToPublishDirectory="Always" />
    <None Include="appsettings.json" CopyToOutputDirectory="Never" CopyToPublishDirectory="Never" />
    <Content Remove="appsettings.*.json;appsettings.json" />
  </ItemGroup>
</When>
<Otherwise>
  <ItemGroup>
    <None Include="appsettings.json" CopyToOutputDirectory="Always" CopyToPublishDirectory="Always" />
    <!--<None Include="appsettings.Staging.json" CopyToOutputDirectory="Never" CopyToPublishDirectory="Never" />-->
  </ItemGroup>
</Otherwise>

So when I run the publish command there was only the right appsettings file. This did not work because on IIS it is looking for appsettings.json and that is required.

So I included both and they are there in the published file set. I then tested and edited the appsettings.json in the IIS folder with the wrong database and recycling the app pool I found the appsettings.json is always read. So how do I get different build's to have the different settings?

JSON example..

{
  "$schema": "appsettings-schema.json",
  "Serilog": {
    "MinimumLevel": {
      "Default": "Information"
    },
    "WriteTo": [
      {
        "Name": "Async",
        "Args": {
          "configure": [
            {
              "Name": "Console"
            }
          ]
        }
      }
    ]
  },
  "Umbraco": {
    "CMS": {
      "Content": {
        "MacroErrors": "Throw"
      },
      "Tours": {
        "EnableTours": false
      },
      "Hosting": {
        "Debug": true
      },
      "RuntimeMinification": {
        "UseInMemoryCache": true,
        "CacheBuster": "Timestamp"
      }
    }
  },
  "ConnectionStrings": {
    "umbracoDbDSN": "Server=bert.pretty.local;Database=umbraco11test;User Id=USER;Password=PASSWORD",
    "umbracoDbDSN_ProviderName": "Microsoft.Data.SqlClient"
  }
}

Can anyone help?

The goal:

• Being able to debug and work locally in the office connect to database.
• Publish for staging and have different settings like debugging on, different database etc.
• Publish for production and have settings where debug and like are off and a different database connection string.

I think I am close? There were a few things for .net7 but they are not how Umbraco setup and running on those guides kills Umbraco.