Use VS Code Workspaces for Multi-Folder Projects
A project spread across an app, API and documentation folder becomes awkward to search and launch. This guide gives you a small, testable way to approach the issue before changing a live system.
A practical workflow
- Add the related folders to one workspace and save the workspace file with team-safe settings.
- Define tasks for repeatable build commands and review workspace extension recommendations.
What to check
Avoid committing machine-specific absolute paths or credentials in shared workspace settings. Compare the result with the original problem and record what changed. If a measurement or test does not support the change, revisit the assumption rather than adding more complexity.
Keep the experiment small enough to reverse. Document the starting state, the change and the result so another person can repeat the process. Product menus and versions can change, so check the current documentation for your environment.
Official reference: Read the documentation.