Bits of .NET

🛠️ The Build Configuration That Kept Undoing Itself

Visual Studio’s Solution Configuration dropdown is meant to be a simple, sticky choice – pick Release, and every subsequent build should use it until you change it again. In practice, several common actions quietly override that choice without any confirmation dialog: opening certain project types (especially ones targeting multiple platforms or using older project formats), running a specific launch profile that embeds its own configuration, or Visual Studio restoring a .suo-stored setting from before you last changed it. The dropdown shows Debug again, a Release build you thought you were making turns out to have been a Debug build all along, and nothing in the UI draws attention to the fact that it reverted.

🔎 The Problem

1. You open Solution Configurations dropdown, select "Release".
2. You build and deploy, assuming optimizations and Release-only
   settings are in effect.
3. Later, you notice debug symbols, unminified output, or
   Debug-only conditional code (#if DEBUG) behaving as if it were a
   Debug build - because the dropdown has silently shown "Debug"
   again at some point without you explicitly reselecting it.

Common silent triggers:
  - Switching the active Startup Project
  - Opening a solution with multiple projects that don't all define
    a "Release" configuration mapping, causing VS to fall back
  - A particular Launch Profile (launchSettings.json) implicitly
    tied to Debug being selected from the Run dropdown
  - The .vs folder's cached state from a previous session being
    restored on solution open

✅ Fix: Verify the Active Configuration Before Every Important Build, Don’t Trust the Last Setting You Remember

• Check the Solution Configuration dropdown immediately before any build you care about (especially before a deployment or a performance test), rather than relying on it having stayed where you last left it.
• Open the Build menu’s Configuration Manager to verify that every project in the solution actually has a Release configuration properly mapped – a project silently left mapped to Debug under an otherwise-Release solution configuration is a common source of this exact symptom.
• If the setting keeps reverting specifically after switching Startup Projects or Launch Profiles, check launchSettings.json and the project’s own default configuration settings for anything hardcoding Debug, since that’s a more deterministic cause than a simple UI glitch.

⚠️ Why This Is Easy to Miss

• The dropdown reverting produces no warning, no dialog, and no log entry – the only way to notice is to happen to glance at it again right before building, which isn’t most developers’ habit once they’ve set it the first time.
• A Debug build that’s deployed by mistake often still runs and looks correct functionally, so the problem surfaces later as an unexplained performance issue or an exposed debug feature rather than an obvious build failure.