My hosted ASP.NET MVC app takes long time (10-20 secs) when it launches. And after ASP.NET worker process is running, everything is normal. Problem is that the worker process is getting killed when the web site is inactive (i.e., no user). This will give the next user very long wait time to load the web site.
I know there is commercial or free services on the web that makes your web worker process alive. But I need to do that myself with simple timer windows service. No problem there. But my question is what is effective way to makes it alive? Would a simple ping do it or is downloading from the web site necessary?
I’d recommend you set up an empty aspx page on the site and see if requesting it occasionally will fulfill your requirement. You should only have to make a request to keep the worker alive.