[Feature] Auto-enable extensions per session

[lonix1]

We develop apps in node, asp.net, and python. We have extensions for each platform, so my vscode has almost 50 extensions, and some conflict with each other.

Switching between projects is challenging, as I need to disable/enable various extensions.

It would be nice to have something similar to .vscode/extensions.json, but it enables specific extensions for that workspace. Let's call it .vscode/session.json for example.

So by default all the extensions would be installed, but not enabled. When I'd open a workspace with a .vscode/session.json, the extensions in that file would be automatically enabled, for that session only.

Maybe we could reuse .vscode/extensions.json like this:

"recommendations": [
  "ms-vscode.vscode-typescript-tslint-plugin",
  "dbaeumer.vscode-eslint",
  "msjsdiag.debugger-for-chrome"
],
"enableForSession": [
  "foo",
  "bar",
  "baz"
]

[ArulDhandapani]

I also recommend feature request, but ".code-workspace" workspace configurations in vscode would be best place for this.

[ArulDhandapani]

Also, I saw few other configurations conflict issues when multiple developers working in a project(By setup their own preference causing project quality). If we able to list out required plugins in a workspace configuration(.code-workspace) for auto-installation would be grateful. If it's implemented then each project controlled by it's own .code-workspace configurations file to install required plugins and it's configurations apply to it's project.

[lonix1]

@ArulDhandapani If you like the feature request, please upvote it. I think that's how the vscode team prioritizes new features. (Unless the team members personally want the feature as well.)

[whut]

Is it dupe of #61723?

[lonix1]

@whut This issue is simpler and to the point. That other issue is too complicated, and that's a guarantee it'll never be implemented. It needs to be automatic, without extra commands.

[sandy081]

Duplicate of #40239