There wasn’t a clean & practical way for us to bundle this dependency with our extension but setting up WSL isn’t too heavy of a lift and gives us the tooling required to interface with a remote host - unavailable natively on Windows. There may be alternatives but we haven’t taken too much initiative to discover them as of yet.
Comments3
Dec 22, 2025
PinnedThis is now available through concurrent SFTP transfers (`v1.5.2`) and is also now the default for Remote Syms.
Oct 11, 2025
PinnedThere are a couple of viable options for this, we're looking into it and expect to have a solution soon.
Dylan Martinez
Jul 8, 2025
The reason we have the WSL dependency is due to us needing our own LSP for PowerOn. Until Microsoft adds support for accessing virtual resources (ref.
https://code.visualstudio.com/api/extension-guides/virtual-workspaces#what-about-support-in-the-language-server-protocol-lsp-for-accessing-virtual-resources) the only practical way to deliver a seamless “semi-virtual” experience is to manage remote resources locally by keeping them synchronized via
rsync.There wasn’t a clean & practical way for us to bundle this dependency with our extension but setting up WSL isn’t too heavy of a lift and gives us the tooling required to interface with a remote host - unavailable natively on Windows. There may be alternatives but we haven’t taken too much initiative to discover them as of yet.