Once a folder has been opened, VS Code will automatically keep track of things such as your open files and editor layout so the editor will be as you left it when you reopen that folder. You don't have to do anything for a folder to become a VS Code workspace other than open the folder with VS Code. Alternatively if you launch VS Code from a terminal, you can pass the path to a folder as the first argument to the code command for opening. The easiest way to open a workspace is using the File menu and selecting one of the available folder entries for opening. In this mode, some of VS Code's capabilities are reduced but you can still open text files and edit them. For example, when you open a new VS Code window by selecting a file from your platform's File menu, you will not be inside a workspace. Note: It is also possible to open VS Code without a workspace. Think of a workspace as the root of a project that has extra VS Code knowledge and capabilities. You may see the terms "folder" and "workspace" used interchangeably in VS Code documentation, issues, and community discussions. Selectively enable or disable extensions only for that workspace.Store and restore UI state associated with that workspace (for example, the files that are opened).Persist task and debugger launch configurations that are only valid in the context of that workspace.Configure settings that only apply to a specific folder or folders but not others.
The concept of a workspace enables VS Code to: In most cases, you will have a single folder opened as the workspace but, depending on your development workflow, you can include more than one folder, using an advanced configuration called Multi-root workspaces. Configure IntelliSense for cross-compilingĪ Visual Studio Code "workspace" is the collection of one or more folders that are opened in a VS Code window (instance).
0 kommentar(er)
