You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Insiders updateChannel doesn't work with WSL remote #3833
The local version uses 0.24.0-insiders2, but my WSL remote incorrectly defaults to "Default" and then doesn't switch after changing it to Insiders. I thought we tested this earlier and it was working for the WSL remote scenario.
I'm having problems also, but I think it's because I'm on WSL2. I'll try to leave more info when I can. Right now though, it can't detect compiler path when I use /usr/bin/gcc or /usr/bin/g++, and I suspect it has to do with the way the WSL pipe works with WSL2.
Brian Vanderbusch (@LongLiveCHIEF) If WSL2 is the new file system (where the /usr/bin/g++ is not detected as a file on Windows), then that's a known issue -- a potential workaround is to use the Remote - WSL extension to connect.
Activity
[-]Insidrs updateChannel doesn't work with WSL remote[/-][+]Insiders updateChannel doesn't work with WSL remote[/+]sean-mcmanus commentedon Jun 26, 2019
It gives the error C/C++: Install vsix -- Failed to find VS Code script in the developer console.
sean-mcmanus commentedon Jun 26, 2019
Manually downloading/installing the vsix in the WSL remote is a workaround.
visstro commentedon Jun 27, 2019
Could you describe how to fix it manually?
visstro commentedon Jun 27, 2019
Ok, there is actually no remote stuff magic here.
According to: https://code.visualstudio.com/api/advanced-topics/remote-extensions#installing-a-development-version-of-your-extension
Seems like it will keep auto updating even after manual install. Hope this is one-time action. :)
LongLiveCHIEF commentedon Jul 28, 2019
I'm having problems also, but I think it's because I'm on WSL2. I'll try to leave more info when I can. Right now though, it can't detect compiler path when I use
/usr/bin/gccor/usr/bin/g++, and I suspect it has to do with the way the WSL pipe works with WSL2.sean-mcmanus commentedon Jul 29, 2019
Brian Vanderbusch (@LongLiveCHIEF) If WSL2 is the new file system (where the /usr/bin/g++ is not detected as a file on Windows), then that's a known issue -- a potential workaround is to use the Remote - WSL extension to connect.
Colengms commentedon Feb 18, 2021
I'm not repro'ing this. I'm seeing insiders build installed in my remote WSL connection. This seems to have been addressed. Closing as fixed.
Colengms commentedon Feb 18, 2021
This was fixed by #4767