![]() vscode directory, you can use a workspace to do the same thing. But if you don't want to create (and perhaps have to git-ignore) the resulting. The associated settings for this are stored in a workspace file, which you can save anywhereĮdit to add more info: often, it's not necessary to explicitly use workspaces unless you want multi-root windows, as VSCode can just save settings to the folder instead. Perhaps 2 different, but related projects, or an application project and a related library project. vscode sub-directory.īut with Workspaces, you can have multiple directories, which might be in completely unrelated places in your filesystem, as "multiple roots" of the VSCode window. ![]() If you make Folder-specific settings in that directory, they'll be stored in a. Normally when you use VSCode, you open it up with a particular directory (e.g., a project). By creating a specific workspace, you now have the ability to set Settings for it separate from those other layers. While the other layers are "natural" (they exist, regardless - every file is in a Folder, so you can set Settings for that folder), Workspaces are "intentional". This allows you to have settings that just apply to a folder, or across an entire server, etc. So at any level, you can override a VSCode setting from a higher level, with a more-specific one. The VSCode settings domains are hierarchical, starting with User, then Remote (if you're connected to a remote server using VSCode Remote Development extensions) per-server, then Workspace, then Folder. In the simplest sense, a workspace is a domain of VSCode settings.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |