vscodium / vscodium

binary releases of VS Code without MS branding/telemetry/licensing

VSCodium

Free/Libre Open Source Software Binaries of VS Code

This is not a fork. This is a repository of scripts to automatically build Microsoft's vscode repository into freely-licensed binaries with a community-driven default configuration.

Table of Contents

• Download/Install
  • Install with Brew
  • Install with Windows Package Manager (WinGet)
  • Install with Chocolatey
  • Install with Scoop
  • Install with snap
  • Install with Package Manager
  • Install on Arch Linux
  • Flatpak Option
• Build
• Why Does This Exist
• More Info
• Supported Platforms

Download/Install

🎉 🎉 Download latest release here: stable or insiders 🎉 🎉

More info / helpful tips are here.

Install with Brew (Mac)

If you are on a Mac and have Homebrew installed:

# stable
brew install --cask vscodium

# insiders
brew tap homebrew/cask-versions
brew install --cask vscodium-insiders

Note for macOS users: if you can't open the App, please read the following troubleshooting.

Install with Windows Package Manager (WinGet)

If you use Windows and have Windows Package Manager installed:

:: stable
winget install -e --id VSCodium.VSCodium

:: insider
winget install -e --id VSCodium.VSCodium.Insiders

Install with Chocolatey (Windows)

If you use Windows and have Chocolatey installed (thanks to @Thilas):

:: stable
choco install vscodium

:: insider
choco install vscodium-insiders

Install with Scoop (Windows)

If you use Windows and have Scoop installed:

scoop bucket add extras
scoop install vscodium

Install with snap (GNU/Linux)

VSCodium is available in the Snap Store as Codium, thanks to the help of the Snapcrafters community. If your GNU/Linux distribution has support for snaps:

snap install codium --classic

Install with Package Manager (GNU/Linux)

You can always install using the downloads (deb, rpm, tar) on the releases page for stable or insiders, but you can also install using your favorite package manager and get automatic updates.

@paulcarroty has set up a repository with instructions for apt, dnf and zypper here.

Any issues installing VSCodium using your package manager should be directed to that repository's issue tracker.

Install on Arch Linux

VSCodium is available in AUR, maintained by @binex-dsk as package vscodium-bin (stable) and as vscodium-insiders-bin.

If you want to save disk space by having VSCodium use the Electron system-wide, you also have vscodium-electron, maintained by @m00nw4tch3r.

An alternative package vscodium-git, maintained by @cedricroijakkers, is also available should you wish to compile from source yourself.

Flatpak Option (GNU/Linux)

VSCodium is available as a Flatpak app here and the build repo is here. If your distribution has support for flatpak, and you have enabled the flathub repo:

flatpak install flathub com.vscodium.codium
flatpak run com.vscodium.codium

Build

Build instructions can be found here

Why Does This Exist

This repository contains build files to generate free release binaries of Microsoft's VS Code. When we speak of "free software", we're talking about freedom, not price.

Microsoft's releases of Visual Studio Code are licensed under this not-FLOSS license and contain telemetry/tracking. According to this comment from a Visual Studio Code maintainer:

When we [Microsoft] build Visual Studio Code, we do exactly this. We clone the vscode repository, we lay down a customized product.json that has Microsoft specific functionality (telemetry, gallery, logo, etc.), and then produce a build that we release under our license.

When you clone and build from the vscode repo, none of these endpoints are configured in the default product.json. Therefore, you generate a "clean" build, without the Microsoft customizations, which is by default licensed under the MIT license

This repo exists so that you don't have to download+build from source. The build scripts in this repo clone Microsoft's vscode repo, run the build commands, and upload the resulting binaries to GitHub releases. These binaries are licensed under the MIT license. Telemetry is disabled.

If you want to build from source yourself, head over to Microsoft's vscode repo and follow their instructions. This repo exists to make it easier to get the latest version of MIT-licensed VS Code.

Microsoft's build process (which we are running to build the binaries) does download additional files. Those packages downloaded during build are:

• Pre-built extensions from the GitHub:
  • ms-vscode.js-debug-companion
  • ms-vscode.js-debug
  • ms-vscode.vscode-js-profile-table
