vscode open workspace file vs open folder.

vscode open workspace file vs open folder.

mpieper
Contributor Contributor
327 Views
0 Replies
Message 1 of 1

vscode open workspace file vs open folder.

mpieper
Contributor
Contributor

I'm building toolsets that I'd like to share between scripts.  It's a very large boon to have a shared folder included in my vscode workspace to easily edit and view source e.g. right now the folder opened looks like:

ScriptFolder

>__pycache__

>.vscode

  {} launch.json

  {} settings.json

*.env

{}ScriptWorkspace-workspace

--Script.manifest

Script.py

 

 whereas I'd like it to open the workspace e.g.

ScriptFolder

>__pycache__

>.vscode

  {} launch.json

  {} settings.json

*.env

{}ScriptWorkspace-workspace

--Script.manifest

Script.py

vSECOND_WORKSPACE_FOLDER

>__pycache__

*.env

*OtherScripts0.py

*OtherScripts1.py

etc.

 

I've saved the workspace in vscode, but whenever opening via the debug or edit button in fusion360's "scripts and addins" toolbar, the workspace is not loaded, but rather the folder is opened up.  Is there any way to have fusion load the workspace file instead?  Maybe a bootstrap call in the settings folder to load the workspace in the same folder of the same name?

 

Thanks.

 

0 Likes
328 Views
0 Replies
Replies (0)