VS Code was not detected on your system.

Question

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.

user112696 · Accepted Answer

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.

user72009 · Answer

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)

VS Code was not detected on your system.

Top Replies