Search icon CANCEL
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Windows Subsystem for Linux 2 (WSL 2) Tips, Tricks, and Techniques

You're reading from   Windows Subsystem for Linux 2 (WSL 2) Tips, Tricks, and Techniques Maximise productivity of your Windows 10 development machine with custom workflows and configurations

Arrow left icon
Product type Paperback
Published in Oct 2020
Publisher Packt
ISBN-13 9781800562448
Length 246 pages
Edition 1st Edition
Tools
Arrow right icon
Author (1):
Arrow left icon
Stuart Leeks Stuart Leeks
Author Profile Icon Stuart Leeks
Stuart Leeks
Arrow right icon
View More author details
Toc

Table of Contents (16) Chapters Close

Preface 1. Section 1: Introduction, Installation, and Configuration
2. Chapter 1: Introduction to the Windows Subsystem for Linux FREE CHAPTER 3. Chapter 2: Installing and Configuring the Windows Subsystem for Linux 4. Chapter 3: Getting Started with Windows Terminal 5. Section 2:Windows and Linux – A Winning Combination
6. Chapter 4: Windows to Linux Interoperability 7. Chapter 5: Linux to Windows Interoperability 8. Chapter 6: Getting More from Windows Terminal 9. Chapter 7: Working with Containers in WSL 10. Chapter 8: Working with WSL Distros 11. Section 3: Developing with the Windows Subsystem for Linux
12. Chapter 9: Visual Studio Code and WSL 13. Chapter 10: Visual Studio Code and Containers 14. Chapter 11: Productivity Tips with Command-Line Tools 15. Other Books You May Enjoy

Introducing Visual Studio Code Remote

One way of working with files from a WSL distro's file system is to open them using the \\wsl$ share that WSL provides (as discussed in Chapter 4, Windows to Linux Interoperability, in the Accessing Linux files from Windows section). For example, I can access the wsl-book folder from my home directory in the Ubuntu-20.04 distribution via \\wsl$\Ubuntu-20.04\home\stuart\wsl-book. However, while this works, it incurs the cost of Windows-to-Linux file interop and doesn't provide me with an integrated environment.

On Windows, if we have Python installed along with the Python extension for Visual Studio Code, then we get an integrated experience for running and debugging our code. If we open code via the \\wsl$ share, then Visual Studio Code will still give us the Windows experience, rather than using the installation of Python and its dependencies and tools from WSL. However, with the Remote-WSL extension from Microsoft, we can fix that...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime