The Homepage of your DNN Portal Site needs a long time to display? DNN KeepAlive solves this problem and shows the Site immediately to you and your visitors.



There are other Solutions (e.g. modules, workarounds) outside available - but we have seen none having the simplicity and stability of our real Windows Service. It does it's task in the background and keeps your DNN Sides online. To keep connection/bandwidth costs small the Service should be (but must not) installed on the Webserver (IIS) running your DNN Portal Sites. But you can also use it from any Internet connected Windows Client /w .NET Framework 2.0 installed. So we give you the perfect solution, even if your Sites are hosted by an ISP.

Advantage:

no interactive Login necessary - just tell the Service which Sites you like to keep alive - that's all
minimal connection/bandwidth costs if installed on your DNN Webserver
no DNN Programming Skills needed - runs out of the box
no config files to edit, no file replacement or other complicated configuration needed
the service is comfortable controlled and configurations via the Windows SysTray
each DNN Portal can has it's own "Keep Alive Interval"
Background:

ASP.NET frees resources after some idle time of the Website (in fact that's true for nearly every ASP driven Site). So resources which are needed to show your DNN Portals Homepage have to be loaded on each visit - and that's the reason for the startup delay.

DNN KeepAlive requests your Portals at given Intervals an effectively prevents ASP.NET from thinking your Site is not visited ;-)

What you'll get:

You'll find in the package a common known Windows Installer (MSI) including the Service and the Service Controller - an a short documentation.

The documented Source Code (VB.NET) is also included. There are no 3rd Party Controls used - only .NET Framework 2.0 Features. So you can open the program in Visual Studio 2005 and start editing and adapting to your needs.

Like to read the Documentation? You'll find it here: Administration Guide

Some words about ASP Worker Threads:

Sometimes we read about setting the time the ASP Worker Thread recycles up to some hours. This could be a solution on poorly frequented sites because ASP really won't unload the Framework dll's - resulting in heavy memory load and poor performance of your overall system. In reality the performance optimation Microsoft included in IIS is a gift you should not throw away. So our tipp is to keep the default IIS settings and recycle the worker processes as soon as possible.

.NET Framework 2.0