From eb6ca84e218bdc0dba2a0bbf56b2754fac43ceaa Mon Sep 17 00:00:00 2001 From: Matthew Watkins Date: Thu, 15 Aug 2019 10:40:45 -0500 Subject: [PATCH 1/2] Update DOCS.md Added details on how to edit the product.json to enable extensions --- DOCS.md | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/DOCS.md b/DOCS.md index c213415..eee3075 100644 --- a/DOCS.md +++ b/DOCS.md @@ -42,6 +42,19 @@ The debugger provided with Microsoft's [C# extension](https://github.com/OmniSha A workaround exists to get debugging working in C# projects, by using Samsung's opensource [netcoredbg](https://github.com/Samsung/netcoredbg) package. See [this comment](https://github.com/VSCodium/vscodium/issues/82#issue-409806641) for instructions on how to set that up. +### Proprietary Extensions + +Like the debuggers mentioned above, some extensions you may find in the marketplace (like the [Remote Development Extensions](https://code.visualstudio.com/docs/remote/remote-overview)) only function the offical Visual Studio Code build. You can work around this by adding the extension's internal ID (found on the extension's page) to the `extensionAllowedProposedApi` property of the product.json in your VSCodium installation. For example: + +```json + "extensionAllowedProposedApi": [ + // ... + "ms-vscode-remote.vscode-remote-extensionpack", + "ms-vscode-remote.remote-wsl", + // ... + ], +``` + ## Migrating from Visual Studio Code to VSCodium VSCodium (and a freshly cloned copy of vscode built from source) stores its extension files in `~/.vscode-oss`. So if you currently have Visual Studio Code installed, your extensions won't automatically populate. You can reinstall your extensions from the Marketplace in VSCodium, or copy the `extensions` from `~/.vscode/extensions` to `~/.vscode-oss/extensions`. From f63fbe4292ce95c5b463d91457aa69fe9f407b4b Mon Sep 17 00:00:00 2001 From: Peter Squicciarini Date: Tue, 19 May 2020 22:01:41 -0700 Subject: [PATCH 2/2] Update DOCS.md --- DOCS.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/DOCS.md b/DOCS.md index eee3075..ef86de0 100644 --- a/DOCS.md +++ b/DOCS.md @@ -55,6 +55,8 @@ Like the debuggers mentioned above, some extensions you may find in the marketpl ], ``` +In some cases, the above change won't help because the extension is hard-coded to only work with the official Visual Studio Code product. + ## Migrating from Visual Studio Code to VSCodium VSCodium (and a freshly cloned copy of vscode built from source) stores its extension files in `~/.vscode-oss`. So if you currently have Visual Studio Code installed, your extensions won't automatically populate. You can reinstall your extensions from the Marketplace in VSCodium, or copy the `extensions` from `~/.vscode/extensions` to `~/.vscode-oss/extensions`.