You can customize the settings and preferences of a workspace.

In case it isnt painfully obvious, I am (very) new to Visual Studio Code.

I figured a workspace is merely the project directory, as the OP suggests.

However, if I choose File -- Open Workspace, the file explorer dialog box does not allow me to simply open a folder, I have to find a specific file.:(.

Im 2 weeks into VS and Im absolutely loving it, but still havent wrapped my head around what exactly Workspaces are and I think its telling that quite a few people seem to have this question.

Ive made a workspace with VS Code but dont see any difference except a different file icon.

I know workspaces are local copies of different branches but couldnt a standard folder for the separate changes do the same thing Id like documentation on this as it is very hard to find.

Its a bit strange that I can open and save an existing workspace, but not close it to start with an empty one.

Sometimes it refers to a workspace as described above, and other times it refers to a workspace as a project that is specifically associated with a.code-workspace file.

But then projects with a.code-workspace file are given a Workspace suffix, contradicting the heading and indicating that only those files are actually workspaces.

With a multi-root workspace, you have a single.code-workspace file that opens all of the root folders you want to be displayed in the explorer (that is, you dont need to keep opening multiple folders manually).

And all of the Visual Studio Code settingsconfigurations that you want to be applied to that workspace are restored every time you open that workspace file.

When you open a folder in Visual Studio Code and start making modifications to the editor that are specifically related to the project youre currently working on, Visual Studio Code automatically creates a.vscode folder and stores it in the root of the project folder that youre working on.

This.vscode folder has files that store the changes you made.

For example, if you change Visual Studio Code settings that you want to apply only to your current project, Visual Studio Code creates a settings.json file with those updates, and that file is stored in the.vscode folder.

Youd then be able to either open the project folder directly, or open the workspace file.

But I cant think of any reason why this would be beneficial.

Instead, it will read that file and open the folders that belong to that workspace.

Not long after that, I think that the definition of WS actually changed, so it has been something of a zombie question.

I have to confess that it has been kind of nice watching the points roll in, and I havent felt very motivated to follow the discussion.

I feel like it would be very unkind not to accept this answer.

Thanks.

This let me cleared a bit things in myself after I realized an issue I had about choosing right Python interpreter( stackoverflow.comquestions54106071 ), but now I have vs code complaining saying that in launch.json the args proprety is not allowed,those file was produced automatically, and I cant find a syllabus for that object.

I was having having a lot of trouble to actually understanding the functionality of the workspace.

If you want to do either of those things, use a workspace, otherwise, just open a folder.

Vs Code For Mac