The basic flow of the article:
- Create a Web Service that will be called to run the jobs
- Create a Windows Service that will call the web service at specified intervals. Create installation package.
- Create classes that inherit from a Job class for each job that will need to be run
- Set up interface with database to store job timing, populate the job classes when needed
- Hook up the jobs to the web service
It does seem to be a little bit more complicated than is needed (the core of it all is the Web Service and Windows Service). However, it does give a very scalable solution for scheduling jobs in ASP.net – once the initial setup is defined, adding jobs will be pretty simple and it should work pretty well.