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!

[dejans]

Hi Matthias,

The problem you are experiencing is related to the fact that VS Code nRF Connect extension cannot see the newly copied folder as separate application.

One way to solve this would be to create a new application from your folder. In VS Code nRF Connect extension go to "Applications", press "+" sign (not visible by default, hover over to see it) "Add Folder as Application". This makes your folder visible under "Applications" and content of your application should be visible to you. 

Another way to solve this would be to go to "Add existing application" under "Welcome" inside nRF extension for VS Code. This has the same effect as previous method, adding your copied folder to the list of your applications.

When you make an application from your folder, you might need to perform pristine build in order to see "Input files", which should then contain relevant files from your copied folder. 

Best regards,
Dejan

[MaLu]

VSCode:
Version: 1.63.2 (user setup)
Commit: 899d46d82c4c95423fb7e10e68eba52050e30ba3
Date: 2021-12-15T09:40:02.816Z
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.19042

nRF Connect for VS Code v2021.12.137

The nRF Connect Windows Program is 3.7.1
It is not the newest because of 

https://devzone.nordicsemi.com/f/nordic-q-a/81345/nrf-connect-3-8-0-programmer-v2-0-0---update-modem-modem-dfu-failed?ReplySortBy=CreatedDate&ReplySortOrder=Descending

and

https://devzone.nordicsemi.com/f/nordic-q-a/81355/dks-not-being-detected-after-updating-to-nrf-connect-3-8-and-programmer-to-2-0-0?ReplySortBy=CreatedDate&ReplySortOrder=Descending

does the nrf connect desktop installation affect the vscode extension? 

[dejans]

Hi,

I have reproduced this issue. 
The problem might be with caching of paths.
The solution is to remove the whole build folder from your copied application folder and do pristine build to recreate it. After that all caching should be removed.

Best regards,
Dejan

[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