IIS 7.5 introduces the concept of autorun providers that allow you to get a WAS to automatically download an application or assemblies when you start an application pool.
Is it possible to achieve a similar result with IIS7?
Basically, we have an application that runs under WAS and has a cache in memory. When the application pool recycles, my deployed WAS application will not actually be activated until the first hit is received. This means that the cache is cold upon receiving the first hit. It would be nice to be able to pre-launch the application as soon as the application pool is redesigned.
Other options we reviewed:
Deploying the application as a Windows service so that it does not re-encode (this would work, but IIS / WAS application lifecycle management is a useful thing besides this problem).
Writing a separate service whose task is to ping an application to warm it up.
However, the best way is to get IIS7 / WAS to do this for us.
source
share