The primary focus of this site is to provide builds of the open-source edition of VS Code for less common platforms (those that might not otherwise receive them). You can find details below of the architectures, operating systems and packaging formats these builds support.
For each and every release, the build system prepares a virtual system for the given architecture. The finished package is then installed and tested with the full suite of tests from Microsoft. Once this is done, a test report is prepared that can be downloaded for review. Only packages that pass all tests will proceed to release.
The instructions below require you to put your device into Developer Mode. There are important security implications to doing this, so please consider the ramifications carefully before deciding to do so. Please click here for more details.
- Put your Chromebook into developer mode.
- Install the crouton extension from the Chrome Web Store.
- Press Ctrl + Alt + T to enter the crosh shell.
- Type shell and press return to enter the developer shell.
- Enter the following command, then press return:
. <( wget -O - https://code.headmelted.com/installers/chromebook.sh )
Linux(including Raspberry Pis, Odroids and other single-board computers)
Packages are currently available in DEB and RPM format.
You can use the scripts here to install the packages and add their repository to your system.
Open a new terminal. If you need super-user rights (you probably do), then you can enter sudo -s and press return to enter a super-user session. Run the installer for your current distribution:
APT instructions(including Debian, Raspbian, Ubuntu and Linux Mint)
. <( wget -O - https://code.headmelted.com/installers/apt.sh )
YUM instructions(including Fedora, Pidora, Red Hat and SUSE)
. <( wget -O - https://code.headmelted.com/installers/yum.sh )
Press the return key. Once the installer has completed, you should have a "Code - OSS" entry in your desktop program list.
If for any reason the script above will not work on your system, or you do not want to add the package source for updates, you can get the latest version of the package for your system below.
Public GPG key
For either APT or YUM installation, you'll want the public GPG key to verify the package, which you can download here.
APT and YUM packages
These packages are now available directly from the releases page.
Frequently asked questions
- What is this?
- These are automated builds of the open-source edition of Microsoft's Visual Studio Code.
- How does this work?
- The latest code is pulled on a nightly basis from Microsoft's official repository. If there are updates, the code is built, tested, packaged and deployed.
- Which devices are supported?
- Please refer to the Platforms section.
- Do these releases support extensions?
- The extensions you want should work. Any dependencies that are not local to your architecture (e.g. x86 binary code on an ARM chromebook) will be emulated to ensure compatibility, but there is no guarantee of compatibility.
- Will Visual Studio Code run on my device?
- The best way to find out if your device is compatible is to go to the Instructions section and try it for yourself.
- Which virtual systems are these releases tested on?
- 32-bit ARM hard-float (armhf)
- These packages are installed and tested on a virtualized Raspberry Pi 2 running Raspbian Jessie.
- 64-bit ARM hard-float (arm64)
- These packages are tested on a modified Ubuntu 16.04 image to mimic an Odroid C2.
- You emulate a whole Raspberry Pi?
- Absolutely, it's the only way to be sure that all of the dependencies are tested and supported for a given build. (Note that x86 emulation is also disabled for this, to make sure we aren't accidentally cheating).
- Are these releases provided by Microsoft?
- No. These releases are an independent community effort. For clarity, this website (and the releases here) are not affiliated with Microsoft.
- Are you a Microsoft employee (or MVP)?
- I am not. (Unfortunately not, but you can nominate me).
- Why is the logo so much different from the one on Microsoft's website?
- The Visual Studio Code logo is owned by Microsoft, and is reserved for use on releases provided directly by them, so cannot be used here. I also do not want to mislead anyone into believing that these builds are provided by or officially endorsed by Microsoft directly (see question and answer above).
- Where are the packages being hosted?
- The release packages are hosted on Github Releases and by JFrog Bintray, both of whom are graciously providing this service for free under their open-source plans.
- Why make these builds?
- The intention of these builds is to get Visual Studio Code into the hands of as many developers (and aspiring developers) as possible. Doing this means reaching out to those users on the most cost-conscious machines, and therefore supporting lower-end devices based on ARM that may be more complicated for Microsoft to support in an official capacity.
- Why Visual Studio Code?
- I personally wanted to use the tool on my own ARM single-board computers for teaching purposes, and on my Chromebook, so this is really a case of "scratch your own itch" software.
- This is really cool. Can I help with this?
- Yes you can! Any and all help is appreciated, but you'll need to digitally sign the Microsoft CLA first, so that we can contribute any fixes back upstream to the core repository.
- I've found a bug, where can I raise it?
- Bugs can be raised directly in Github at the issues page, but please ensure the bug is related to the installation on ARM and/or Chromebooks as per these scripts. Issues with the core product should be raised at Microsoft's official repository, so that they'll be fixed in the core (the fixes will propagate to these builds).
- So who maintains this site?
- I'm Jay. Nice to meet you. You can find my details in the contact section.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.