Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add multi solutions support #6966

Open
1 task done
fabrice-bauer opened this issue Dec 18, 2024 · 5 comments
Open
1 task done

Add multi solutions support #6966

fabrice-bauer opened this issue Dec 18, 2024 · 5 comments
Labels
area-app-model Issues pertaining to the APIs in Aspire.Hosting, e.g. DistributedApplication untriaged New issue has not been triaged
Milestone

Comments

@fabrice-bauer
Copy link

Is there an existing issue for this?

  • I have searched the existing issues

Is your feature request related to a problem? Please describe the problem.

Hello,

I am trying to use Aspire using 4 existing solutions. Each of these solutions contain between 10+ and 60+ projects.

I managed to create an Aspire host project referencing the 4 "main" projects of each solution and this works very well.
However when using the Aspire solution not all projects are there and therefore it is not possible to easily navigate code or rebuild everything.
I could manually add all existing projects into the Aspire solution but with the high number of projects this would be quite long plus it would require maintenance when we add new projects in the existing 4 solutions.

Describe the solution you'd like

I am not fully sure if this should be managed by Aspire or Visual Studio but in this scenario being able to reference solutions from a solution could greatly help.

Thanks very much.

Additional context

No response

@FAYSALAHAMMAD2004
Copy link

Hi there

@joperezr joperezr added untriaged New issue has not been triaged area-app-model Issues pertaining to the APIs in Aspire.Hosting, e.g. DistributedApplication labels Dec 18, 2024
@joperezr
Copy link
Member

Hello @fabrice-bauer, thanks for your submission. Out of curiosity, is there a reason why you can't just have everything in a single solution? What people do in similar situations, is to have a single .sln file that has all of the projects, and then have multiple solution filter files .slnf which can enable people that just want to open a subset of projects to be able to do so. You can find more information on solution filters here, but the TL;DR is that they are very small files that just point to a solution, and apply some filters to it so that when you open that file (The .slnf file) with Visual Studio, it looks like if it were a different solution as it only has a subset of projects.

Doing this would allow you to continue working on a subset of projects when needed, but also allow you to fully orchestrate the projects with Aspire when you need to run everything, rebuild and debug.

@joperezr joperezr added this to the Backlog milestone Dec 18, 2024
@fabrice-bauer
Copy link
Author

Hello @joperezr, in fact I forgot to mention an important aspect which is that each solution and corresponding set of projects are in 4 separate repos.
But thinking about it again, this is probably not an Aspire related improvement but rather a Visual Studio one.
I will also have a look at the new slnx format which might make it much easier to "replicate" the existing solutions content into the new one.
Thanks very much.

@Mrxx99
Copy link
Contributor

Mrxx99 commented Dec 19, 2024

@fabrice-bauer
Copy link
Author

Thanks @Mrxx99 I had not seen it, it can be very interesting, too, but it addresses the multi repo part.
For the solution with all projects of all existing solutions to be able to rebuild and debug the whole distributed app from the single Aspire Host, it seems the new slnx format makes it much easier to maintain a new dedicated solution, so I will try it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-app-model Issues pertaining to the APIs in Aspire.Hosting, e.g. DistributedApplication untriaged New issue has not been triaged
Projects
None yet
Development

No branches or pull requests

4 participants