Talk:Visual Studio Code

From ArchWiki

Has anyone gotten debugging working with code (open-source release)?

The official (AFAIK) debugger vsdbg is not included in the open-source release: https://aka.ms/VSCode-DotNet-DbgLicense

Is it not possible to download vsdbg manually? Eg. https://aka.ms/getvsdbgsh

Aude (talk) 08:27, 8 May 2019 (UTC) Reply

I managed to do it using netcoredbg ^AUR, though it's not very well documented.

The way I did was by adding this to the default launch configuration for .NET Core:

./.vscode/launch.json

...
"pipeTransport": {
 "pipeCwd": "${workspaceFolder}",
 "pipeProgram": "/usr/bin/bash",
 "pipeArgs": ["-c"],
 "debuggerPath": "/usr/bin/netcoredbg"
}
...

This will trick Code into running netcoredbg instead of vsdbg. From what I understand pipeTransport is used for SSH configurations, but you can use a shell just the same to take advantage of debuggerPath.

Luluco250 (talk) 16:11, 7 September 2019 (UTC) Reply

You can also now use vsdbg with unofficial builds of code by following this: Visual Studio Code#Patch vsdbg to bypass the validation check Kaydax (talk) 22:18, 14 January 2026 (UTC) Reply

The work-around is reported to have stopped working. Follow up topic #DotRush Debugger. Closing this item. --Indigo (talk) 18:40, 24 May 2026 (UTC) Reply

Re-open; see Special:diff/879793. --Indigo (talk) 19:50, 21 June 2026 (UTC) Reply

snap or flatpak are becoming the preferred method (by Microsoft) for the installation of Visual Studio Code.

There are two versions of Visual Studio Code: open-source OSS has a flatpak, and Microsoft vscode has a snap package.

For VSCode see https://snapcraft.io/code see below on how to install snap.

For OSS see https://flathub.org/apps/details/com.visualstudio.code.oss

Installation of Flatpak: Make sure to follow the setup guide before installing

$ sudo pacman --noconfirm --needed -S flatpak
$ flatpak install flathub com.visualstudio.code.oss

Run:

$ flatpak run com.visualstudio.code.oss

snap is currently only in AUR.

To get it to run using AppArmor

$ sudo systemctl enable --now apparmor.service

To get it to automatically update snap packages

$ sudo systemctl enable --now snapd.apparmor.service

$ sudo snap find vscode
Name Version Publisher Notes Summary
code 8795a988 vscode✓ classic Code editing. Redefined.
code-insiders a747d264 vscode✓ classic Code editing. Redefined.

To install Visual Studio Code

$ sudo snap install code --classic

or to install Visual Studio Code Insiders

$ sudo snap install code-insiders --classic

Flesh (talk) 18:49, 27 November 2019 (UTC) Reply

Update: AUR flag for Visual Studio Code Insiders is wrong because the package is self updating.

Dcelasun (talk)

.NET Core should ship with its own version of MSBuild. Right now, the AUR msbuild-stable package is quite out-of-date and on version 16.0, while the one that comes with .NET Core is version 16.4. I never had to install another version of MSBuild, and when I did it didn't use it. I think there's some way of manually specifying the MSBuild verison, but I couldn't find a good resource detailing how to do that.

For this reason I think it's reasonable to remove the section talking about a missing MSBuild, titled "Error from OmniSharp that MSBuild cannot be located"?

Also, (possibly when Mono is installed as well as .NET Core SDK,) everything in VSCode is unrecognised when debugging C# (and possibly the other .NET languages, Visual Basic and F#) , things like 'System' not found. The solution to this is to tell Omnisharp to ignore Mono, as detailed in this GitHub issue. This would be useful to add on to the troubleshooting section. TheSheepGuy (talk) 08:21, 7 June 2020 (UTC) Reply

This doesn't appear to be possible. The only way I've found to get Wayland working on vscode is to use the command code --enable-features=UseOzonePlatform --ozone-platform=wayland CRISPYricePC (talk) 14:15, 9 November 2021 (UTC) Reply

