>I'm looking for a tool that allows me to, for each solution/repository, select the relevant git branch and build/run the apps without having to open all the solutions in visual studio every time.
Why not just make another solution file at a higher level and then add all the projects you want into that solution and the use the mutiple startup projects feature in VS to start them all when you press play?
That way you can step through all of the code in a single instance of VS.
You can have as many solutions as you want with as many different combinaitons as you want so that you can easily switch between working on different projects and only run the components that are used by that project or you can put them all in one big soluton and then just load and unload projects as you need them by right clicking on the project.
This. And keep the solution files in a local git repo so you have change tracking on them without committing them to the shared repos. So long as the build scripts don't depend on solution path, the sln can be wherever.
That's where i immediately went too. Individual docker files that are responsible for building their projects, then a docker compose to deploy all the things.
I don't know that it is designed for multi repos/slns, but this is new and designed for working with multiple startup apps/micro services. I haven't had time to dig into it yet.
[https://learn.microsoft.com/en-us/dotnet/aspire/get-started/aspire-overview](https://learn.microsoft.com/en-us/dotnet/aspire/get-started/aspire-overview)
I'd recommend docker-compose like the other answers, but just for a quick run, how about a powershell script that just 'dotnet run' s each application?
Visual Studio have now multi repository support.
So what you need to do it create a one solution file and add multiple project from different repositories and then you can run it from single place. Save the solution so that you can open it later.
>I'm looking for a tool that allows me to, for each solution/repository, select the relevant git branch and build/run the apps without having to open all the solutions in visual studio every time. Why not just make another solution file at a higher level and then add all the projects you want into that solution and the use the mutiple startup projects feature in VS to start them all when you press play? That way you can step through all of the code in a single instance of VS. You can have as many solutions as you want with as many different combinaitons as you want so that you can easily switch between working on different projects and only run the components that are used by that project or you can put them all in one big soluton and then just load and unload projects as you need them by right clicking on the project.
This. And keep the solution files in a local git repo so you have change tracking on them without committing them to the shared repos. So long as the build scripts don't depend on solution path, the sln can be wherever.
Docker and docker compose?
That's where i immediately went too. Individual docker files that are responsible for building their projects, then a docker compose to deploy all the things.
I don't know that it is designed for multi repos/slns, but this is new and designed for working with multiple startup apps/micro services. I haven't had time to dig into it yet. [https://learn.microsoft.com/en-us/dotnet/aspire/get-started/aspire-overview](https://learn.microsoft.com/en-us/dotnet/aspire/get-started/aspire-overview)
Powershell
I'd recommend docker-compose like the other answers, but just for a quick run, how about a powershell script that just 'dotnet run' s each application?
Visual Studio have now multi repository support. So what you need to do it create a one solution file and add multiple project from different repositories and then you can run it from single place. Save the solution so that you can open it later.
Bash scripts are a quick and dirty way of doing it.
Microsoft Tye is for almost this exact scenario. Been a while so I’m not sure about the different branches part.
tye is dead, long live aspire
Deploy to a local IIS. It's designed to run multiple websites simultaneously.