Solution build in Visual Studio stops AppHost instead of restarting it
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 6.3k
- Forks
- 991
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 201
Description
### Is there an existing issue for this?
- [x] I have searched the existing issues
### Describe the bug
I usually run Aspire projects from Visual Studio without attaching the debugger (using Ctrl-F5).
When I run the build using Ctrl-Shift-B (or when Copilot Agent Mode runs the build to see the compile errors), the AppHost stops.
### Expected Behavior
I think it should start again after the build is finished. It is annoying to always run the app again, especially when Copilot triggers the build multiple times.
### Steps To Reproduce
Open any .NET Aspire project from Visual Studio.
Run AppHost using Ctrl-F5.
Build the solution (Ctrl-Shift-B).
AppHost will stop and will not be restarted.
### Exceptions (if any)
_No response_
### .NET Version info
9 and 10
### Anything else?
_No response_
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the behavior in a .NET Aspire project opened in Visual Studio: run the AppHost with Ctrl-F5, then build the solution with Ctrl-Shift-B. Start by tracing the Visual Studio build and AppHost lifecycle behavior; done means the AppHost remains running or starts again after the build finishes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- devtools
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100