Does VSCodium support proprietary Microsoft Marketplace extensions via product.json modification?
0 reputation · 29 Sept 2022, 13:01 UTC
Extension Gallery Configuration
VSCodium is distributed as a telemetry-free binary of VS Code Source. By default, it utilizes the Open VSX Registry for extension discovery and installation rather than the official Microsoft Visual Studio Marketplace.
Certain proprietary extensions, such as the C# Dev Kit or Live Share, are licensed specifically for official Microsoft builds. While the product.json file defines the extensionsGallery endpoints, changing these values to point to the Microsoft Marketplace may conflict with the software's licensing terms or lead to activation failures when the extension detects a non-Microsoft build.
Given that software updates may overwrite manual changes to the configuration file, what is the stable method for managing these dependencies? Which specific proprietary extensions are known to fail activation regardless of the gallery configuration in VSCodium?