#1 most-used code editor Source: Stack Overflow Developer Survey 2021Visual Studio Code - WSL - SSH - Containers - Free - Cross-platform - Lightweight #1 most-used code editor Source: Stack Overflow Overflow Developer Survey 2021Visual Studio Code - IntelliSense - Debugging - CMake - Make - WSL - SSH - Containers - Free - Cross-platform - Lightweight #1 most-used code editor Source: Stack Overflow 1. Installing VS Code on the Raspberry Pi 2. Installing VS Code on a laptop and using the Remote-SSH extensionDemo #2 key takeaways 1. VS Code provides full C++ IntelliSense and debug support for Raspberry

This is To Reduce Connectivity Costs and Use the Limited Connectivity for the most Crucial Things. SSH • This is one of the benefits of Terminal Based Computing. • Try To Learn About Vim/Neovim or Emacs basic android phones with terminals via ssh-clients. This works with windows PCs. • I use this personally as my personal machine is Linux based, but always ssh into my wife’s laptop to try things out

Works on many OS – develop on Mac, Linux, Windows,... Remote Development solutions – WSL, tunneling, SSH, ... Code completion through IntelliSense But I want a fully integrated build system & debugging to a Remote Machine via a secure tunnel from a VS Code client anywhere, without the requirement of SSH. - Develop anywhere: connect to a tunnel from VS Code Desktop or vscode.dev - Like using a CLI more

same. The recommended approach is to manage the credentials in an orthogonal way, for example using ssh keys. The provided example contains a Github action that does this: 208 Chapter 7. Examples Conan actions/checkout@v3 with: ssh-key: ${{ secrets.SSH_PRIVATE_KEY }} - uses: actions/setup-python@v4 with: python-version: '3.10' - uses: webfactory/ssh-agent@v0.7.0 with: ssh-private-key: ${{ secrets.SSH_PRIVATE_KEY checkout actions/checkout@v3 action receives the ssh-key to checkout as git@ instead of https • The webfactory/ssh-agent@v0.7.0 action takes care that the ssh key is also activated during the execution of

Windows, macOS, and Linux C++ IntelliSense, debug & code browsing CMake, vcpkg and git integrations SSH/container/WSL remote experiences and much, much more… https://aka.ms/cpp/code Thu 10/05 – 3:15pm ms/cmakevs for more details🐧 Linux Targeting Target any Linux distro, including WSL-2 Interactive SSH Integrated Terminal for Linux CMake Presets for Linux Targeting New: Automatically Install WSL from

same. The recommended approach is to manage the credentials in an orthogonal way, for example using ssh keys. The provided example contains a Github action that does this: Listing 27: .github/workflows/hello-demo actions/checkout@v3 with: ssh-key: ${{ secrets.SSH_PRIVATE_KEY }} - uses: actions/setup-python@v4 with: python-version: '3.10' - uses: webfactory/ssh-agent@v0.7.0 with: ssh-private-key: ${{ secrets.SSH_PRIVATE_KEY checkout actions/checkout@v3 action receives the ssh-key to checkout as git@ instead of https • The webfactory/ssh-agent@v0.7.0 action takes care that the ssh key is also activated during the execution of

same. The recommended approach is to manage the credentials in an orthogonal way, for example using ssh keys. The provided example contains a Github action that does this: Listing 28: .github/workflows/hello-demo actions/checkout@v3 with: ssh-key: ${{ secrets.SSH_PRIVATE_KEY }} - uses: actions/setup-python@v4 with: python-version: '3.10' - uses: webfactory/ssh-agent@v0.7.0 with: ssh-private-key: ${{ secrets.SSH_PRIVATE_KEY checkout actions/checkout@v3 action receives the ssh-key to checkout as git@ instead of https • The webfactory/ssh-agent@v0.7.0 action takes care that the ssh key is also activated during the execution of

same. The recommended approach is to manage the credentials in an orthogonal way, for example using ssh keys. The provided example contains a Github action that does this: Listing 32: .github/workflows/hello-demo actions/checkout@v3 with: ssh-key: ${{ secrets.SSH_PRIVATE_KEY }} - uses: actions/setup-python@v4 with: python-version: '3.10' - uses: webfactory/ssh-agent@v0.7.0 with: ssh-private-key: ${{ secrets.SSH_PRIVATE_KEY checkout actions/checkout@v3 action receives the ssh-key to checkout as git@ instead of https • The webfactory/ssh-agent@v0.7.0 action takes care that the ssh key is also activated during the execution of

same. The recommended approach is to manage the credentials in an orthogonal way, for example using ssh keys. The provided example contains a Github action that does this: Listing 27: .github/workflows/hello-demo actions/checkout@v3 with: ssh-key: ${{ secrets.SSH_PRIVATE_KEY }} - uses: actions/setup-python@v4 with: python-version: '3.10' - uses: webfactory/ssh-agent@v0.7.0 with: ssh-private-key: ${{ secrets.SSH_PRIVATE_KEY checkout actions/checkout@v3 action receives the ssh-key to checkout as git@ instead of https • The webfactory/ssh-agent@v0.7.0 action takes care that the ssh key is also activated during the execution of

same. The recommended approach is to manage the credentials in an orthogonal way, for example using ssh keys. The provided example contains a Github action that does this: Listing 32: .github/workflows/hello-demo actions/checkout@v3 with: ssh-key: ${{ secrets.SSH_PRIVATE_KEY }} - uses: actions/setup-python@v4 with: python-version: '3.10' - uses: webfactory/ssh-agent@v0.7.0 with: ssh-private-key: ${{ secrets.SSH_PRIVATE_KEY checkout actions/checkout@v3 action receives the ssh-key to checkout as git@ instead of https • The webfactory/ssh-agent@v0.7.0 action takes care that the ssh key is also activated during the execution of