• From Electron releases (using gulp-atom-electron)
  • electron
  • ffmpeg

More Info

Documentation

For more information on getting all the telemetry disabled, tips for migrating from Visual Studio Code to VSCodium and more, have a look at the Docs page page.

Troubleshooting

If you have any issue, please check the Troubleshooting page or the existing issues.

Extensions and the Marketplace

According to the VS Code Marketplace Terms of Use, you may only install and use Marketplace Offerings with Visual Studio Products and Services. For this reason, VSCodium uses open-vsx.org, an open source registry for VS Code extensions. See the Extensions + Marketplace section on the Docs page for more details.

Please note that some Visual Studio Code extensions have licenses that restrict their use to the official Visual Studio Code builds and therefore do not work with VSCodium. See this note on the Docs page for what's been found so far and possible workarounds.

How are the VSCodium binaries built?

If you would like to see the commands we run to build vscode into VSCodium binaries, have a look at the workflow files in .github/workflows for Windows, GNU/Linux and macOS. These build files call all the other scripts in the repo. If you find something that doesn't make sense, feel free to ask about it on Gitter.

The builds are run every day, but exit early if there isn't a new release from Microsoft.

Supported Platforms

The minimal version is limited by the core component Electron, you may want to check its platform prerequisites.

• macOS (zip, dmg) macOS 10.15 or newer x64
• macOS (zip, dmg) macOS 11.0 or newer arm64
• GNU/Linux x64 (deb, rpm, AppImage, snap, tar.gz)
• GNU/Linux arm64 (deb, rpm, snap, tar.gz)
• GNU/Linux armhf (deb, rpm, tar.gz)
• Windows 10 / Server 2012 R2 or newer x64
• Windows 10 / Server 2012 R2 or newer arm64

Donate

If you would like to support the development of VSCodium, feel free to send BTC to 3PgjE95yzBDTrSPxPiqoxSgZFuKPPAix1N (@stripedpajamas).

Special thanks

@jaredreich	for the logo
@PalinuroSec	for CDN and domain name
	for providing a Mac mini M1

License

MIT

vscodium's Issues

Mac installation: adding code-oss in the path

VScode installs code in the path, so that it's very convenient to open it from any directory:

~/in-my-project $ code .

opens VSCode for in-my-project

ls -la /usr/local/bin/code
lrwxr-xr-x 1 <user> <group> 68 May 17  2017 /usr/local/bin/code -> '/Applications/Visual Studio Code.app/Contents/Resources/app/bin/code'

It'd be awesome if the brew installation would do the same.

Documentation concerning macOS defaults

I just had to search through all the defaults on my mac to find the proper name for defaults for this app. I was trying to turn of press & hold so the vim plugin was actually useable.

Not really sure where this info should live, but it would be nice to let folks know the right name for that, since all the answers online assume you're using the MS version. In any case, here's what I had to do make it work:

defaults write com.visualstudio.code.oss ApplePressAndHoldEnabled -bool false

The MS version uses com.microsoft.VSCode.

Thanks

Cooperate with com.visualstudio.code.oss from flathub