Doesn't work for me either. Pound Hash (talk) 06:07, 26 December 2021 (UTC) Reply

The same, doesn't work for me. I think as vscodium goes with its own electron (not using the system version), the flags file may be read from some other path. Ashark (talk) 22:42, 30 January 2022 (UTC) Reply

Installing VSCode prints a post-install message "Custom flags should be put directly in: ~/.config/code-flags.conf". I can put flags in there (I tested it to work with --enable-features=Vulkan), but trying with the Ozone platform causes it to refuse to start. Note, I use an NVIDIA card. CRISPYricePC (talk) 15:45, 24 March 2022 (UTC) Reply

Same issue, VS Code doesn't start when putting these flags in ~/.config/code-flags.conf, MacBook Pro 11,4 (Intel graphics). Jad042 (talk) 12:13, 3 April 2022 (UTC) Reply

Works fine for me with `echo '--ozone-platform-hint=auto' > ~/.config/code-flags.conf` C0rn3j (talk) 14:37, 13 September 2022 (UTC) Reply

Same here, added --enable-features=WaylandWindowDecorations and --ozone-platform-hint=auto to ~/.config/code-flags.conf and got it working with no issues. Capi Etheriel (talk) 02:57, 24 October 2022 (UTC) Reply

Plese use xeyes to detect the backend protocol. Visual-studio-code-bin may start with features in code-flags.conf, but the feature may not work Dingisoul (talk) 05:27, 17 January 2024 (UTC) Reply

Currently, all packages provide inconsistent names for what they provide. Some names are: code, vscode, codium, vscodium, visual-studio-code-git, and one package provides nothing.

Package	Provides	Notes
code	vscode
code-git	visual-studio-code-git
visual-studio-code-bin	code, vscode	Contains /usr/bin/code, which is a script that reads config and executes /opt/visual-studio-code/bin/code.
visual-studio-code-insiders-bin	-
vscodium	codium
vscodium-bin	codium, vscodium	Contains /usr/bin/codium and /usr/bin/vscodium. Does not contain /usr/bin/code.
vscodium-git	codium

I want to be able to easily determine which of flavor packages are installed with the command pacman -Q vscode. I guess all packages should provide list that vscode in provides array. Is that correct? If yes, I can write to all maintainers to edit their pkgbuilds. Ashark (talk) 16:35, 19 June 2022 (UTC) Reply

Do all of them include the /usr/bin/code excutable? If so, one might indeed argue they provide code. -- Alad (talk) 09:43, 20 June 2022 (UTC) Reply

I mean, should not they all provide a vscode like a virtual package? I can remember another example with DaVinci Resolve. There are several variants: studio, free, beta, stable. And they all provide davinci-resolve (which is convenient), and none of them contains /usr/bin/davinci-resolve binary. And even code package in official repo provides vscode while does not include /usr/bin/vscode Ashark (talk) 13:03, 20 June 2022 (UTC) Reply

I'm using dev containers with docker-desktop. No issues with visual-studio-code-bin ^AUR, but it just breaks using code . Don't know if there is a workaround or if I just have to use the microsoft build for this feature :/ Capi Etheriel (talk) 03:01, 24 October 2022 (UTC) Reply

From those symptoms it does sound like something is restricting it to the Microsoft licensed build. If you're feeling confident (or can find a source) you can add it to the list alongside Omnisharp, though the list isn't intended to be comprehensive. -- CodingKoopa (talk) 03:16, 24 October 2022 (UTC) Reply

Unfortunately, this workaround does not seem to be working for me using code OSS:

$ code-oss --enable-proposed-api ms-vscode-remote.remote-containers

...neither does editing the `/usr/lib/code/product.json` directly. This is quite confusing, I'm out of ideas. Ratijas (talk) 15:04, 27 May 2025 (UTC) Reply

I just updated the code package and code welcomed me with a clean new profile afterwards. It seems the config folder was silently changed from .config/.Code - OSS to .config/.Code

