Windows Service or Scheduled Task, which one do we prefer?

Question

If we need to write a program that works periodically, which way do we prefer? Writing a windows service or writing a console application which works as scheduled task?

Answer 1

I would suggest running the process as a scheduled task if you can, and writing a service only if you need to. Services are quite a bit more difficult to write (correctly), and if you're running your process on a schedule of any sort, you're much better off using the windows scheduler than attempting to build a scheduler of your own (within the servce).

• The windows task scheduler is more efficient than your home-made scheduler will be
• The windows task scheduler offers a number of options that you almost certainly won't attempt to replicate, but may find useful later on
• If you build a service, you'd have to recompile the program if you want to change the logic that determines what conditions to run the task under. If you use the scheduler, you just flip some options and are done with it.

If you're trying to decide between the two, then obviously using the Task Scheduler is a viable option. And if using the Task Scheduler is a viable option, then building a service is almost certainly the wrong choice.

Answer 2

Depends on just how regular you need it to run.

If its something that needs to run every 60 seconds all day, I'd go with a Windows Service.

If its something that only needs to run once a day, I'd go with Scheduled Task

Anything in the middle... use your judgement :)