We have tasks running under a web site which should automatically start after a IIS recycle. We also have other init code that should be run immediately after a recycle.

I have looked at Application Initialization: http://www.iis.net/learn/get-started/whats-new-in-iis-8/iis-80-application-initialization#TOC301259894

And from this article it seems that setting AlwaysRunning and PreloadEnabled settings in applicationHost.config is enough to make IIS make a request to your site which will execute the init code in applicationStart.

This seems like enough to me, but then I read other articles where they implement IProcessHostPreloadClient in the web application and let this run the init code.

What is the difference between implementing IProcessHostPreloadClient and only setting those two properties in applicationHost.config?

Related posts

Recent Viewed