Quartz.NET vs. Windows Task Scheduler 2.0
2,941 views
Skip to first unread message
zambak
Jan 18, 2011, 10:23:54 AM1/18/11
to Quartz.NET
Hi
I don't want to start any "holly wars" here - what I am interested is
if anyone can share (objectivelly hopefully ;) what are the
differences/advantages/disadvantages/use cases between Quartz.NET and
the new Windows Task Scheduler 2.0. For Windows Task Scheduler there
is a C# wrapper API (http://taskscheduler.codeplex.com/) that can be
used...
Regards
Z...
I don't want to start any "holly wars" here - what I am interested is
if anyone can share (objectivelly hopefully ;) what are the
differences/advantages/disadvantages/use cases between Quartz.NET and
the new Windows Task Scheduler 2.0. For Windows Task Scheduler there
is a C# wrapper API (http://taskscheduler.codeplex.com/) that can be
used...
Regards
Z...
Lloyd Cotten
Jan 20, 2011, 1:39:45 PM1/20/11
to quar...@googlegroups.com
I'm very interested in what thoughts people have on this as well. Even if it's statements of the obvious, it would be a helpful reference for people new to quartz or any type of enterprise and/or embedded schedulers.
Cheers,
Lloyd
Cheers,
Lloyd
--
You received this message because you are subscribed to the Google Groups "Quartz.NET" group.
To post to this group, send email to quar...@googlegroups.com.
To unsubscribe from this group, send email to quartznet+...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/quartznet?hl=en.
Robert Fuchs
Jan 20, 2011, 3:21:52 PM1/20/11
to quar...@googlegroups.com
I think the obvious difference (and please anyone correct me if I'm wrong)
is that with the Windows Task Scheduler C# wrapper API you can only run
"executable" tasks, like exe, com, cmd, bat, vbs, ps...
You can't run method x from class y, unless you implement this via command
line arguments (eg. like rundll.exe does).
So the scheduler acts external from your app, while with Quartz the
scheduler can be part of your app.
is that with the Windows Task Scheduler C# wrapper API you can only run
"executable" tasks, like exe, com, cmd, bat, vbs, ps...
You can't run method x from class y, unless you implement this via command
line arguments (eg. like rundll.exe does).
So the scheduler acts external from your app, while with Quartz the
scheduler can be part of your app.
Regards, Robert
Stephen Tunney
Jan 20, 2011, 3:56:01 PM1/20/11
to quar...@googlegroups.com
Does windows task scheduler cluster across multiple machines?
Regards, Robert
RambleCampbell
Jan 20, 2011, 10:50:09 PM1/20/11
to Quartz.NET
I'm quite new to Quartz.NET myself, and also investigated Windows Task
Scheduler when I began working on a scheduling app, and ultimately
decided that Quartz.NET was WAY better. Along with the important point
that Robert made above (which I'm pretty sure is correct), managing
Windows Task Scheduler remotely is far inferior to Quartz.NET. To
manage Task Scheduler, you either have to remote into that machine, or
else write a web service to be hosted on that machine that can
communicate with the Scheduler via the C# wrapper you mentioned. With
Quartz.NET, if you use a database jobstore, your GUI for managing jobs
and the Quartz.NET service itself only have to be pointed at the same
database, so you can move either around, add scheduling servers, etc.
very easily. With Task Scheduler, you're tied to the machine where you
scheduled the jobs, which seems like a big PITA to me...
Scheduler when I began working on a scheduling app, and ultimately
decided that Quartz.NET was WAY better. Along with the important point
that Robert made above (which I'm pretty sure is correct), managing
Windows Task Scheduler remotely is far inferior to Quartz.NET. To
manage Task Scheduler, you either have to remote into that machine, or
else write a web service to be hosted on that machine that can
communicate with the Scheduler via the C# wrapper you mentioned. With
Quartz.NET, if you use a database jobstore, your GUI for managing jobs
and the Quartz.NET service itself only have to be pointed at the same
database, so you can move either around, add scheduling servers, etc.
very easily. With Task Scheduler, you're tied to the machine where you
scheduled the jobs, which seems like a big PITA to me...
zambak
Jan 26, 2011, 4:14:34 PM1/26/11
to Quartz.NET
Maybe I am wrong, but I don't see difference in managing WTS2 vs
Quartz via web app...
Granted Quartz is more flexible when it comes to management, but if
you are hosting a web app, then it can manage WTS2 tasks on the same
server (same as quartz)...
Correct?
Again this is all scenario dependent...
Another such scenario is when you have to execute scheduled task/job
on the server on regular basis...
Do you use WTS2 with an exe or do you "wrap" Quartz scheduler into a
windows service and have it run your job(s)...
Furthermore, I think WTS2 runs as windows service (and manages all
tasks)....
In this scenario what would be pros/cons?....
I wish someone would post a bulleted list of all scenarios with pros/
cons of both WTS2 and Quartz....That would be nice...:))
On Jan 20, 10:50 pm, RambleCampbell <campbelllan...@hotmail.com>
wrote:
Quartz via web app...
Granted Quartz is more flexible when it comes to management, but if
you are hosting a web app, then it can manage WTS2 tasks on the same
server (same as quartz)...
Correct?
Again this is all scenario dependent...
Another such scenario is when you have to execute scheduled task/job
on the server on regular basis...
Do you use WTS2 with an exe or do you "wrap" Quartz scheduler into a
windows service and have it run your job(s)...
Furthermore, I think WTS2 runs as windows service (and manages all
tasks)....
In this scenario what would be pros/cons?....
I wish someone would post a bulleted list of all scenarios with pros/
cons of both WTS2 and Quartz....That would be nice...:))
On Jan 20, 10:50 pm, RambleCampbell <campbelllan...@hotmail.com>
wrote:
Reply all
Reply to author
Forward
0 new messages