In this post I’ll go over what the DisallowConcurrentExecution job attribute does and how to use it. Documentation The Quartz.net documentation states that the DisallowConcurrentExecutionAttribute is An attribute that marks a IJob class as one that must not have multiple instances executed concurrently (where instance is based-upon a IJobDetail definition - or in other words based upon a JobKey.
Continue ReadingIn this post we document the ITrigger interface for Quartz.net. This simple post is one of the documentation series of posts, so it only documents classes and interfaces that are not documented online. Here is the ITrigger interface in all its glory: namespace Quartz { /// <summary> /// The base interface with properties common to all <see cref="
Continue ReadingThis 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 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 Reading