can not find the all reference when c++ file extension is not `.cpp`

[heartacker]

Bug type: Language Service

Describe the bug
版本: 1.64.0-insider (system setup)
提交: 23aa7ad51c95d90d48b1d352a316d7f0c2c4310d
日期: 2022-01-18T09:44:38.476Z
Electron: 13.5.2
Chromium: 91.0.4472.164
Node.js: 14.16.0
V8: 9.1.269.39-electron.0
OS: Windows_NT x64 10.0.14393
C/C++: 1.8.0-INSIDER

Steps to reproduce

1. a foo.h file
2. a foo.pln file witch code is cpp
3. change the .pln file association with cpp
4. focus a function declaration in the header file, execute command find all reference
5. we could not see any reference in pln file
6. open the pln with vscode
7. execute command find all reference again
8. we could see that reference in pln file

Expected behavior
we could see reference in pln file

Screenshots

• before open pln file in vscode
  

• after open pln file in vscode
  

Additional context

pln is a special file extension of cpp in my solution

[heartacker]

"files.associations": {
    "*.pln": "cpp",
}

[sean-mcmanus]

The bug is that changing the files.association doesn't automatically trigger a Rescan. You can workaround it via running the C/C++: Rescan Workspace command.

That'll fix the case where an extension is associated with c/cpp, but if an extension is unassociated from c/cpp, then it requires a manual Reset IntelliSense Database command.

UPDATE:
This should be fixed in our next release (1.8.1, next week).

However, the case when file extensions are unassociated with c/cpp is not fixed and still requires a manual Reset IntelliSense Database if you want to stop getting symbol results for those files (that case is rarer and harder to fix, particularly since unassociated files are still desired to be in the database when they are #included by some other c/cpp file).

[heartacker]

oh, thanks, BTW, I have associated pln with cpp before

[sean-mcmanus]

We believe this is fixed with https://github.com/microsoft/vscode-cpptools/releases/tag/1.8.1 .