Then all you need to do is have a slight change in workflow. Instead of opening VS Code from the Start Menu (i.e. from Windows), you should start it from the WSL Terminal by running “code. ” from the directory you wish to work in. This can be a Windows directory mounted in the WSL (i.e. Note: make sure that the default of wsl is now ubuntu app, otherwise use the following command: wsl -s Ubuntu-20.04 Then I typed code. “/mnt/c/…”) but it can also be a true Linux directory. This last bit is interesting because this wan’t possible previously. If you wanted to edit something in your Linux user directory (“~/.gitconfig” for example), you had to edit it in the WSL. The first time you start VS Code from the WSL, it will install the necessary components:Īfter that, you’re good to go. VS Code will now perform all its actions in the WSL: sending commands, editing files, etc. However, this also means you might need to re-install some extensions.
You can see you’re running a remote session by the green bar in the bottom left:Ī consequence to keep in mind is that any output is now sent to the Debug Console in VS Code.įeature files) had to be installed in WSL in order to work: For example, my Cucumber extension (to provide syntax support in. If you were previously used to running everything in the WSL terminal in Windows, you’ll have to get used to this change. Other than that, great work from Microsoft.
0 kommentar(er)
