Did an update of vscode tonight and the ide suggested I download and install VSCode (user) instead.
I uninstalled my vscode, deleted my .vscode and .platformio dirs from my home directory (win10/64) and installed the VSCode (user).
Installed the platformio ide plugin. Then nothing. It never re-created the .platformio directory no matter what project I opened up. No drive IO to show any signs of life.
So I uninstalled the user version. Removed .vscode and installed 1.14.2, as it was the only installer I kept. All worked fine, .platformio populated and could compile perfect.
It did an update to 1.26.0 (vscode) and stopped working. (no toolbar at bottom). I stopped, deleted existing .platformio and started. .platformio was not created and no signs of life in the ide.
I found another dir that wasn’t removed (%appdata%\Code) and even did a clean install with 1.26 with the same results. It’s as if the plugin doesn’t get activated.
Well, nothing like a bitter old man spitting vinegar as he broke all his development.
The problem:crap left over from old atom installs. Remove Python and CMake. It was probably the python.
I removed %appdata%\code, %home%.platformio and %home%.Code and did a complete re-install.
Somewhere along the way PlatformIO or VSCode devs changed the program pathing and left this mess.
My guess is this will nail old atom users than anything else.
(update) Not Fixed!
What this did was properly kick the platformio extension to install itself into the .platformio folder (it didn’t do it before) but stops there. The process does install a more modern version of python than I had before.
It’s as far as I can go without knowing what goes on under the hood.
Breaks PlatformIO plugin. Remove it and it works again. I don’t know what happened between 1.25.1 and 1.26, but this one slipped through. I don’t use/like git, but I will just have to sift through the annoying messages.