@amtlib-dot-dll is doing a great job packaging the open source version of vscode to flathub.org (https://flathub.org/apps/details/com.visualstudio.code.oss).

Maybe vscodium contributors can merge efforts with him to avoid confusion between various OSS versions.

I propose to:

• Use the same project name. We could rename vscodium to CodeOSS, the contrary or pick another neat name.
• Merge doc and code if necessary, under the same repo, and indicate that a flatpak build is available on flathub.org.
• Create a static site to showcase the product and link to installation packages

vscodium adds microsoft apt repository

When installing vscodium the microsoft apt repository is added to the system. I think this should not be done since most people are using vscodium because they don't want to use vscode from microsoft.

https://github.com/Microsoft/vscode/blob/5db58b3867bfff05e6f4d874753ef960e9a59c4a/resources/linux/debian/postinst.template#L68

This issue is maybe related to #1 and #5

Better Icon

We should come up with a better icon for the FOSS version. The FOSS icon is really ugly. That would be sugar on top of the cake. 👍

GPG sign for Linux packages

The latest (minimum) Linux packages aren't signed - https://gitlab.com/paulcarroty/vscodium-deb-rpm-repo/issues/1

I can sign them with my repository key, but then verifications by checksums will be broken. So, I'd suggest sign them after build like MS did.

Linux tar packages named Vscode

Minor issue but why is the tar package named Vscode instead of Vscodium?

VSCode-linux-x64-1.30.2.tar.gz

Building VSCodium on Ubuntu 16.04 LTS

Hi,

I'm looking to build VSCodium on Ubuntu 16.04 LTS.

Here's what I've done so far:

git clone https://github.com/VSCodium/vscodium
cd vscodium

The scripts seem pretty straightforward. I'm going to make an educated guess that I should run install_deps.sh, then run get_repo.sh, then run SHOULD_BUILD=yes ./build.sh

./install_deps.sh seemed to work fine. \o/
./get_repo.sh says it's cloned and checked out 1.27.1.

But when I run SHOULD_BUILD=yes ./build.sh, I get some errors:

SHOULD_BUILD=yes ./build.sh                                                                                                                                                                                                                  
./build.sh: line 5: yarn: command not found
./build.sh: line 7: jq: command not found
./build.sh: line 14: npx: command not found
./build.sh: line 15: npx: command not found
./build.sh: line 16: npx: command not found

Okay, cool, so I assume I'll need to install those...

sudo apt-get install yarn jq npx
Reading package lists... Done
Building dependency tree       
Reading state information... Done
E: Unable to locate package yarn
E: Unable to locate package npx

It looks like ./install_deps.sh is not as thorough as it should be.

Which packages do I need to install in order to build?

What data will telemetry collect?

Thanks.

Needs build instructions

It would be nice to have some instructions for manually building vscodium on each OS.

Could you discuss in README if telemetry features are included or disabled in builds?

Latest Release Missing OSX

The 1.26.1 release is missing a binary for Mac OS X.

Linux 32-bit builds are failing as of 1.31.0

Seems like we might be missing a 32-bit package somewhere in the install_deps section. Error from Travis:

error /home/travis/build/VSCodium/vscodium/vscode/node_modules/keytar: Command failed.
Exit code: 1
Command: prebuild-install || node-gyp rebuild
Arguments: 
Directory: /home/travis/build/VSCodium/vscodium/vscode/node_modules/keytar
Output:
/home/travis/build/VSCodium/vscodium/vscode/node_modules/node-abi/index.js:30
  throw new Error('Could not detect abi for version ' + target + ' and runtime ' + runtime + '.  Updating "node-abi" might help solve this issue if it is a new release of ' + runtime)
  ^
Error: Could not detect abi for version 3.1.2 and runtime electron.  Updating "node-abi" might help solve this issue if it is a new release of electron
    at getAbi (/home/travis/build/VSCodium/vscodium/vscode/node_modules/node-abi/index.js:30:9)
    at module.exports (/home/travis/build/VSCodium/vscodium/vscode/node_modules/prebuild-install/rc.js:64:12)
    at Object.<anonymous> (/home/travis/build/VSCodium/vscodium/vscode/node_modules/prebuild-install/bin.js:8:25)
    at Module._compile (module.js:653:30)
    at Object.Module._extensions..js (module.js:664:10)
    at Module.load (module.js:566:32)
    at tryModuleLoad (module.js:506:12)
    at Function.Module._load (module.js:498:3)
    at Function.Module.runMain (module.js:694:10)
    at startup (bootstrap_node.js:204:16)
gyp info it worked if it ends with ok
gyp info using [email protected]
gyp info using [email protected] | linux | x64
gyp http GET https://atom.io/download/electron/v3.1.2/iojs-v3.1.2-headers.tar.gz
gyp http 200 https://atom.io/download/electron/v3.1.2/iojs-v3.1.2-headers.tar.gz
gyp http GET https://atom.io/download/electron/v3.1.2/SHASUMS256.txt
gyp http 200 https://atom.io/download/electron/v3.1.2/SHASUMS256.txt
gyp info spawn /opt/pyenv/shims/python2
gyp info spawn args [ '/home/travis/.nvm/versions/node/v8.15.0/lib/node_modules/npm/node_modules/node-gyp/gyp/gyp_main.py',
gyp info spawn args   'binding.gyp',
gyp info spawn args   '-f',
gyp info spawn args   'make',
gyp info spawn args   '-I',
gyp info spawn args   '/home/travis/build/VSCodium/vscodium/vscode/node_modules/keytar/build/config.gypi',
gyp info spawn args   '-I',
gyp info spawn args   '/home/travis/.nvm/versions/node/v8.15.0/lib/node_modules/npm/node_modules/node-gyp/addon.gypi',
gyp info spawn args   '-I',
gyp info spawn args   '/home/travis/.node-gyp/iojs-3.1.2/common.gypi',
gyp info spawn args   '-Dlibrary=shared_library',
gyp info spawn args   '-Dvisibility=default',
gyp info spawn args   '-Dnode_root_dir=/home/travis/.node-gyp/iojs-3.1.2',
gyp info spawn args   '-Dnode_gyp_dir=/home/travis/.nvm/versions/node/v8.15.0/lib/node_modules/npm/node_modules/node-gyp',
gyp info spawn args   '-Dnode_lib_file=/home/travis/.node-gyp/iojs-3.1.2/<(target_arch)/iojs.lib',
gyp info spawn args   '-Dmodule_root_dir=/home/travis/build/VSCodium/vscodium/vscode/node_modules/keytar',
gyp info spawn args   '-Dnode_engine=v8',
gyp info spawn args   '--depth=.',
gyp info spawn args   '--no-parallel',
gyp info spawn args   '--generator-output',
gyp info spawn args   'build',
gyp info spawn args   '-Goutput_dir=.' ]
gyp info spawn make
gyp info spawn args [ 'BUILDTYPE=Release', '-C', 'build' ]
make: Entering directory `/home/travis/build/VSCodium/vscodium/vscode/node_modules/keytar/build'
  CXX(target) Release/obj.target/keytar/src/async.o
  CXX(target) Release/obj.target/keytar/src/main.o
  CXX(target) Release/obj.target/keytar/src/keytar_posix.o
  SOLINK_MODULE(target) Release/obj.target/keytar.node
/usr/bin/ld: cannot find -lsecret-1
/usr/bin/ld: cannot find -lgio-2.0
/usr/bin/ld: cannot find -lgobject-2.0
/usr/bin/ld: cannot find -lglib-2.0
collect2: error: ld returned 1 exit status
make: *** [Release/obj.target/keytar.node] Error 1
make: Leaving directory `/home/travis/build/VSCodium/vscodium/vscode/node_modules/keytar/build'
gyp ERR! build error 
gyp ERR! stack Error: `make` failed with exit code: 2
gyp ERR! stack     at ChildProcess.onExit (/home/travis/.nvm/versions/node/v8.15.0/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:262:23)
gyp ERR! stack     at emitTwo (events.js:126:13)
gyp ERR! stack     at ChildProcess.emit (events.js:214:7)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:198:12)
gyp ERR! System Linux 4.4.0-101-generic
gyp ERR! command "/home/travis/.nvm/versions/node/v8.15.0/bin/node" "/home/travis/.nvm/versions/node/v8.15.0/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /home/travis/build/VSCodium/vscodium/vscode/node_modules/keytar
gyp ERR! node -v v8.15.0
gyp ERR! node-gyp -v v3.8.0
gyp ERR! not ok

