Does Cache activity prevent IIS from unloading an ASP.NET app?
<p>I want to add a scheduled task to a client's ASP.NET app. These posts cover the idea well:</p>

<ul>
<li><a href="http://blog.stackoverflow.com/2008/07/easy-background-tasks-in-aspnet/" rel="nofollow">http://blog.stackoverflow.com/2008/07/easy-background-tasks-in-aspnet/</a></li>
<li><a href="http://stackoverflow.com/questions/45841/what-is-the-best-practice-to-kick-off-maintenance-process-on-aspnet">http://stackoverflow.com/questions/45841/what-is-the-best-practice-to-kick-off-maintenance-process-on-aspnet</a></li>
<li><a href="http://stackoverflow.com/questions/42822/out-of-band-processing-techiniques-for-aspnet-applications">http://stackoverflow.com/questions/42822/out-of-band-processing-techiniques-for-aspnet-applications</a></li>
</ul>

<p>My question has two parts: First, will IIS unload the application if there isn't enough request activity despite the Cache activity? My client doesn't enjoy as much traffic as stackoverflow so they can't rely on user requests to keep the app 'active'. Obviously, I can't schedule tasks in an unloaded app.</p>

<p>Second, if so, is there a way to prevent IIS from unloading the app outside of configuration or external 'stay-alive' requests? My client's host doesn't allow much configuration tweaking and a stay-alive utility introduces the deployment complexity I'm trying to avoid with an ASP.NET Cache solution.</p>

<p>Thanks a bunch.</p>

<p>Edit/Conclusion: TheXenocide's solution is exactly correct given the question. However, I've decided it is a really bad question. The temptation to cut corners is always looming. I've regained my senses and told my client to use a website monitoring tool to keep the site active. In addition, the scheduled task is going in a windows service despite the extra deployment hassle.</p>
