Package Details: visual-studio-code-bin 1.43.2-2

Git Clone URL: (read-only, click to copy)
Package Base: visual-studio-code-bin
Description: Visual Studio Code (vscode): Editor for building and debugging modern web and cloud applications (official binary version)
Upstream URL:
Licenses: custom: commercial
Conflicts: code
Provides: code
Submitter: dcelasun
Maintainer: dcelasun
Last Packager: dcelasun
Votes: 877
Popularity: 8.07
First Submitted: 2017-12-18 19:14
Last Updated: 2020-03-30 09:29

Pinned Comments

dcelasun commented on 2017-11-15 06:20

FREQUENTLY ASKED QUESTIONS (read before flagging or commenting!)

  • What is the difference between this package and the one in the community repo?

This is the official binary distribution from Microsoft. The one in the community repo is an unofficial build made from source. Beyond the license difference and branding, there are some proprietary features not available in the open source version.

  • There is a new version out, why is the package not updated?

Please check this page before flagging as out-of-date. If there is no new version on that page, it's not yet released. A tag on Github is NOT a release! If you can see the new version on the updates page but the AUR package is still not updated, flag it and give it time. It's usually done within a day or two.

  • I'm using an AUR helper (yay, yaourt etc.) and I can't install it. Why?

Sometimes AUR helpers do weird things. Download the tarball and install it manually with makepkg -si. If that works, report the problem to your AUR helper's upstream, not here.

  • When I install this package xdg-open uses vscode, not my file manager! How do I fix this?

Install shared-mime-info-gnome. Also see this reddit thread.

  • Why is $X a dependency? I don't like it.

Just because $X is not required to open the app, doesn't mean there is nothing that depends on it. Always search the comment history on AUR to see if that dependency has been previously discussed before writing your own comment. Still nothing? Then use namcap to make sure it's really not needed. If namcap doesn't complain, please leave a comment here and I'll investigate.

  • Something is broken with the app, where do I report it?

The problem might be a packaging issue (wrong paths, dependencies, icons), so please write a comment here first. If you don't get a reply, or if someone says it's an upstream issue, you can report it on Github.

  • I have a problem with this package, can I email you?

No, you won't get a reply. Please stop doing this. Leave a comment here instead and be patient.

Latest Comments

1 2 3 4 5 6 ... Next › Last »

dcelasun commented on 2020-03-31 22:09


Nowaker commented on 2020-03-31 22:07

Would you mind creating visual-studio-code-insiders-bin? The Insiders version of the package would be very similar to this one - only pointing to a different URL, and having sha256sums=SKIP since Insiders is a daily build. Thank you.

dcelasun commented on 2020-03-30 09:36

@op3 done, let me know if it doesn't work as expected.

op3 commented on 2020-03-29 11:02

The upstream code package is providing a .desktop file that includes a “New Empty Window” option. I find this very useful and would appreciate if you introduced this feature to the .desktop file provided with this package.

dcelasun commented on 2020-03-25 19:17

@Xaekai I'm not sure how up-to-date this page is, but Micrososft maintains such a list here.

Xaekai commented on 2020-03-25 19:14

I request that "proprietary features" in your FAQ be linkified to an enumeration of those features if possible. Thank you.

Det commented on 2020-03-24 20:50

Wow, ok, cool. Does that warrant like a FAQ mention?

dcelasun commented on 2020-03-24 20:39

@Det this package is the official build from Microsoft and can use the name "Visual Studio Code". The package in community is an unofficial build and isn't allowed to use Microsoft branding so it's only called "code".

Det commented on 2020-03-24 20:36

So wait, what was the reason again this had a different name from community/code?

Rowisi commented on 2020-02-10 13:50

@dcelasun @jaysistar

I was the maintainer of vscodium-bin-multiarch. I have now added ARM support into vscodium-bin and deleted my package.

From now, vscodium-bin supports ARM and ARM64.