codium as app executable name instead of vscodium?

The titles, names, and executables in the official and OSS versions all are variations of code and code-oss respectively. Maybe we should keep the pattern by making the executable codium? Also I think the Visual Studio name is copyrighted by Microsoft, not sure, but we might as well be careful. Something else I like about the original code executable is that it's very quick to type, enabling commands like code ~/very/big/path feel more fluent and quick.

ARM64 packages don't work

I just installed the deb package, but the window is empty. I'm pretty sure that it's an issue with cross compiling upstream, since I ran another repository without the VSCodium changes and the issue persisted. For now, I think we should say that ARM64 packages cannot be built correctly yet.
I hope that the issue is fixed soon, but for now I guess we still won't be able to support ARM.
I tried to file an issue to Microsoft, but since I used the VSCodium build the issue was immediately closed, telling me that "please start by filing this issue to VSCodium." The issue is here if you're curious.

32-bit Windows packages.

I believe that Windows and Wine users will be happy if we provide 32-bit Windows packages. Any suggestions?

Bad system call

I recently installed Parrot Home KDE edition and configured the task.json, launch.json to work on c++ application and after building and compiling (F5) and get this message :

"[1] + Bad system call /usr/bin/gdb --interpreter=mi --tty=${DbgTerm} 0</tmp/Microsoft-MIEngine-In-wi527ekr.wtn 1>/tmp/Microsoft-MIEngine-Out-a7nqamb7.6wg

