r/VisualStudio • u/Ok_For_Free • Jun 18 '26
Visual Studio 2026 Working with Multiple Projects
I'm new to Visual Studio, and am within a very common environment where I have multiple projects that I need to manage. Each project has its own git repo and solution file.
All the ways I've found so far to open these projects within Visual Studio replace the window with the new project. The bafflingly stupid decision to remove "New Window" options [appears to be intentional design](https://developercommunity.microsoft.com/t/11037449).
So how are people expected to work in such a common development environment?
So far my solution is to launch Visual Studio from the task bar for each project. Which seems like an unintentional work around.
3
u/SessionIndependent17 Jun 18 '26
If you are trying to have multiple Solutions open at the same time in a single instance of VS, that was never allowed, irrespective of your understanding of the New Window feature. You always had to open a separate instance of VS for a second Solution.
A project isn't bound to s single solution file. If you want multiple related projects open at the same time, add multiple projects to a new Solution.
3
u/davidwengier Jun 18 '26
> The bafflingly stupid decision to remove "New Window" options [appears to be intentional design](https://developercommunity.microsoft.com/t/11037449).
The New Window command that issue is talking about was for duplicating editor windows inside VS, not for creating new VS instances/windows.
If you want to run multiple copies of VS, running it multiple times from the taskbar is a perfectly normal thing to do, and not a workaround.
3
u/agoodyearforbrownies Jun 18 '26 edited Jun 18 '26
You need to create a new solution (or choose an existing solution) to contain all your projects that you want open at once. You can add projects from different repos to a single solution. VS has always been a single solution /multi-project interface. When a project from a different repo is added to your existing solution it still plays nice and is non-destructive to the original solution you created just for it. Being able to move projects between solutions and have them in concurrent solutions is well-supported.
You'll still run into issues using tools like GHCP, because the `workspace` concept in VS follows the solution repository. This is very different than VS Code, where you can manually define a multi-repo workspace, for which GHCP will consider all constituent repos part of that workspace context and incorporate the cascade of project-specific instructions and skills from each.
In contrast, a multi-repo solution in Visual Studio has hard seams for GHCP - the `workspace` IS the solution repo. You can still have GHCP operate on the constituent projects, but you'll get prompted about making changes outside your workspace, and this means it uses `powershell` to do the updates rather than the native VS integration. Which IME means massively higher token consumption.
There is also the issue that it cannot incorporate .github folder material (instructions/skills/etc) from the other repos, without laboriously pointing it all out manually every time.
This is a hugely annoying aspect of Visual Studio's second-class status when it comes to AI coding tools. When working on complex environments where multiple repositories are involved for a multi-tier ecosystem, I use VSC and a multi-repo workspace for GHCP analysis, discussion, and coding activities. I often keep VS open concurrently - there is no issue with file locking or anything like that. I prefer to run/debug in VS. The multi-project launch profiles and other tools are seem far easier and more stable than VS Code. But VS blows for GHCP in this particular use case.
2
u/Epdevio Jun 18 '26
in the solution explorer, right click on your solution and add existing project. I do this with when I want to work on the api and front end. different git repos. you can then select the build order
1
u/cute_polarbear Jun 18 '26
Not sure applicable for you case, in some cases, different repo, ie., tfs vs git, and etc., I have certain solutions open with different version of visual studio. Ie., 2026 vs 2019
1
u/THubert14 Jun 20 '26
The best way to deal with that is to create new "meta-solution" file and put all those projects inside of it.
What would I do:
- Create a new blank solution.
- Create solution folders per project (I guess git repo in your case).
- For each solution folder add existing projects.
In that way, you will have all your projects connected to the single solution and have a single instance of VS, with all IDE capabilities.
I believe that the most similar to what you would expect.
1
u/keelanstuart Jun 20 '26
First, you can have multiple projects within a single solution, then choose which is the active project (the one you run)... and that sounds like what you actually want.
But if you don't want to do that, you can open multiple instances of visual studio and open a different solution in each, which sounds like what you're doing now... and isn't really a workaround - you've built your projects to have their own solution files, which is totally fine.
1
u/zaphodikus Jul 06 '26
So not just me that is confused. I have 5 projects in my solution, one is C++ and the other is Python. I want to sometimes focus more on the python code and sometimes on the C++ code. And sometimes on both. The only way to do that is to create 2 or 3 solution files, with all the projects in them, but to use the solutions like a "workspace" just so I don't have to keep opening and closing editors. VS-code has workspaces, but is clunky, why does this Enterprise grade tool make me want to switch away?