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

Git Clone URL: (read-only)
Package Base: visual-studio-code-bin
Description: Visual Studio Code: Editor for building and debugging modern web and cloud applications (official binary version)
Upstream URL:
Licenses: custom: commercial
Conflicts: visual-studio-code
Provides: visual-studio-code, visualstudiocode, vscode
Replaces: visual-studio-code
Submitter: dcelasun
Maintainer: dcelasun
Last Packager: dcelasun
Votes: 681
Popularity: 31.325362
First Submitted: 2017-12-18 19:14
Last Updated: 2018-07-13 05:36

Pinned Comments

dcelasun commented on 2017-11-15 06:20

FREQUENTLY ASKED QUESTIONS (read before flagging or commenting!)

  • 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.

  • 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 the package or the program itself, can I email you?

No. You won't get a reply. 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

malathion commented on 2018-06-06 15:47

This package stores lots of stuff in ~/.config/Code/ that doesn't seem to belong in $XDG_CONFIG_HOME.

In particular:

  • Cache/, CachedData/, CachedExtensions/, GPUCache/, logs/ : user-specific cached data should be in $XDG_CACHE_HOME ($HOME/.cache by default)

  • 'Local Storage'/, Backups/, User/workspaceStorage/, Cookies, Cookies-journal, machineid : This looks like stuff that belongs in $XDG_DATA_HOME ($HOME/.local/share by default)

  • storage.json : I'm not sure about this but it smells fishy :P

For a reference, see and and

Anonymous comment on 2018-06-06 08:07

The information you share is very useful. It is closely related to my work and has helped me grow. Thank you!

springer commented on 2018-05-31 18:40

Installing this package changed my xdg default for folders. xdg-open, which is also used by other programs, now opens VS Code for folders instead of my previous default (nautilus).

I don't think a software installation should change defaults. However, I don't know if this is a bug of this package or an upstream bug.

Manually restoring the previous default is possible with: xdg-mime default org.gnome.Nautilus.desktop inode/directory

dcelasun commented on 2018-05-29 07:46

@spacepluk: Fixed, thanks.

spacepluk commented on 2018-05-29 07:38

:: Checking visual-studio-code-bin integrity... ==> ERROR: provides contains invalid characters: ',,'

enihcam commented on 2018-05-20 03:08

As you can see, VSCode shifted from gtk2 to gtk3.

dcelasun commented on 2018-05-17 05:47

@Batou: This package follows upstream. Feel free to use other packages and/or a personal settings.json.

Batou commented on 2018-05-17 00:12

There is a massive amount of "telemetry" or spying going on within this package. Much more so than when you build the VSCode yourself (the code in AUR). I suggest to everyone to add some anti-telemetry preferences to their user settings at the bare minimum. You should also add some domain blocks to your hosts file. One of the options that's also problematic is the automatic update which is set by default. You should definitely not be updating from within this application so disable it.

I've created a short guide here: Maybe the maintainer should create ~/.config/Code/User/settings.json with the above defaults for all new installations?

welkie commented on 2018-05-09 01:34

I'm having a problem when I try to open an ASP.NET Core app. I've never had this problem before. In the bottom right corner I get a notification saying:

Some projects have trouble loading. Please review the output for more details.

There's more in the "show more output", including a stacktrace. This gist ( includes that, along with my versions of "mono" and "msbuild". I didn't have the msbuild package installed yet, but my troubleshooting led me to manually install that to try to solve this. This GitHub issue ( details the error when I reported it.

gururise commented on 2018-05-06 22:57

Using the C# plugin, I keep getting the following error: "The .NET CLI tools cannot be located. .NET Core debugging will not be enabled. Make sure .NET CLI tools are installed and on the path."

How do I resolve this?

All comments