2025-11-27 12:46 PM
Hi, I'm trying to come up to speed with the VSCode workflow, coming from experience so far only using CubeIDE.
In CubeIDE, it seems that I was encouraged to think of having a "workspace", in which several projects co-existed. I enjoyed the ability to be able to have multiple projects "open" at once, to be able to compare code and easily understand/navigate to out-of-project source code, like centralized libraries and such.
The VScode workflow, in contrast, seems to want me to only open a single project at once, otherwise CMake seems to get crabby. This is slightly annoying in that it requires me to open multiple windows in order to see multiple projects simultaneously, but notably more annoying when I am trying to use out-of-project code - I need to open a second window at a higher directory level, but can't actually build anything in this second window. It's kind of cluttered and confusing.
It also seems to kind of push me away from the path of having a git repo that spans multiple projects - if I'm trying to develop something that conceptually should all belong in one repo but contains multiple projects, I can't easily work from the top level of my repo as I'd expect to be able to do.
Am I missing something obvious in this workflow? I keep trying to find a "set active folder" function or something like that, but there doesn't seem to be one...
Thanks!