• State Verified Answer
  • Replies 10 replies
  • Answers 1 answer
  • Subscribers 68 subscribers
  • Views 2188 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 289420
Options

VS Code was not detected on your system.

AndreKR

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.

  • 0

    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)

  • 0 in reply to AndreKR

    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.

  • 0 in reply to ChrisInAtl

    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.

  • 0 in reply to AndreKR

    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.

  • 0 in reply to Nicholas Lee

    Thanks   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!

Related