Press any key to continue..."

The thing is when I was using the MATE version everything was running fine.
I'm using the C/C++ extension from Microsft.

Migrate Windows Builds to New Platform

The last version with a build for Windows was 1.29. Both 1.30 and 1.30.1 don't have Windows packages.

CLI tool for vscodium

Are there plans to include a CLI tool for vscodium?

Cannot install in Mac

I'm trying to install with brew, but I get a SHA signature validation error. It's a new / clean Macbook (no previous vscodium installed)

This is the output (I have also tried 'brew update' with no change)

brew cask install vscodium
==> Satisfying dependencies
==> Downloading https://github.com/VSCodium/vscodium/releases/download/1.27.2/VS
==> Downloading from https://github-production-release-asset-2e65be.s3.amazonaws
######################################################################## 100.0%
==> Verifying SHA-256 checksum for Cask 'vscodium'.
==> Note: Running brew update may fix SHA-256 checksum errors.
Error: Checksum for Cask 'vscodium' does not match.

Expected: 53dee2011c3447756ceb4abe7c8b24b0d75bd55575ff4c1f56d853ff92004e7a
Actual: 12eab5a0387aa3042ee1e2f1dd6dd8b5ed68ef7f20f1b08eefee172ab209aa4c
File: /Users/myuser/Library/Caches/Homebrew/downloads/23252e6726991c70244c11a9f6116e142517dc6a683e96d25eacd2b64d49b9fc--VSCode-darwin-1.27.2.zip

Where are binaries for Win? (v.1.31)

Guys, you spend your time to compile for Apple, but didn't make binaries for Windows??? Serious? In what world do you live, Narnia?

Remove "VS" from name?

In regards to avoiding trademark issues, shouldn't the use of "VS" and "Visual Studio" be removed since that's the name of the Microsoft suite of products? Perhaps this should be named "Codium"? Thoughts?

Missing amd64.deb and el7.x86_64.rpm builds for 1.30.2

Hello,

Would it be possible to release the mentioned packages for v1.30.2?

Thanks

automatic telemetry removal

Even though we do not pass the telemetry build flags (and go out of our way to cripple the baked-in telemetry), Microsoft will still track usage by default. After installing VSCodium, you must manually disable telemetry in your settings file to stop it from sending tracking data to Microsoft.

Couldn't we just add a post-install script on every platform that automatically fixes the settings file? imo the whole purpose of this repo is telemetry is disabled. Even better, couldn't we just remove the code responsible for all aspects of telemetry? (I am sure there is some compelling reason for us not being able to do the latter, though)

Add brew cask

flatpak package

Is it possible to have vscodium as flatpak package in the near future?
thank,

`

Don't hard code the owner name and repo name in the Travis file

Currently we check the current releases by asking Github's API about VSCodium/vscodium's releases. This makes PRs more dangerous: a change to anything in the build matrix won't necessary be run through Travis because the binaries already exist.

Suggest using the $TRAVIS_REPO_SLUG env var which resolves to owner_name/repo_name in this API call. That way it will attempt all the builds during local development (provided a $GITHUB_TOKEN is defined).

AUR Package

Releasing this as an AUR package should not be too complicated. If I manage to find the time I will do a PR, in the meantime here's the issue.

VSCodium still accessing MS data gathering URLs

Running the latest build of VScodium on maxOS High Sierra.

As reported by the Little Snitch firewall. The binary is trying to access telemetry domains:

dc.services.visualstudio.com
dc.trafficmanager.net
vortex.data.microsoft.com

These are MS data gathering URLs. If one of the intentions of this project is to disable Telemetry it would be good to remove the communication to these.

There has been quite a bit of discussion around this on the VScode github page:

microsoft/vscode#16131

And on Reddit:

https://www.reddit.com/r/privacy/comments/80d8wu/just_realised_that_visual_studio_code_sends/

Telemetry in VSCode can be turned off, but not fully. Instead of disabling it altogether, they just register that you have it turned off, the server communication still happens.

The URL https://vortex.data.microsoft.com/collect/v1 is referenced in the VSCode source, so it could be replaced with something innocuous via Sed, that doesn't stop the other domains or any future ones they add. The others are likely added via the code's npm/build dependencies.

So it may be best to just simply add information on the "issue" and instructions to this projects README.MD to work around the problem by utilising your local hosts file to block the domains.

eg. Adding the line to your /etc/hosts file:

0.0.0.0 dc.services.visualstudio.com dc.trafficmanager.net vortex.data.microsoft.com

I'm interested in hearing what others think about this.

Key repeat in macos

Hi! just in case somebody else is looking for this, like me. I had to do this to enable key repeat in macOs.

defaults write com.visualstudio.code.oss ApplePressAndHoldEnabled -bool false

Windows builds

I don't have the time to make a PR, but for whoever does, I wanted to suggest using dockcross. I had excellent results with it in cross-compiling clib

VSCodium is more than twice the size of VSCode on MacOS

Hello,
I have been following vscodium for a couple of months now, and decided to give it a try, but…

In the screen both of them were just downloaded from vscodium and vscode.

I'm no expert of build pipelines, so I don't know if this is expected or not, but surely 430MB of size seems odd. Sorry if I get it wrong.

I also inspected both packages and inside VSCodium it appears to be three Electron.Framework bundles (by 70MB each), while in VSCode there is only one.

PPA?

Would be really, really great to see a PPA for this ;)

extension code-settings-sync fails

The extension code-settings-sync fails on vscodium.

The extension loads fine but fails to download settings (cf issue)

here is the error notification :

and the developer tools console :

Please document how to rebuild locally

Even though the purpose may be to release already built packages, I guess it would be better to document the build process, so that one can redo and not fear MitM...

AFAICS the .travis.yml can lead to needed commands ATM.

Hope this helps,

Setup RPM/Deb packages repositories

Maybe consider using a service like https://packagecloud.io which is free for open source projects ?

code-settings-sync extension cannot install extensions when using linux build

code-settings-sync extension cannot install extensions when using linux build. Tested on latest Ubuntu.

Steps to reproduce:

• Install latest linux build(either amd64 or x64)
• Try to sync extensions using latest code-settings-sync extension
• Extension installation fails with following error

"bin/code" --install-extension stevencl.addDocComments
Error: Command failed: "bin/code" --install-extension stevencl.addDocComments
/bin/sh: 1: bin/code: not found

Reason:

• MacOS and Windows(probably) have bin/code file inside installation path, whereas linux builds have bin/vscodium file
• code-settings-sync extension resolves bin/code binary inside installation folder(source)

Why does it resolves to bin/code?
Looks like issue with this line.

Eg: When debian build of VSCodium is installed, the vscodium binary path is resolved to /usr/share/vscodium/vscodium(initial myExt in above source) and then it resets it to bin/code.

I see that VSCodium support was merged to code-settings-sync here, this works fine. but this PR doesn't cover linux path resolution fix while installing extensions.

Does this issue belongs here or should I raise the issue in code-settings-sync repo?

event-stream issue

Details: dominictarr/event-stream#116

VSCode uses event-stream. Yesterday microsoft/vscode@981d0ab it was locked to secure version of package (3.3.4).

First version of new maintainer of event-stream appeared on Sep 5, 2018: dominictarr/event-stream@918d4a3

So releases (https://github.com/VSCodium/vscodium/releases) of vscodium from 1.27.1 to 1.29.1 are probably vulnerable. It depends on which versions it was built.

I don't know how to check it, if release that I installed from link above is vulnerable. There is no event-stream directory.

Any comments @stripedpajamas?

C# extension's debugging does not work 0x89720010

1. Install Microsoft's C# extension;
2. Create a folder with a Hello World C# program and build it;
3. Debug with the default Microsoft .NET Core Debugger (vsdbg) launch.json.

This message shows, and then nothing happens:

-------------------------------------------------------------------
You may only use the Microsoft .NET Core Debugger (vsdbg) with
Visual Studio Code, Visual Studio or Visual Studio for Mac software
to help you develop and test your applications.
-------------------------------------------------------------------

#71
dotnet/core#505
dotnet/vscode-csharp#2491

Fix:

• Easy
  Install omnisharp-vscode+netcoredbg extension (open-vsx.org) [src]

• ⚠️Doesn't work anymore⚠️ Advanced

  • Get https://github.com/Samsung/netcoredbg/
  • Edit "/your_proj_name/.vscode/launch.json"

  windows:

  {
  "version": "0.2.0",
  "configurations": [
          {
              "name": ".NET Core Launch (console)",
              "type": "coreclr",
              "request": "launch",
              "preLaunchTask": "build",
              "program": "${workspaceFolder}/bin/Debug/netcoreapp_your_ver/your_proj_name.dll",
              "args": [],
              "cwd": "${workspaceFolder}",
              "console": "integratedTerminal",
              "stopAtEntry": false,
              "internalConsoleOptions": "openOnSessionStart",
              "pipeTransport": {
                  "pipeCwd": "${workspaceFolder}",
                  "pipeProgram": "cmd",
                  "pipeArgs": ["/c"],
                  "debuggerPath": "C:\\\"Portable Bin\"\\netcoredbg\\netcoredbg.exe",
                  "quoteArgs": true
              }
          }
      ,]
  }
  

  linux, change this:

                  "pipeProgram": "bash",
                  "pipeArgs": ["-c"],
                  "debuggerPath": "/home/your_user_name/bin/netcoredbg/netcoredbg",
  

The Linux Deb/RPM repository

Hosted on Gitlab only. Scheduler and GPG sign works. Please test it and notify me about any issue.

I did it 'cause nobody are interested in #5 .

Need of a place to discuss about VSCodium

Hi guys!
Love the initiative, but struggle to find a place to discuss about it without opening issues(like a gitter channel or reddit sub, something like that). It would be nice to have one. Like the name and icon by the way.
Thank you !

Windows build doesn't show app icon in taskbar

code command is not symlinked to homebrew prefix

I think it's a good idea to symlink VSCodium.app/Contents/Resources/app/bin/code to Homebrew prefix so users can code <file-name> from the command line like they can do it with the original VSCode.

Rename macOS app to VSCodium.app

As pointed out in Homebrew/homebrew-cask#51727 (comment), the token has to be named the same way as the App file to be included in Homebrew Cask, this means either renaming the app file to VSCodium.app or changing the token to code-oss. I personally like the first option more as it includes the name of this project so it isn't that general.

Forgetting to set npm_config_arch on arm64

I might have an idea to why arm64 doesn't build properly. When you build on arm64, try setting npm_config_arch to arm64.

C++ extension's Windows debugging does not work

1. Install Microsoft's C/C++ extension;
2. Create a folder with a Hello World C++ program and build it;
3. Debug with the default C++/Windows (cppvsdbg) launch.json.

Expected behavior: (tested in MS VSCode)
The program is launched and can be debugged.

Actual behavior in VSCodium:
This message shows, and then nothing happens.

-------------------------------------------------------------------
You may only use the C/C++ Extension for Visual Studio Code with
Visual Studio Code, Visual Studio or Visual Studio for Mac software
to help you develop and test your applications.
-------------------------------------------------------------------

Is this because of the C/C++ extension's licensing? Is there any way around this?

The icon partially covers the title when pinned to the Start menu

The new icon covers most of the application title when pinned to the Start menu and resized to medium.

VSCodium shortcut between ST3 and VSCode

Window 10 (64-bit Enterprise 1709)

Auto Updating Support

How does auto updating works here? how are we pushing the new update?

also anyone has idea about how to configure custom update.channel?

ARM packages.

I'm helping with a GPL package manager for Chromebooks, called Chromebrew. It would really help if you could also create i686 and ARM tarballs. Thank you.

Make a notice in README that build process involves downloading binary packages and binary blobs

The build process involves downloading binary blobs and binary packages so it is not a complete build from source