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
You may have noticed that with the latest update to the WSL remote extension (0.77.0), connecting to NixOS fails.
This is because Micrsoft removed the option for setting the remote connection method. Where before you could get it to connect by setting the option to something other than wslExeProxy, that is the only option available now.
EDIT: As @purepani pointed out over at the Microsoft repo, for the time being, you can try to get it to work by downgrading the WSL Remote extension to the latest working version (0.76.0) either through the GUI or by running the following command:
Deleted. I think what occurs to me is not the same issue.
Deleted content
For me, just type code in my WSL shell, waiting for it to download vscode-server is enough.
After vscode-server is downloaded, everything is the same as before. Just use nixos-vscode-server or manually replace node under ~/.vscode-server with a symlink.
You may have noticed that with the latest update to the WSL remote extension (0.77.0), connecting to NixOS fails.
This is because Micrsoft removed the option for setting the remote connection method. Where before you could get it to connect by setting the option to something other than
wslExeProxy
, that is the only option available now.There are two issues tracking possible solutions:
wsl --exec
#222 here for patching NixOS on WSL to supportwslExeProxy
EDIT: As @purepani pointed out over at the Microsoft repo, for the time being, you can try to get it to work by downgrading the WSL Remote extension to the latest working version (
0.76.0
) either through the GUI or by running the following command:and making sure that you have the following setting configured in VSCode
The text was updated successfully, but these errors were encountered: