"Configure Default Build Task" - Task Generation Only Lists Top-Most Project As Active In Multi-Root Workspace

[vindicatorr]

Type: LanguageService

Describe the bug

• OS and Version: Linux x64 5.8.7-dirty
• VS Code Version: 1.53.0-insider (9b6aaf1e86c8fec4c86c664edf5f713583c70fe5)
• C/C++ Extension Version: v1.1.3
• Other extensions you installed (and if the issue persists after disabling them): Only C/C++ extension is enabled.
• Does this issue involve using SSH remote to run the extension on a remote machine?: N/A
• A clear and concise description of what the bug is, including information about the workspace (i.e. is the workspace a single project or multiple projects, size of the project, etc).: "Tasks: Configure Default Build Task" always lists the top-most project as the "active file" for generating a new task.

Steps to reproduce

1. Create a workspace
2. Add multiple root workspace projects
3. Make one of the projects NOT contain a "tasks.json" file, but do NOT make that project the top/first project. (not really necessary, but highlights the issue)
4. Tasks: Configure Default Build Task
5. Close the workspace and only open the project WITHOUT a "tasks.json" file.
6. Tasks: Configure Default Build Task

Expected behavior

I'd expect step 4 to show the project that doesn't have a "tasks.json" file like it does in step 6, as opposed to showing the top root workspace project for task generation (screenshots should make it clear).

Logs

``` N/A (nothing showing relating to the "Configure Default Build Task" when activated) ```

Screenshots

Multi-root incorrect: It looks to always be the top-most project that gets the "generate" option for tasks. It seems to always consider it the "active file". Even when I open the "app.cpp" for the "firmware" project which already has a "tasks.json" file, it still considers the top Arduino project as the "active file".

Solo project correct:

Additional context

[sean-mcmanus]

@elahehrashedi Do you remember if this was a known TODO for build tasks? I seem to recall it was.

[elahehrashedi]

This is potentially a Vs Code feature. Follow this issue from here: https://github.com/microsoft/vscode/issues/120133

[sean-mcmanus]

@elahehrashedi Is this fixed with 1.3.0?

[elahehrashedi]

Track this issue on Vs Code side: https://github.com/microsoft/vscode/issues/35312 (also https://github.com/microsoft/vscode/issues/120133 and https://github.com/microsoft/vscode/issues/89448). It will be possibly fixed in their June release.