![]() ![]()
Note as well that the Windows ZIP archive does not support auto update.Ĭreate a symbolic link to the folder %USERPROFILE%\.vscode\extensions under the Visual Studio Code install path. #Visual studio code extensions directory portable#Portable mode is only supported on the Windows ZIP (.zip) archive. Note: Do not attempt to configure portable mode on an installation from the Windows User or System installers. Note: On Insiders, the folder should be named code-insiders-portable-data. Developers can use extensions to add languages, debuggers, development tools. Make sure you remove the quarantine attribute, if portable mode doesn't seem to work: xattr -dr Visual\ Studio\ Code.app One of the most useful features of the Visual Studio Code is extensions. Portable mode won't work if your application is in quarantine, which happens by default if you just downloaded Visual Studio Code. The default folder name is code-portable-data: Since the folder will be alongside the application, you need to name it specifically so that Code can find it. ![]() On macOS, you need to place the data folder as a sibling of the application itself. This is useful for updating your portable Visual Studio Code version: simply move the data folder to a newer extracted version of Visual Studio Code. This will show you a list of the most popular VS Code extensions on the VS Code Marketplace. Bring up the Extensions view by clicking on the Extensions icon in the Activity Bar on the side of VS Code or the View: Extensions command ( Ctrl Shift X ). The data folder can be moved to other Visual Studio Code installations. You can browse and install extensions from within VS Code. It works under Windows, Linux, and macOS: Enable Portable Mode Windows and LinuxĪfter unzipping the Visual Studio Code download, simply create a data folder within Visual Studio Code's folder:įrom then on, that folder will be used to contain all Visual Studio Code data, including session state, preferences, extensions, etc. Another option is to launch VS Code with the -extensions-dir CLI option, which is documented here. Here is for the user data directory: "D:\Microsoft VS Code\Code.exe" -user-data-dir="D:\Microsoft VS Code\settings"Īccessing the 'Target' field is done by right-clicking the shortcut and choosing 'Properties'Īnyway, there's a simpler solution to that problem - just use the portable version of Visual Studio Code. One option is to create a symbolic link from the default extensions folder to a place on your D drive. ![]() vscode/settings.json file and provide the project directory as. So mine looks like this: "D:\Microsoft VS Code\Code.exe" -extensions-dir="D:\Microsoft VS Code\extensions" Install the Sorbet extension from the VS Code extension marketplace. Where DRIVERLETTER and VSCODE are the corresponding drive and directory where Visual Studio Code is installed. user-data-dir="DRIVELETTER:\VSCODE\settings" What I did - after installing Visual Studio Code for the first time, I checked the documentation and added at the end of 'Target' field of editor's shortcut the following (there's a space before the two dashes): -extensions-dir="DRIVELETTER:\VSCODE\extensions" Code -extensions-dir 'new_directory_to_set' ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |