re: How to Create Code Profiles in VSCode VIEW POST


What is the benefit of this approach over workspaces? This seems like manual work when a VSCode workspace can be saved with per-workspace settings, extensions, etc. You simply re-open the workspace and pick up where you left off.


Yes, that's true. But based on my understanding, aren't workspaces tied to your repository in the .vscode/ directory?

So the advantage to this approach is you can launch any project by using this command, without having to manually change the workspace settings.


You can use "Save Workspace As" and save it anywhere you would like. Then open the .code-workspace file to open it from anywhere.

Oh, now I see what you're saying. Save it somewhere and then with each project, you load the workspace. So it's never tied to a repository. Smart!

code of conduct - report abuse