The reason is because to run a keep-alive service within the same application process is contradictory to the way the ASP.Net framework is architected.

Let me know if you want the technical details, but the bottom line is that an asp.net application that tries to keep itself alive is like a person performing surgery on himself.

Your best solution is to use a third-party monitor in the case of the former, or a doctor in the case of the later.

Be aware though, that if you are on a shared host then there are other villians that are fighting for the memory your application is using and the one in control of the server has a lot of power to reclaim it.

BTW, I have my own dedicated servers, but I use an outside service to monitor the apps because it's also nice to know if the application has stopped responding to the outside world.

So basically, ASP.NET was just born to lag.  I thought it was supposed to be "precompiled" and whatnot, so much faster than PHP.  I don't understand.  My company's site doesn't have many visitors, and it will never get any because people don't get past the initial lag.  Sure, it's fine when it's up and running but who will wait that long.

I don't understand why Microsoft even made a platform like this.  You'd think with today's server technology the stuff would load up really fast.  But I hear that even running one DNN site on a high end dedicated server doesn't get rid of this lag.  I'm done with ASP.NET.