![]() Other than that, great work from Microsoft. If you were previously used to running everything in the WSL terminal in Windows, you’ll have to get used to this change. 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. ![]() feature files) had to be installed in WSL in order to work: For example, my Cucumber extension (to provide syntax support in. However, this also means you might need to re-install some extensions. ![]() VS Code will now perform all its actions in the WSL: sending commands, editing files, etc. The first time you start VS Code from the WSL, it will install the necessary components:Īfter that, you’re good to go. If you wanted to edit something in your Linux user directory (“~/.gitconfig” for example), you had to edit it in the WSL. This last bit is interesting because this wan’t possible previously. “/mnt/c/…”) but it can also be a true Linux directory. 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. This can be a Windows directory mounted in the WSL (i.e. ” from the directory you wish to work in. from Windows), you should start it from the WSL Terminal by running “code. Instead of opening VS Code from the Start Menu (i.e. ![]() Then all you need to do is have a slight change in workflow. You could probably also install the “Remote – WSL” extension, but as I will probably be using the SSH extension as well, I’ll install the extension that contains the three separate ones: WSL, SSH and containers. Nevertheless, here’s a quick overview of getting started.įirst, install the “Remote Development” extension in VS Code: There is now an extension for VS Code that will allow you to debug applications running in the WSL. I had to add statements, run the application, add more statements, run it again, rinse and repeat. Needless to say, this is not the most efficient way of debugging. ![]() Previously, I had to “debug” by adding console.log statements everywhere. Up until now, I was missing one important feature: debugging support. That means running Visual Studio Code in Windows, but running the program in Linux. Ever since I had to do Python development, I use the WSL for almost all of my non-.NET work: PHP, Python, Typescript/Node.js. I love the Windows Subsystem for Linux (WSL). ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |