Should the ApplicationBuilder behave differently between Microsoft.NET.Sdk and Microsoft.NET.Sdk.Worker??

Question

I've noticed if my project file references Microsoft.NET.Sdk, then the ApplicationBuilder does NOT automatically load the appsettings.json file, but if the project file references Microsoft.NET.Sdk.Worker, then it does.

I've noticed this has occurred while creating an application in .NET 8.0.
It does feel like an important change in behaviour with a very subtle difference.

Is it intentional?

Thoughts???

Answer 1

Hello hope your doing well. thanks for reaching out!

Two SDKs, Two Behaviors

• Microsoft.NET.Sdk: Basic SDK for console apps.
• Microsoft.NET.Sdk.Worker: Designed for background services with built-in hosting.
• Configuration Loading
• Microsoft.NET.Sdk: Does not load appsettings.json automatically.
  • Microsoft.NET.Sdk.Worker: Does load appsettings.json by default.
  • Why the Difference?
  • Worker SDK uses Host.CreateApplicationBuilder() which sets up:

       - Configuration (including `appsettings.json`)
    
                - Logging
    
                         - Dependency Injection
    

    • Basic SDK does not include this setup unless you add it manually.
    • How to Fix It in Microsoft.NET.Sdk
• Add this code to load configuration manually
• var builder = Host.CreateApplicationBuilder(args); builder.Configuration.AddJsonFile("appsettings.json", optional: true, reloadOnChange: true); var app = builder.Build();
• Is It Intentional?
• Yes, it’s by design in .NET 8.
• Each SDK has different defaults based on its purpose.