Unless we feel it's time to flatten that machine :), we hesitate to try out a new stack like Rust, Go, Node, or Python3, for fear of 'messing up' our current, well-tuned environment. We saw many developers trying to use VS Code to develop against containers and remote VMs configured with specific development and runtime stacks, simply because it is too hard, too disruptive, and in some cases impossible, to set up these development environments locally. With the growth in popularity of VS Code, we've had the privilege and opportunity to talk to more and more users with different development environments, many vastly different than our own, to try to identify ways in which we could move VS Code forward to address real developer pain points.Īn interesting pattern emerged during these conversations.

Note: You'll need to use the Insiders build for now, but remote development support will eventually be available in the Stable release.

You can get started right away by installing the Remote Development Extension Pack. Today we're excited to announce the preview of three new extensions for Visual Studio Code that enable seamless development in Containers, remotely on physical or virtual machines, and with the Windows Subsystem for Linux (WSL).

Node.js Development with Visual Studio Code and Azure.

Moving from Local to Remote Development.

Download phpstorm remote debugging