Code Analysis for "All File" and "Open files" will incorrectly use the active file's workspace folder settings

[Colengms]

In multiroot scenarios, the "All Files" and "Open Files" Code Analysis options appear to use the active file's workspace folder for code analysis settings. This results in inconsistent Code Analysis results, depending on which file is active and which workspace folder it's associated with. It may also result in a crash, if the extension was activated without a file becoming active (such as opening c_cpp_properties.json), in which case there is no active file and the workspace folder used will be null (leading to a null deference).

Currently, this issue is minimized by the fact that our active file is never cleared out properly. I need to address that in the context of other changes, to avoid invalid scenarios such as non-visible or unopen files still being considered 'active'.

[denis-adamchuk]

This is interesting. I observe a slightly different, and more annoying behavior. In a multi-root workspace if I "Run Code Analysis on All Files" no matter which file is open, the analysis runs on the first folder from the workspace and ignores the others. A workaround is to re-order folders and try again, but it is inconvenient even on a half a dozen of folders. VSCode 1.95.1.