![\"Mascote](\"\/wp-content\/uploads\/2026\/09\/vscode-v4.webp\")
<\/p>\n<\/p>\n
.deb<\/code> standalone file and mixed up two different products. It has been rewritten: the correct method today is the official apt repository<\/strong>, which updates along with the system \u2014 and it is worth knowing there is an alternative build without telemetry.<\/div>\nThe Visual Studio Code<\/strong> is the most widely used editor in the world, runs well on Linux and is free. This guide shows how to install it in a way that stays up to date automatically, what to do next and the difference between the Microsoft binary and VSCodium<\/strong>.<\/p>\n<\/p>\n
First: VS Code is not Visual Studio<\/h2>\n
The names are confusing, but they are different products:<\/p>\n
\n- Visual Studio Code<\/strong> \u2014 a lightweight, cross-platform code editor, written in TypeScript on Electron. This is the one that runs on Linux.<\/li>\n
- Visual Studio<\/strong> (without \u201cCode\u201d) \u2014 Microsoft\u2019s heavyweight IDE for .NET, C++ and C#, in Community, Professional and Enterprise editions. It does not exist for Linux<\/strong>. Anyone who needs .NET on Linux uses the SDK from the command line \u2014 the topic of the post installing .NET on Linux<\/a> \u2014 with VS Code on top.<\/li>\n<\/ul>\n
Installing from the official repository (recommended)<\/h2>\n
This is the right path: register the Microsoft repository, and from then on the editor updates along with the system\u2019s `apt upgrade`, without hunting for a new `.deb` for each version.<\/p>\n
sudo apt install wget gpg\n\nwget -qO- https:\/\/packages.microsoft.com\/keys\/microsoft.asc \n | sudo gpg --dearmor -o \/usr\/share\/keyrings\/microsoft.gpg\n<\/code><\/pre>\nNow the repository file. Recent distributions use the format deb822<\/code>, more readable than the old single line:<\/p>\nsudo tee \/etc\/apt\/sources.list.d\/vscode.sources > \/dev\/null <<'FIM'\nTypes: deb\nURIs: https:\/\/packages.microsoft.com\/repos\/code\nSuites: stable\nComponents: main\nArchitectures: amd64,arm64,armhf\nSigned-By: \/usr\/share\/keyrings\/microsoft.gpg\nFIM\n\nsudo apt update\nsudo apt install code\n<\/code><\/pre>\nNotice Architectures<\/code>: in addition to the usual amd64<\/code> , the repository serves arm64<\/code>. In other words, it works on a Raspberry Pi 4\/5 with 64 bits and on ARM servers, not just on PCs.<\/p>\nOther methods<\/h2>\n# snap (vem pronto no Ubuntu)\nsudo snap install --classic code\n\n# flatpak, pela Flathub\nflatpak install flathub com.visualstudio.code\n\n# .deb avulso, quando voc\u00ea precisa de uma vers\u00e3o espec\u00edfica\nsudo apt install .\/code_1.XX.X_amd64.deb\n<\/code><\/pre>\nThe --classic<\/code> in snap is not decorative: without it the editor is confined and cannot see your files or the compilers installed on the system. Flatpak has the same sandbox limitation and requires granting folder access \u2014 for an editor, which needs to reach the entire project and build tools, the apt repository remains the path of least resistance.<\/p>\nVSCodium: the same editor, without telemetry<\/h2>\n
Here is the part the 2017 post did not mention. The VS Code source code is on github.com\/microsoft\/vscode<\/a> under MIT license<\/strong>. But the binary Microsoft distributes is not just that compiled code: at build time it adds what its own documentation calls \u201cMicrosoft-specific functionality\u201d \u2014 telemetry, the extension gallery and branding<\/strong> \u2014 and distributes it under a proprietary license.<\/p>\nThe VSCodium<\/a> is exactly the same source code compiled without<\/em> those additions: MIT binary, telemetry disabled. Install it the same way:<\/p>\nwget -qO- https:\/\/gitlab.com\/paulcarroty\/vscodium-deb-rpm-repo\/raw\/master\/pub.gpg \n | gpg --dearmor \n | sudo dd of=\/usr\/share\/keyrings\/vscodium-archive-keyring.gpg\n\nsudo tee \/etc\/apt\/sources.list.d\/vscodium.sources > \/dev\/null <<'FIM'\nTypes: deb\nURIs: https:\/\/download.vscodium.com\/debs\nSuites: vscodium\nComponents: main\nArchitectures: amd64 arm64\nSigned-by: \/usr\/share\/keyrings\/vscodium-archive-keyring.gpg\nFIM\n\nsudo apt update\nsudo apt install codium\n<\/code><\/pre>\nThe trade-off: the official Microsoft marketplace has terms of use that only allow its own client, so VSCodium points to Open VSX<\/strong>, an open catalog. Most popular extensions are there, but some \u2014 generally Microsoft\u2019s own, such as those for C++ and remote access \u2014 are not. Before migrating, check whether the extension you depend on exists on Open VSX.<\/p>\nAfter installation<\/h2>\n
The first practical benefit is opening a project directly from the terminal, without going through the file manager:<\/p>\n
code . # abre a pasta atual como projeto\ncode arquivo.py # abre um arquivo\ncode --diff a.txt b.txt # compara dois arquivos lado a lado\ncode --list-extensions # o que voc\u00ea j\u00e1 tem instalado\n<\/code><\/pre>\nExtensions from the command line, useful for reproducing your environment on a new machine:<\/p>\n
code --install-extension ms-python.python\ncode --install-extension golang.go\ncode --install-extension rust-lang.rust-analyzer\n\n# levar sua lista para outra m\u00e1quina\ncode --list-extensions > extensoes.txt\nxargs -n1 code --install-extension < extensoes.txt\n<\/code><\/pre>\nAnd the feature that turns the editor into a server administration tool: Remote \u2014 SSH<\/strong>. With it you open a folder on a remote server and edit as though it were local \u2014 with syntax highlighting, an integrated terminal and a debugger running there<\/em>, not here. For anyone who administers Linux machines over SSH, it is the difference between editing YAML in vim<\/code> over a slow connection and having the entire project open on screen.<\/p>\ncode --install-extension ms-vscode-remote.remote-ssh\n# depois: F1 \u2192 \"Remote-SSH: Connect to Host\" \u2192 usa o seu ~\/.ssh\/config\n<\/code><\/pre>\nIt reads your ~\/.ssh\/config<\/code>, so the host aliases you already use appear in the list. This is one of the extensions not on Open VSX \u2014 a concrete case where Microsoft\u2019s build wins over VSCodium.<\/p>\nShortcuts worth learning<\/h2>\n\nCtrl+P<\/code> \u2014 open a file by name without taking your hands off the keyboard<\/li>\nCtrl+Shift+P<\/code> \u2014 the command palette: everything the editor can do, searchable by text<\/li>\nCtrl+`<\/code> \u2014 toggle the integrated terminal<\/li>\nCtrl+Shift+F<\/code> \u2014 search all project files<\/li>\nF2<\/code> \u2014 rename a symbol throughout the project, respecting scope<\/li>\nAlt+clique<\/code> \u2014 multiple cursors, to edit several lines at once<\/li>\n<\/ul>\nTo keep going<\/h2>\n\n- Installing .NET on Linux<\/a> \u2014 the SDK that replaces Visual Studio here<\/li>\n
- AI assistants on the Linux terminal<\/a><\/li>\n
- Go on Ubuntu<\/a> and Rust on Ubuntu<\/a> \u2014 two languages with good editor extensions<\/li>\n
- Official Linux installation documentation<\/a> \u00b7 VSCodium<\/a> \u00b7 Open VSX<\/a><\/li>\n<\/ul>","protected":false},"excerpt":{"rendered":"
Visual Studio Code is the world\u2019s most widely used editor, runs well on Linux, and is free. This guide shows how to install it so it stays up to date automatically, what to do right afterward, and what the difference is \u2026 Read more<\/a><\/p>","protected":false},"author":0,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[45,2,3],"tags":[405,14,262,397,5,404,406],"class_list":["post-128","post","type-post","status-publish","format-standard","hentry","category-desenv","category-linux","category-ubuntu","tag-editor","tag-howto","tag-microsoft","tag-programacao","tag-ubuntu","tag-vscode","tag-vscodium"],"_links":{"self":[{"href":"https:\/\/www.linuxpro.com.br\/en\/wp-json\/wp\/v2\/posts\/128","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.linuxpro.com.br\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.linuxpro.com.br\/en\/wp-json\/wp\/v2\/types\/post"}],"replies":[{"embeddable":true,"href":"https:\/\/www.linuxpro.com.br\/en\/wp-json\/wp\/v2\/comments?post=128"}],"version-history":[{"count":6,"href":"https:\/\/www.linuxpro.com.br\/en\/wp-json\/wp\/v2\/posts\/128\/revisions"}],"predecessor-version":[{"id":1084,"href":"https:\/\/www.linuxpro.com.br\/en\/wp-json\/wp\/v2\/posts\/128\/revisions\/1084"}],"wp:attachment":[{"href":"https:\/\/www.linuxpro.com.br\/en\/wp-json\/wp\/v2\/media?parent=128"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.linuxpro.com.br\/en\/wp-json\/wp\/v2\/categories?post=128"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.linuxpro.com.br\/en\/wp-json\/wp\/v2\/tags?post=128"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}