The order of starting/stopping IHostedServices in generic host

[jakubfijalkowski]

Hi!

I've stumbled on a small problem - the order in which IHostedServices are stopped is the same as they are started. This was not always the case. The WebHost (now removed) used reverse order. Why does the generic host doesn't reverse the services when stopping? It seems to me that stopping services in reverse order than starting them is a more "natural" way of working.

The reversed order might make more sense if you have two IHostedServices depending on each other. I am aware that dependencies here might not be the best design choice but hear me out :) In my case this is mostly related to integration tests, where I bootstrap the database and then drop it in the very first service. Other services (e.g. some subscriptions or periodic tasks) might rely on the database being available the whole time they work. If the services are stopped in the same order as they are started, I get nasty exceptions (that don't fail the test but are cluttering the output) during the time between dropping the database and stopping the dependent service.

I wasn't able to find any reasoning why the order is the way it is, so - why is that? Is this "by design"? If so, what would you suggest as a workaround (I'm currently experimenting with custom ordering but I'm not quite sure whether this is a viable option)? Or am I just missing something?

[jakubfijalkowski]

Okay, so I finally got to the correct place. During the initial investigation overlooked the correct implementation which is... in the generic host. :) I was searching through the now-deprecated Microsoft.AspNetCore.Hosting.Host believing that it is the go-to implementation.

Using the correct host completely solves my problem. :)