Windows Service or Schedule Task

Thanks for the info Karthik. I am looking for that automation process which will trigger another process to download files through given FTP server and a given point of time. There could be several FTP servers which has to accessed only at a given time relevant to that FTP server. In Task Scheduler, the minimum interval between the repeating a task is 5 mins, whereas there could be some FTP servers which would be required to access within that 5 mins of interval. So the "Task Scheduler", will always run the process atleast few mins delayed than the expected time of execution of my required task.

Thinking out of the box, rather than depending on Task Scheduler, can we develop an windows application, that can run at the background, hiding itself in the task bar just like another application which run hiding and showing only it icon at the right side of task bar beside time / date (like instant messengers, antivirus, etc.,) ? If yes can you please advise me how can it be done ??

Hi Mohandas,

I got the same requirement as mentioned above and asked to develop a Windows service. Please let me know, if you got the solution for your question.

Thanks for your time and help.

-Sri

Spot on. I have written stuff that works exactly this way in the past, and I highly recommend it for unattended batch processing, with a couple of things to be aware of first.

1) Scheduled Tasks (in more recent versions of Windows, it's called Task Manager, and it's under Administrative Tools) will not run more often than every 5 minutes. You set it up to trigger the actions daily at a set time, repeating every 5 minutes thereafter. From what I can tell, you cannot run your task trigger more often than this. If you need to run it with more than a 5 minute granularity, you'll have to use a Windows Service and a threading timer.

2) Building a new command line app for every task you want to trigger is a difficult-to-maintain mess. So you're going to have some overhead with a general-purpose task engine. The ones I've written are specific enough to require an input, archive, and error directory path (or hostname, paths, and credentials for FTP) for each sub-task. The engine checks the database to see which sub-tasks need to run right now, and it kicks them off. The sub-tasks themselves are smart enough to go get their files from the input location and process them, then move them to the archive or error locations (pass/fail style, and we keep a complete history).

So there's a table in the database that tells it when to run, where to get data, where to put data, and what classname to instantiate to process the data. There's a command-line app that gets that config for the currently needed processes, instantiates each active process' class, and runs it. And there's a timer that kicks off the command-line app every 5 minutes.

It works well and it's dirt simple. Let the OS handle the timing stuff. Don't invent your own if you don't have to.