Explore support for developing on WSL

[kieferrm]

WSL allows you to run linux program on Windows. We are looking into providing support for working with WSL when Code runs on Windows. This is related to #29194.

Other related items are:

• Git: Support WSL #9502
• Support launching VS Code from Bash on Ubuntu on Windows #13138
• Run ts server using ubuntu bash (WSL) #20220
• Optionally Run Language Servers/Extensions using Windows Subsystem for Linux #22663
• Feature request: WSL remote interpreters for extensions developers #28667
• Globally WSL support #50795

Here is the query of all open issues labeled with WSL: query

[jsynowiec]

Just a heads-up, for reference, most JetBrains IDEs now support WSL interpreters without the remote-interpreter-over-ssh workaround. It's available in PyCharm 2018.3, RubyMine 2017.3, WebStorm 2018.2.

[uishon]

Just a heads-up, for reference, most JetBrains IDEs now support WSL interpreters without the remote-interpreter-over-ssh workaround. It's available in PyCharm 2018.3, RubyMine 2017.3, WebStorm 2018.2.

As for JetBrains IDEs, it's true and nice but as for Python (PyCharm), virtualenvs are not supported so at least for me, this makes this feature useless. Unfortunately.

[helioascorreia]

Yes, a totally agree with uishon. Vscode is from windows and now the python package too (and the top downloaded package). I think they should focus more on getting the best integration between vscode, python and WSL.
When I'm doing Django development on windows, I need to use wsl because I got some bugs on translations and channels for example. If I use that, I can't set the python linter for vscode.
The fix I needed to do was have two virtualenvs, one for windows and another to WSL.

[offero]

Does debugging through docker work on Windows?

[benc-uk]

Oh god yes!
I need this. The integration today is non-existent, and actually causes a lot of problems (e.g. multiple git commits).

Support for WSL git as the main source control, but also critical for language extensions (Node, Dotnet, Python, Go).
The lack of support currently means I have to have SDKs for all languages installed under both Windows and WSL

Also tasks and debug also need to be aware of WSL, with path translations and locating binaries. Trying to get a set of clean launch configs that work on any developer's system is impossible