Package Details: visual-studio-code-bin 1.39.2-1

Git Clone URL: (read-only)
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: 855
Popularity: 12.888280
First Submitted: 2017-12-18 19:14
Last Updated: 2019-10-16 06:35

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 etc), 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.

  • What happened to visual-studio-code?

It got renamed with a -bin suffix. If you have the original package installed, you will be prompted to delete it when you install this package for the first time.

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 9 ... Next › Last »

dcelasun commented on 2019-05-17 06:58

@manuelino should be fixed now.

manuelino commented on 2019-05-17 06:52


Thanks for the workaround, but as is it does not work, because the image under hicolor is named "code.png", while the desktop entry refers to it as "visual-studio-code".

Simply renaming the image and updating the icon cache sorts it out. Also, the image has executable bits set (0755 rather than 0644).

dcelasun commented on 2019-05-16 21:26

@manuelino I've added a workaround, please try with the latest version and report back.

manuelino commented on 2019-05-03 08:32

@dcelasun Here is the link to the issue:

dcelasun commented on 2019-05-02 20:13

@manuelino, can you link me to that issue? I wouldn't resize it at build time (it would require a dependency), but I'd be willing to ship a static image with the PKGBUILD.

manuelino commented on 2019-05-02 14:24

It seems that there is a bug in the current XFCE packages, which causes desktop launchers not to display icons if they are placed under /usr/share/icons and not under a theme. It also breaks if moving the icon under the hicolor theme but under a 1024x1024 directory.

Is there any chance the icon could be resized at build time to 512x512 and installed under the hicolor theme? I understand this is really an issue with the DE (I have reported this to the devs), but this packages is the only one I have seen in a while that does not store the icons under the hicolor theme and that has such a large image.

If this looks feasible, I am willing to provide a patch. Since the proposed path is standardized by the Icon Theme Specification, it should have no negative impact on other DE's.

saverio commented on 2019-04-22 17:57

@cogwerkz Many thanks... I didn't read the FREQUENTLY ASKED QUESTIONS at the top. The FAQ is very useful and it must be red by all users before posting repetitive comments, sorry it was my issue.

cogwerkz commented on 2019-04-21 18:36

@saverio The one in the Community repo is the fully open source version, meaning it only has the open source base, and hasn't got direct access to proprietary elements like the marketplace.

This version has a commercial license, which is something you'll never see on anything in the official repos.

saverio commented on 2019-04-21 18:02

Hi dcelasun, is there any difference between this AUR maintained package and the one available in the official Arch Community repo? (

As far as I can see, both Community and your AUR package have the same version...

Rainer commented on 2019-04-07 10:02

I'm on arch 32Bit. I downloaded the snapshot and installed the package with makepkg -sirc. Everything worked fine. If I start either from the menu or with "code" from the terminal it starts but all I get is a blank screen. Did I missed something?