While our steps are written for Raspberry Pi OS, they will also work on alternative operating systems such as Ubuntu.ġ. You will be using this web browser to download the latest available package of Visual Studio Code. To achieve this, you will need to have a web browser installed to your Raspberry Pi, such as Chromium. In this section, we will show you how to install Visual Studio code on your Raspberry Pi. Visual Studio Code is registered under the MIT license giving you the flexibility to fork and edit the code. You can view the entirety of the code on GitHub if you want to follow the code editor’s development.
Open Source & FreeĪn exciting part of VS Code is that it is open-source. One of the best parts is that it’s completely free and very customizable. Many features of Visual Studio Code make it stand out from alternatives. Equipmentīelow are all the equipment pieces that we used to set up VS Code on the Raspberry Pi.
You can set up your Raspberry Pi as a self-hosted Git server, or you can even install GitLab. We highly recommend it for anyone who is looking for a versatile code-editor.įor the best coding experience with VS Code, we recommend that you look into using git. Visual Studio Code is our favorite code editor both on the Raspberry Pi and off it. This official support means the software should continue to receive updates and function well on the device. In addition to Visual Studio Codes baked-in features, there is also a wealth of add-ons that you can use to extend its functionality even further.īest of all, Visual Studio Code on the Raspberry Pi is officially supported by the development team. The code editor is packed with numerous features and contains everything you need to write code on your device confidently. Even Jira tickets and Bitbucket PRs can be integrated by extensions.Īnd finally, it's just soooo much faster and offers all the extensions for basically any need.Visual Studio Code is one of the best code editors that you can run on your Raspberry Pi. There's almost no more need to leave VSCode in my general workflow. Then there's the integrated terminal which can be customized as well. On top of that, I can trigger one (or more) tasks as a precondition for my launch config.
I use one for debugging, one for unittest etc. I have a task to build binaries, unit tests, doxygen, etc.On VS Code, I can define custom launch configurations, e.g. I can assign a keyboard shortcut to trigger these tasks. Both instances are setup almost identically. I have VS Code on both Windows and a Linux VM. We use a Makefile based toolchain to build our software.We use the same toolchain to build for Windows and (cross-compiled) embedded Linux. I was happy and didn't think I would ever use VSCode as my primary IDE. When I came to my current position, I was used to using Visual Studio (201x).
0 kommentar(er)
