-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Update dotnet watch to support running .NET Aspire AppHost projects #36971
Comments
@vijayrkn do you know who owns this , and next action here -- is it your team? |
for my own future reference, per offline discussion @tmat owns this area and is looking at it. |
@tmat could you give an update -- is it possible to set expectations? I hear this is significant work, to handle the DCP protocol etc. |
So, using the Aspire Sample with the Blazor App, there is no way around restarting the whole thing to see some html change? |
linking dotnet/aspire#1008 |
Noting here that work is actively in progress |
@tmat did this work get completed in the SDK? I'm wondering whether we should re-validate the scenarios in dotnet/aspire#633 and dotnet/aspire#1008 for Aspire P5. |
Any updates to share on this one? It's been 4/5 months since the last comment @danmoseley 😄 |
It's now been more than 8 months since the last comment @danmoseley. Any updates? dotnet/aspire#1008 (comment) seems to imply it's coming in an upcoming .Net 9 update; is this true, or is that just a subset of the issue? |
In order to properly watch .NET Aspire AppHost projects,
dotnet watch
needs to implement the IDE execution spec. This ensures that the AppHost process can coordinate withdotnet watch
to manage the lifecycle of projects composed into the AppHost as resources.The text was updated successfully, but these errors were encountered: