Well, clearly something is not right here. :)
How exactly does it try to "detect" VS Code?
I have now installed the Extension Pack from inside VS Code which worked without any issues.
Well, clearly something is not right here. :)
How exactly does it try to "detect" VS Code?
I have now installed the Extension Pack from inside VS Code which worked without any issues.
Hi,
Could you provide more information about the issue?
What did you try to do before error appeared?
You could try updating nRF Connect for Desktop as well as Toolchain Manager.
Best regards,
Dejan
Isn't it clear from the screenshot? I have VS Code installed. I installed the Toolchain Manager using nRF Connect for Desktop and I installed an SDK using the Toolchain Manager. When I then click "Open VS Code" in the Toolchain Manager, I get "VS Code was not detected on your system", even though VS Code is actually running at the same time.
Hi,
Have you tried updating nRF Connect for Desktop and Toolchain Manager to the newest versions?
In Toolchain Manager, from which nRF Connect SDK (NCS) version you cannot open VS Code? Do you get the same issue with other installed versions of NCS?
Best regards,
Dejan
I have not tried upgrading because I had to downgrade from 3.8 to 3.7 as described here to make my PPK2 work.
I only have one SDK installed (they are quite big), that is v1.9.1.
Silly me, I just realized that of course the Toolchain Manager is open source, so it's easy to see that the "detection" actually just tries to run code --list-extensions. I confirmed with Process Monitor that this command is executed with an unmodified PATH, so VS Code would actually have to be in PATH. Since of course on my machine it is not, this mechanism will fail.