c# - .Net Web Application app startup workflow for IIS -

okay, let's have web application absolutely has perform kind of startup , has remain running indefinitely regardless of communication receives clients (as it's push based system)

now testing have been hosting windows service, great because allows me have hard entry point application can bootstrapping , service , running

next, i'm trying move iis world instead can face service outside world...and i've hit snag...i don't have hard entry point can bootstrap application except global.asax, understand invoked when clients make call server

is there better area can put entrance application , bootstrapped without waiting client connect it? , area called once or going called periodically application falls out of scope (so speak)? said, app has remain running @ times

is there better area can put entrance application , bootstrapped without waiting client connect it?

yes, there is. can warm iis.

and area called once or going called periodically application falls out of scope (so speak)?

it depends method in global.asax use. application_start runs once per app start.

like said, app has remain running @ times

beware, dragons here. depends how critical is. if need utter reliability, must use load balancer , have @ least 1 other duplicate service. other things consider, app pool needs recycled time time. iis, os, application have bugs, updates needs installed, network device fails, power outages happen , on.