This is another of the documentation series posts. This post will be documenting the IJobDetail interface. Here it is: namespace Quartz { /// <summary> /// Conveys the detail properties of a given job instance. /// JobDetails are to be created/defined with <see cref="JobBuilder" />. /// </summary> /// <remarks> /// Quartz does not store an actual instance of a <see cref="
Continue ReadingThis post is part of the documenation series. It just provides a place to document some of the classes and interfaces that are not available in the API documentation. In this post we are documenting the IJob interface. Without further ado, here it is: namespace Quartz { /// <summary> /// The interface to be implemented by classes which represent a 'job' to be /// performed.
Continue ReadingUnfortunately it seems that the Quartz.Net API documentation that is available online is not complete. Since I would like to link to some of these classes and interfaces from some of my posts, I’m going to start adding them as separate posts, all tagged as documentation. At some point I’ll tackle generating another set of API documents with all the missing classes but until then, these posts will have to do.
Continue ReadingJobs and triggers are at the very core of the Quartz.Net scheduler. In a nutshell, jobs DO the work and triggers determine WHEN the work gets done. Quartz.Net Jobs Creating a Quartz.Net job is pretty straightforward. First, you must implement the IJob interface. The IJob interface is pretty simple. Here it is:
Continue ReadingLesson 1: Using Quartz There are at least two ways to use Quartz.Net: embedded (hosted) in your application or as a standalone windows service. Embedding Quartz.Net in Your Application If you are going to host the Quartz.Net scheduler in your application, you’ll need to create a scheduler. This can be easily done through the scheduler factory provided in the distribution.
Continue Reading