nRF Connect VSCode extension caching paths?

[MaLu]

Hello,

I recently installed the VSCode Extension for nRF Connect and I am experiencing, what seems to me, strange behaviour. 

Here's the steps:

1. I create a project from an example
2. select board, the SDK, do a pristine build etc.. all good
3. I copy the project folder to a new folder (like "Project-Copy")
4. I open this new Folder, with the same project in it, in VSCode

Now, with this copied folder, the strangeness begins, because the extension is still referencing files, (CMakeLists.txt for example) from the old folder. I know this, because when I click on the File from the extensions "Input files", it opens the old one and editing the file in the new folder does not affect anything, only editing the old one does. It also does not seem to matter, if I delete the build folder, it still references old files, despite no path in any of the files in my project pointing to that old project folder.

Maybe I'm missing something, but this does not seem intended/desirable. 

Thank you in advance!

[MaLu]

Hi,

this seems to work when you delete the build folder before opening the copied folder with vscode. 

If you open the copied application and then delete the build folder, the wrong paths are obviously already loaded from cache and pristine building does nothing to resolve this. 

I want to thank you for this fix/workaraound for now.
I still hope, that this topic would get looked into in the extension itself, as I can see it being really headache inducing.

[dejans]

Hi Matthias,

I am glad that this solution worked for you. 

This is exactly what I meant. First remove the build folder and then load the application to VS Code. Afterwards, pristine build should be performed to recreate build folder.

Best regards,
Dejan