VSCode NRF Connect plugin broken

[luc_eac]

Hi

I have been working on a project for some time, using the SDK and the nRF Connect for VS Code plugin. A few weeks ago I stepped away from this to take on different work, but now I am picking it back up to prepare systems for testing.

Out of nowhere the nRF Connect for VS Code plugin doesn't do anything anymore!

The project has not changed, the settings have not changed, the SDK (2.4.0) has not changed - nothing has changed that I know of. I open the project like I always do: Open VSCode, File->Open recent->my project, and expect the plugin to start loading and show me the project, the build targets, etc.. But the NRF CONNECT tab only shows me: >WELCOME and >CONNECTED DEVICES. The plugin does not even open the welcome page anymore.

This is not the first time I have had issues with the toolchain - in fact, I have run into issues pretty much every step of the way now and I am really getting fed up with this. This is taking huge amounts of time - of which we now have very little! Needless to say I am very unhappy about your products, but.. I have to soldier on.

So once again, I ask for your support: How do I get this mess to work again?

VS Code version 1.82.3

nRF Connect for VS Code v2023.9.336

nRF Connect for VS Code Extension Pack v2023.9.4

SDK Version 2.4.0

Edit:

I tried re-installing the plugins (nRF connect for VS Code + Extensions), that did not work.

I tried re-installing VS Code, that did not work either

[luc_eac]

It turns out the new version of the extension did not cope with my existing toolchain and SDK installation.

After relocating my toolchain and SDK from C:\ncs to C:\_ncs and rebooting VS Code, the extension now showed an "Install toolchain" button. Having installed the toolchain and SDK through there, everything looks like it's working again. The application shows up and I am able to build it.

The strange thing is that this process has essentially created a 1:1 copy of the folder that I had just moved, nothing changed as far as I can tell. Somehow it magically fixed the extension though.

[caezar]

Thank you! This worked for me too.

The extension definitely has feelings about a pre-existing folder. Maybe it's a permissions issue?