.Net schedulers?
-
I'm looking into using Quartz.net[^] but I haven't seen a good UI so that the user can schedule their own jobs. Just curious what other people have used. Have you exposed scheduling to end users? If so how detailed was it, meaning could the user choose which days of the week, or perhaps every 3rd Tuesday, etc.
There are only 10 types of people in the world, those who understand binary and those who don't.
-
I'm looking into using Quartz.net[^] but I haven't seen a good UI so that the user can schedule their own jobs. Just curious what other people have used. Have you exposed scheduling to end users? If so how detailed was it, meaning could the user choose which days of the week, or perhaps every 3rd Tuesday, etc.
There are only 10 types of people in the world, those who understand binary and those who don't.
Using console app + built in Windows Scheduler. Does the job.
-
I'm looking into using Quartz.net[^] but I haven't seen a good UI so that the user can schedule their own jobs. Just curious what other people have used. Have you exposed scheduling to end users? If so how detailed was it, meaning could the user choose which days of the week, or perhaps every 3rd Tuesday, etc.
There are only 10 types of people in the world, those who understand binary and those who don't.
I used to think that I wanted a job scheduler to do things, but I thought all the .NET ones were over-complicated. So, I spent a couple hours or so and wrote one in to my app. Just have a timer that checks your configured jobs every interval (maybe a minute or less) if it's time to run one, then run it. There's a few other complexities to deal with, but it's not as hard as you think. Think about the configuration for Unix chron as the simplest way do it with lots of timing options.
-
I used to think that I wanted a job scheduler to do things, but I thought all the .NET ones were over-complicated. So, I spent a couple hours or so and wrote one in to my app. Just have a timer that checks your configured jobs every interval (maybe a minute or less) if it's time to run one, then run it. There's a few other complexities to deal with, but it's not as hard as you think. Think about the configuration for Unix chron as the simplest way do it with lots of timing options.
Timv256 wrote:
but it's not as hard as you think.
The complexity comes in play when you allow users the freedom to schedule their own jobs. For example, do you support the option for just every weekday or do you let them choose which days of the week. Do you allow start and stop time to be different on each of those days, etc. It can get out of hand very quickly depending on how flexible you want it.
There are only 10 types of people in the world, those who understand binary and those who don't.
-
Timv256 wrote:
but it's not as hard as you think.
The complexity comes in play when you allow users the freedom to schedule their own jobs. For example, do you support the option for just every weekday or do you let them choose which days of the week. Do you allow start and stop time to be different on each of those days, etc. It can get out of hand very quickly depending on how flexible you want it.
There are only 10 types of people in the world, those who understand binary and those who don't.
Even with lots of timing options, it wasn't that hard. I had a schedule record and just went through each schedule and executed jobs associated with the schedule during an interval when a schedule was triggered. Name StartTime EndTime RepeatIntervalMinutes DaysOfWeek DaysOfMonth Hours Minutes NextRunTime LastRunTime friday7 2014-09-05 00:00:00 2020-04-18 00:00:00 90 Friday NULL 7 NULL NULL 2015-03-13 07:00:49.9115390 -05:00
-
Even with lots of timing options, it wasn't that hard. I had a schedule record and just went through each schedule and executed jobs associated with the schedule during an interval when a schedule was triggered. Name StartTime EndTime RepeatIntervalMinutes DaysOfWeek DaysOfMonth Hours Minutes NextRunTime LastRunTime friday7 2014-09-05 00:00:00 2020-04-18 00:00:00 90 Friday NULL 7 NULL NULL 2015-03-13 07:00:49.9115390 -05:00