VS Code was not detected on your system.

RE: VS Code was not detected on your system.

henning larsen — Sat, 27 May 2023 08:08:30 GMT

Thanks Nicholas Lee Trimming the system PATH environment variable worked for me as well. (to be precise I moved the string "C:\Program Files\Microsoft VS Code\bin;" towards the start of the PATH - possibly creating problems for other programs further down now) I did however have a path length of about 1200 characters and it still works. So the number of 260 char I cannot confirm.

Note that it may be of significance weather vs code is installed in system or user mode. I have installed in system mode and this PATH is much longer than the user PATH. What a mess this is!

RE: VS Code was not detected on your system.

ChrisInAtl — Thu, 08 Sep 2022 23:32:41 GMT

Yes, code works fine from the command line. I've used that to launch VS Code for years.

I'll play around with execsnoop, though. Thanks.

RE: VS Code was not detected on your system.

AndreKR — Thu, 08 Sep 2022 20:50:31 GMT

Can you run the command code from a shell? Does it open VS Code? Then your PATH should be correct and the command that Toolchain Manager runs should succeed.

Process Monitor is a Windows thing, on MacOS you could try execsnoop.

RE: VS Code was not detected on your system.

ChrisInAtl — Thu, 08 Sep 2022 19:09:08 GMT

I'm seeing the same symptom on my macos install of nRF Connect for Desktop, v3.12.0.

I've tried mucking around with the PATH to shorten (per the other comment below) and to try to make sure it is set somewhere fundamental to running processes like .zshenv. No luck.

How did you view the PATH of the executing Toolchain Manager? I'm unfamiliar with Process Monitor, is that the app by the same name in the App Store? Thank you for any help.

RE: VS Code was not detected on your system.

Nicholas Lee — Tue, 14 Jun 2022 15:32:36 GMT

I too was wondering why VS code wasn't detected by the Tool Chain Manager, even when I had specified that VS Code be added to the path.
It turns out that if your windows PATH environment variable is already quite long, then, when it adds the VS Code directory to the PATH, that can take it over the limit of 260 characters, and then the Tool Chain Manager will fail to 'detect' VS code.
The solution in my case was to manually prune any obsolete directory entries from the PATH, then the Tool Chain Manager successfully detects and launches VS Code.
(My thanks to AndreKR for identifying that it was path related issue in the first place)

RE: VS Code was not detected on your system.

AndreKR — Mon, 23 May 2022 11:30:24 GMT

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.

RE: VS Code was not detected on your system.

AndreKR — Mon, 23 May 2022 11:25:25 GMT

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.

RE: VS Code was not detected on your system.

dejans — Mon, 23 May 2022 11:10:20 GMT

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

RE: VS Code was not detected on your system.

AndreKR — Mon, 23 May 2022 10:49:38 GMT

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.

RE: VS Code was not detected on your system.

dejans — Mon, 23 May 2022 08:34:29 GMT

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