Can anyone confirm this is normal behavior or something to do with my setup? If so I'd add it to the settings section of the page, otherwise leave a note in the troubleshooting section.

--Kelvan (talk) 11:22, 14 August 2023 (UTC) Reply

No, current version of code (1.81.1-1) is using ~/.config/Code - OSS as always.

Hanabishi (talk) 11:27, 14 August 2023 (UTC) Reply

The last version of code-features ^AUR (1.81.1-1) changed the location of the data folder.

Marcelotsvaz (talk) 15:26, 14 August 2023 (UTC) Reply

So it should be changed back to stay consistent with the official code package on which it depends. — Lahwaacz (talk) 15:42, 14 August 2023 (UTC) Reply

there is a bug in the vscode( and codium) that only occur in the flatpak session https://github.com/flathub/com.vscodium.codium/issues/215, but it don't know if i'm allowed to put the workaround here in the wiki, or what are the guidelines for an edit only applied to flatpak Finlike (talk) 18:30, 17 October 2023 (UTC) Reply

This page does not mention flatpak at all, so it is not relevant here. — Lahwaacz (talk) 07:15, 21 October 2023 (UTC) Reply

When I'm trying to enable the [tunnel](https://code.visualstudio.com/docs/remote/tunnels) server, I get a complaint that `code-tunnel` is not installed. `pkgfile` also doesn't know any package it's in.

The flatpak package semes to have it, but that has its own problems as far as I can tell.

Has anyone else managed to make tunneling work?

Generalbaguette (talk) 01:46, 18 January 2024 (UTC) Reply

I added this section specifically as these files are not just about Wayland. There are dozens (hundreds?) of flags one can specify. I see you've added a merge flag Lahwaacz. So I added links to all the other supported flags. Any objections to removing the merge flag? Dcelasun (talk)

👍 but the footnote for vscodium still looks out of place.

OK. vscodium has a separate note in the Wayland section, so I removed both. Dcelasun (talk)

Thanks!

Followed the instructions in Unable to debug C# to set up netcoredbg but kept running into this error on attempting to debug.

Discovered the DotRush debugger which is available via the OpenVSX registry and this works for me with minimal tinkering, just needed to create the launch.json provided in the setup instructions at the root of my .NET project.

Any objections to me updating the Unable to debug C# section with this information? BudgetKratos (talk) 12:57, 23 May 2026 (UTC) Reply

Forgot to mention that I am using this extension with the official Code - OSS package so I'm fairly certain there is no use of propriety Microsoft extensions.

Happy to be proven wrong. BudgetKratos (talk) 12:59, 23 May 2026 (UTC) Reply

I have added Special:diff/876245 and now see the first talk item #vsdbg recently got a work-around that may be necessary/useful to apply to the current content as well. I have no opinion on the topic itself. --Indigo (talk) 17:02, 23 May 2026 (UTC) Reply

Ah, that makes the title much clearer, thanks.

As for the workaround, do you mean this patch? If so, going by the history, I see that it's been removed due to questionable legality. BudgetKratos (talk) 00:46, 24 May 2026 (UTC) Reply

Ok, I did not look at details and closed the other talk item now. Perhaps, the AUR package maintainer sorts the problem or someone comes with feedback. If you add your solution in the meantime, please do so as an alternative and leave the template regarding the AUR package. --Indigo (talk) 18:54, 24 May 2026 (UTC) Reply

Added Special:Diff/879773 at the end of the section. BudgetKratos (talk) 17:04, 21 June 2026 (UTC) Reply

Ok, Special:diff/879793 from me, you're welcome to adjust it. Let's close this item then. --Indigo (talk) 19:54, 21 June 2026 (UTC) Reply

Thank you BudgetKratos (talk) 04:30, 22 June 2026 (UTC) Reply

Retrieved from "https://wiki.archlinux.org/index.php?title=Talk:Visual_Studio_Code&oldid=879813"