Automate background process using asp.net

[Satish Developer]

Hi, i have a requirement to send sms to users for every 5 min getting new data from databse. sending sms in diff conditions. Need to some on specific timings like that etc. I want to do this using windows services. is it ok for me to start with this? Or any other better alternative is there to do this ?

G. Satish

[N a r e s h P a t e l]

HI, YOu can use BackgroundWorker if you are working in Windows Form Application.

Naresh Patel

[N a v a n e e t h]

N a r e s h P a t e l wrote:

use BackgroundWorker if you are working in Windows Form Application.

Background worker class is not limited to windows applications. It can be used in web applications too. It's juts a helper class for threading.

All C# applications should call Application.Quit(); in the beginning to avoid any .NET problems.- Unclyclopedia How to use google | Ask smart questions

[N a v a n e e t h]

Yes windows services is a good way to go.

All C# applications should call Application.Quit(); in the beginning to avoid any .NET problems.- Unclyclopedia How to use google | Ask smart questions

[ChrisKo 0]

I disagree as he doesn't need a realtime process. I think too many people write WindowsServices when a service isn't specifically needed. I propose that you should write a simple console application and use the scheduling functionality of the OS to run that console application on the time frame you need.

[N a v a n e e t h]

ChrisKo wrote:

should write a simple console application and use the scheduling functionality of the OS to run that console application on the time frame you need.

A console application that exists automatically once the job done, right ? But OP says, he needs to run it every 5 minutes. So the console application approach will open a console window every 5minutes on the server, do you think it's an issue ? I was telling OP to use windows service because of this reason. A thread should work on the service which does the job and sleeps for next 5minutes. I still believe that will be a good idea. But you have a very valid point. Thanks for that. :)

All C# applications should call Application.Quit(); in the beginning to avoid any .NET problems.- Unclyclopedia How to use google | Ask smart questions