You can access both of them (but I recommend only making changes to settings.json) from the VSCode command pallet. After all, the 'Settings' user interface is just a visual representation of your personal 'settings.json' file and the 'defaultSettings.json' file. If you aren't familiar with JSON, its time to start learning. While installing the extension is pretty straightforward, what comes next isn't quite as intuitive as you would hope, especially if you've never configured a VSCode extension before. I'm going to switch to a virtual machine now Visual Studio Code installed and show you the exact four steps you need to do. Select the extension and then using the search for the marketplace find ToDo Tree and click install. However, if you're using a newer version, the extension icon is the 'app' icon. If you are running an older version, the extension icon is the square box under the bug. Possibly, you are right that something has to be reinstalled.However, note the icons were updated more recently than the documentation this may cause the images to look different.

You can reinstall or restore this module on the local computer. The module that raised this event possibly is not installed on the local computer or the installations is corrupt. The error message that I see also says something like this (translated from Dutch):Ĭannot find the description of the event-id 0 of the source cntlm. It could also be a regular vscode check for updates, I am not 100% sure. Now, every time i run 'icons enable' or 'icons update', this error message appears in my event veiwer:Ĭntlm: PID 18604: 127.0.0.1 CONNECT :443Ĭntlm: PID 18604: 127.0.0.1 CONNECT :443 otherwise they don's install, upgrade, etc.

i have configured the cntlm local proxy and it is a classic solution for all stuff atom, vscode, nodejs, etc. i am beginning to suspect the corporate proxy.

Visual studio code icons not showing