-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Closed
Labels
bugfixedCheck the Milestone for the release in which the fix is or will be available.Check the Milestone for the release in which the fix is or will be available.regressionA bug that didn't exist in a previous releaseA bug that didn't exist in a previous releasetasks/build/debugAn issue relating to tasks.json (e.g. build issues)An issue relating to tasks.json (e.g. build issues)verifiedBug has been reproducedBug has been reproduced
Milestone
Description
Type: LanguageService
When I do the key combo 'CTRL+SHIFT+B' on a new directory (not configured for any build task), it would previously prompt me to set up a new task. This was wonderful since I likely wanted to invoke cmake/ninja/etc. It is now, however, only presenting me the option to invoke cl.exe on the active file. While I can still go in and manually set up a new build task, it was very convenient to do everything the old way. This could also be an editor change unrelated to the extension, but it's still annoying nonetheless. FWIW if the active file is not a C++ file, then it presents me with the old experience, so I suppose at least I still have that
Describe the bug
- OS and Version: Windows Insiders (but hit this on 1803 machine at home)
- VS Code Version: 1.35.0-insider
- C/C++ Extension Version: 0.23.1
Metadata
Metadata
Assignees
Labels
bugfixedCheck the Milestone for the release in which the fix is or will be available.Check the Milestone for the release in which the fix is or will be available.regressionA bug that didn't exist in a previous releaseA bug that didn't exist in a previous releasetasks/build/debugAn issue relating to tasks.json (e.g. build issues)An issue relating to tasks.json (e.g. build issues)verifiedBug has been reproducedBug has been reproduced