Some additional notes that we probably won’t get to, but I’ll include here just in case.

Workspace File Structure and Persistence

Multi-root workspaces are defined by a .code-workspace file, which not only lists the folders included in the workspace but also allows you to store workspace-specific settings and configurations. This file can be saved, version controlled, and shared with your team, ensuring that everyone uses a consistent development environment. For example:

{
  "folders": [
    {
      "path": "frontend"
    },
    {
      "path": "backend"
    }
  ],
  "settings": {
    "editor.tabSize": 2,
    "files.exclude": {
      "**/node_modules": true
    }
  }
}

Advanced Workspace Management

Visual Studio Code provides commands to manage workspace folders dynamically. Use the Command Palette to run “Workspaces: Add Folder to Workspace” or “Workspaces: Remove Folder from Workspace” to quickly adjust your workspace. You can also reorder folders by dragging them in the Explorer, allowing you to prioritize certain projects.

Version Control Across Multiple Folders

Each folder in a multi-root workspace can have its own version control settings, enabling you to work with separate Git repositories simultaneously. This means you can stage, commit, and push changes independently for each project while still benefiting from a unified interface. Additionally, workspace-level settings can help standardize linting and formatting rules across all projects.

Integrated Task and Debugging Configurations

Multi-root workspaces allow you to define tasks and debugging configurations that span multiple folders. In your .code-workspace file, you can specify tasks that run commands in a particular folder or even trigger compound tasks across different projects. Similarly, workspace-level launch configurations can help you debug interactions between services, such as a front-end application connecting to a back-end API.