26 Kicks

Using a Windows Service just to run a scheduled process is Wrong!(weblogs.asp.net)

submitted by HoolieManHoolieMan(1715) 4 years ago

A classic post by Jon Galloway: A Windows Service is the wrong solution to scheduling one-off custom processes. The right solution for scheduling simple processes is the Windows Task Scheduler.

1 comment |category: |Views: 113

tags: another

new Add a live kick counter to your blog >> liveImage

You can even customize the image by choosing your own colors, and then clicking the button below to update the preview and the html code:

  • "Kick It" text
  • "Kick It" background
  • kick count text
  • kick count background
  • border

Simply copy and paste this HTML into your blog post.


Users who kicked this story:
chrismo111chrismo111(47) - dovedove(735) - bahadornbahadorn(340) - mjpaladmjpalad(615)
More who kicked this story...
Comments:

posted by xlar54xlar54(0) 4 years ago 0

Where I work, we implemented exactly this kind of solution using a Windows service for scheduling. It did / does work, but in hindsight, I would have to agree with the author. Its a bit too "low-level" for all it does. Granted, I dont like task scheduler, but it IS made for these kinds of scenarios. And the other thing to think about is maintenance. Putting stuff like this in as a Windows service takes it out of the proper context for troubleshooting. Folks who do the support of a system may (rightfully so) think that the buggy scheduled process is running via task scheduler, when its actually tucked away on a machine as a service. It just makes sense to put it where Microsoft recommends.

Reply

information Login or create an account to comment on this story
Submit a Story
View upcoming stories
How else can I help?
Add our feeds to your site

Most Active Users

What's this?