Is Windows Service an ideal replacement for VB 6 exe as a scheduled task?

There is an existing VB 6 exe that is defined as a scheduled task (runs every 20 minutes) on a Windows server. Now the client wants to replace it with a .NET component. Is creating a Windows service (with a built-in timer) the perfect solution?

+4
source share
1 answer

If you do not need to keep state information between calls, I would simply leave it simple and leave it as a planned task. This gives you free planning and basic logging.

I have about 20 .Net applications working as scheduled tasks like this.

+5
source

All Articles