IntegratedConsoleDebugging project capability not respected

Visual Studio Version: 16.2.0

Project Type ASP .Net Core 2.2

Summary: There is an ‘IntegratedConsoleDebugging’ project capability that could be detected to decide whether or not to launch inside the integrated console, but it isn’t used. See issue 3667 (which indicates that the ‘IntegratedConsoleDebugging’ should be used) and the resolution (which doesn’t check for the project capability)

The only way to opt out of the integrated console debugging experience appears to be to select the ‘Automatically close the console when debugging stops’ debug option.

Expected Behavior: Check the project capabilities to see if ‘IntegratedConsoleDebugging’ is included. If not, expect that the app will not be launched for debugging in the integrated console.

Actual Behavior: Regardless of whether or not the app has ‘IntegratedConsoleDebugging’ project capability specified, it ends up being launched for debugging in the integrated console.

User Impact: The ‘Automatically close the console when debugging stops’ debug option can’t be specified at the project level and isn’t very flexible. Making use of the ‘IntegratedConsoleDebugging’ capability as a requisite for launching in the integrated console would provide flexibility for VSIX extensions to temporarily remove the capability and bypass the integrated console for special launches (temporarily) without needing to fiddle with an IDE-wide option that actually gets persisted (and therefore would cause problems if VS suddenly crashed without undoing the change to the IDE option).

---

Update: Similarly DebugLaunchOptions.IntegratedConsole isn’t specified as a debug options flag, despite the launch taking place inside the integrated console

[aodl]

Thanks @davkean, here’s a link to the tracker item

[davkean]

@aodl Can you file a bug via Help -> Send Feedback -> Report a Problem and I’ll route to them? They don’t track bugs here.