BackgroundService exceptions now propagate in .NET 11
Here's a bug that lived in .NET for over four years. If your BackgroundService threw an exception after its first await, your host would catch it, log a critical message, and then exit cleanly with exit code 0.
So everyone would think it terminated successfully. That got fixed!







