The following seems to work when copied into each .vscode of each workspace. The previous solution with having a workspace setting in user settings is obsolete (there is no migration). This is a work around though and not a solution. See #396 (comment) for more details on our approach.. Each Cloud Function has its own virtualenv because each has its own Python dependencies. There is no need for these folders to share parent folders; indeed that is the point since VSCode normally uses a single folder in the Explorer side-bar. But for now, it would be disabled for multi-root workspaces. You might have figured – I’m a VSCode fanboy. Windows @isidorn; Linux @weinand; macOS @chrisdias; In this milestone we rewrote how multi root workspaces surface in VS Code. This provides a variety of advantages and use cases, such as working on multiple projects at the same time -- say a project's documentation and its source code repositories -- and keeping everything in sync. I think multi-root-workspaces need some more work. You might remember the session I did on NAVTechDays 2017 (Rock ‘n Roll with VSCode), where I dove quite a bit into the possibilities this great tool comes with.But I didn’t talk about the concept of “Multi-root Workspaces”: an ability of VSCode for you to work on multiple “projects” at the same time, in one environment. Complexity: 5. A multi-root workspace is a set of folders (the "roots") that are opened collectively in an instance of VSCode. Multi-root workspaces let developers group a set of disparate project folders into one workspace, instead of having to work with files and folders residing only in a single root folder.

The first use to consider is in what is calls a multi-root workspace. Without the root folder name, the variable is scoped to the same folder where it is used. So – I always have a second VSCode open with my PS Scripts. Do notice though that I’m not making my scripts part of the multi root workspace. Test for: Multi Root Workspaces. I am working on a project that requires multiple Google Cloud Functions. By appending the root folder's name to a variable (separated by a colon), it is possible to reach into sibling root folders of a workspace. One of many. That just doesn’t work – the Al Language Extension does “something” with the F5 key that kind of like disables the ability to run any PowerShell script that’s part of the same Multi Root environment (F8 does work – but I need F5 ;-)).