This is interesting. However, I got blindsided by both VSC and the extension on an existing project which was using powershell commands and working. The update causes a LOT of problems. I even went so far as to create a NEW C++ project (see this post: I tried using the C++ template doing a helloworld project. It had issues - #8 by ToradexAI )and the first issue that the basic setup that happens with some powershell commands use xonsh to change the directory and VSC won’t recognize the workspace as trusted. I tried adding the directories several times but that didn’t work. The work around is adding an option of “cwd”;”” in some of the commands. This only happens when trying to run the port sharing routine.
Then the next issue is the actual build and container running. It seems to build it on my local repo, but it thinks it is starting the container, it doesn’t spin up because the image is not located on the device. Then when it does the xonsh service-check.xsh, it thinks it is only getting 1 argument. I haven’t been able to figure that one out as I don’t know anything about xonsh.
So basically, I can’t even get a C++ HelloWorld to compile and run on the device.
So when you say it is invasive, it makes me cringe…