You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
On Aspire 9 I have a problem that when I stop aspire, or stop my worker service in particular, the BackgroundService method StopAsync is never called. When I run my worker service directly and I hit stop I can see the log that StopAsync is called as expected.
I even tried writing a file to disk in StopAsync just to make sure I wasn't just missing the logs somehow, and it doesn't get written when stopping Aspire.
I first reported this on Aspires issues but was told this should be reported as an IDE bug since the IDE is responsible for this process. Issue
To Reproduce
Steps to reproduce the behavior:
Create worker project in Aspire solution
Create background service that overrides StopAsync
When stopping AppHost, StopAsync is never called for worker project
Expected behavior
Same behaviour as when worker project is run directly and is stopped by Rider
Additional context
Dotnet 9 and Aspire 9.
The text was updated successfully, but these errors were encountered:
Hi, thanks for a great plugin!
Describe the bug
On Aspire 9 I have a problem that when I stop aspire, or stop my worker service in particular, the BackgroundService method StopAsync is never called. When I run my worker service directly and I hit stop I can see the log that StopAsync is called as expected.
I even tried writing a file to disk in StopAsync just to make sure I wasn't just missing the logs somehow, and it doesn't get written when stopping Aspire.
I first reported this on Aspires issues but was told this should be reported as an IDE bug since the IDE is responsible for this process. Issue
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Same behaviour as when worker project is run directly and is stopped by Rider
Additional context
Dotnet 9 and Aspire 9.
The text was updated successfully, but these errors were encountered: