👁 Image
Quartz 3.18.1

layout: default title: Quartz.NET Quick Start Guide

Welcome to the Quick Start Guide for Quartz.NET. As you read this guide, expect to see details of:

• Downloading Quartz.NET
• Installing Quartz.NET
• Configuring Quartz to your own particular needs
• Starting a sample application

Download and Install

You can either download the zip file or use the NuGet package. NuGet package contains only the binaries needed to run Quartz.NET, zip file comes with source code, samples and Quartz.NET server sample application.

NuGet Package

Couldn't get any simpler than this. Just fire up Visual Studio (with NuGet installed) and add reference to package Quartz from package manager extension:

• Right-click on your project's References and choose Manage NuGet Packages...
• Choose Online category from the left
• Enter Quartz to the top right search and hit enter
• Choose Quartz.NET from search results and hit install
• Done!

or from NuGet Command-Line:

Install-Package Quartz

If you want to add JSON Serialization, just add the package the same way.

Zip Archive

Short version: Once you've downloaded Quartz.NET, unzip it somewhere, grab the Quartz.dll from bin directory and start to use it.

Quartz core library does not have any hard binary dependencies. You can opt-in to more dependencies when you choose to use JSON serialization package, which requires JSON.NET. You need to have at least Quartz.dll beside your app binaries to successfully run Quartz.NET. So just add it as a references to your Visual Studio project that uses them. You can find these dlls from extracted archive from path bin\your-target-framework-version\release\Quartz.

Configuration

This is the big bit! Quartz.NET is a very configurable library. There are two main ways (which are not mutually exclusive) to supply Quartz.NET configuration information:

Fluent Scheduler Builder API

You can configure scheduler using C# fluent API, or via providing NameValueCollection parameter to scheduler factory which contains configuration keys and values.

// you can have base properties
var properties = new NameValueCollection();

// and override values via builder
IScheduler scheduler = await SchedulerBuilder.Create(properties)
 // default max concurrency is 10
 .UseDefaultThreadPool(x => x.MaxConcurrency = 5)
 // this is the default 
 // .WithMisfireThreshold(TimeSpan.FromSeconds(60))
 .UsePersistentStore(x =>
 {
 // force job data map values to be considered as strings
 // prevents nasty surprises if object is accidentally serialized and then 
 // serialization format breaks, defaults to false
 x.UseProperties = true;
 x.UseClustering();
 // there are other SQL providers supported too 
 x.UseSqlServer("my connection string");
 // this requires Quartz.Serialization.Json NuGet package
 x.UseJsonSerializer();
 })
 // job initialization plugin handles our xml reading, without it defaults are used
 // requires Quartz.Plugins NuGet package
 .UseXmlSchedulingConfiguration(x =>
 {
 x.Files = new[] { "~/quartz_jobs.xml" };
 // this is the default
 x.FailOnFileNotFound = true;
 // this is not the default
 x.FailOnSchedulingError = true;
 })
 .BuildScheduler();

await scheduler.Start();

Configuration files

Following files are searched for known configuration properties:

• YourApplication.exe.config configuration file using quartz-element (full .NET framework only)
• appsettings.json (.NET Core/NET5 onwards)
• quartz.config file in your application's root directory (works both with .NET Core and full .NET Framework)

Full documentation of available properties is available in the .

To get up and running quickly, a basic quartz.config looks something like this:

quartz.scheduler.instanceName = MyScheduler
quartz.jobStore.type = Quartz.Simpl.RAMJobStore, Quartz
quartz.threadPool.maxConcurrency = 3

Remember to set the Copy to Output Directory on Visual Studio's file property pages to have value Copy always. Otherwise the config will not be seen if it's not in build directory.

The scheduler created by this configuration has the following characteristics:

• quartz.scheduler.instanceName - This scheduler's name will be "MyScheduler".

• quartz.threadPool.maxConcurrency - Maximum of 3 jobs can be run simultaneously (default is 10).

• quartz.jobStore.type - All of Quartz's data, such as details of jobs and triggers, is held in memory (rather than in a database).

• Even if you have a database and want to use it with Quartz, I suggest you get Quartz working with the RamJobStore before you open up a whole new dimension by working with a database.

::: tip Actually you don't need to define these properties if you don't want to, Quartz.NET comes with sane defaults :::

Starting a Sample Application

Now you've downloaded and installed Quartz, it's time to get a sample application up and running. The following code obtains an instance of the scheduler, starts it, then shuts it down:

Program.cs

using System;
using System.Threading.Tasks;

using Quartz;
using Quartz.Impl;

namespace QuartzSampleApp
{
 public class Program
 {
 private static async Task Main(string[] args)
 {
 // Grab the Scheduler instance from the Factory
 StdSchedulerFactory factory = new StdSchedulerFactory();
 IScheduler scheduler = await factory.GetScheduler();

 // and start it off
 await scheduler.Start();

 // some sleep to show what's happening
 await Task.Delay(TimeSpan.FromSeconds(10));

 // and last shut down the scheduler when you are ready to close your program
 await scheduler.Shutdown();
 }
 }
}

As of Quartz 3.0 your application will terminate when there's no code left to execute after scheduler.Shutdown(), because there won't be any active threads. You should manually block exiting of application if you want scheduler to keep running also after the Task.Delay and Shutdown has been processed.

Now running the program will not show anything. When 10 seconds have passed the program will just terminate. Lets add some logging to console.

Adding logging

LibLog can be configured to use different logging frameworks under the hood; namely Log4Net, NLog and Serilog.

When LibLog does not detect any other logging framework to be present, it will be silent. We can configure a custom logger provider that just logs to console show the output if you don't have logging framework setup ready yet.

LogProvider.SetCurrentLogProvider(new ConsoleLogProvider());

private class ConsoleLogProvider : ILogProvider
{
 public Logger GetLogger(string name)
 {
 return (level, func, exception, parameters) =>
 {
 if (level >= LogLevel.Info && func != null)
 {
 Console.WriteLine("[" + DateTime.Now.ToLongTimeString() + "] [" + level + "] " + func(), parameters);
 }
 return true;
 };
 }

 public IDisposable OpenNestedContext(string message)
 {
 throw new NotImplementedException();
 }

 public IDisposable OpenMappedContext(string key, object value, bool destructure = false)
 {
 throw new NotImplementedException();
 }
}

Trying out the application

Now we should get a lot more information when we start the application.

[12.51.10] [Info] Quartz.NET properties loaded from configuration file 'C:\QuartzSampleApp\quartz.config'
[12.51.10] [Info] Initialized Scheduler Signaller of type: Quartz.Core.SchedulerSignalerImpl
[12.51.10] [Info] Quartz Scheduler created
[12.51.10] [Info] RAMJobStore initialized.
[12.51.10] [Info] Scheduler meta-data: Quartz Scheduler (v3.0.0.0) 'MyScheduler' with instanceId 'NON_CLUSTERED'
 Scheduler class: 'Quartz.Core.QuartzScheduler' - running locally.
 NOT STARTED.
 Currently in standby mode.
 Number of jobs executed: 0
 Using thread pool 'Quartz.Simpl.DefaultThreadPool' - with 3 threads.
 Using job-store 'Quartz.Simpl.RAMJobStore' - which does not support persistence. and is not clustered.

[12.51.10] [Info] Quartz scheduler 'MyScheduler' initialized
[12.51.10] [Info] Quartz scheduler version: 3.0.0.0
[12.51.10] [Info] Scheduler MyScheduler_$_NON_CLUSTERED started.

We need a simple test job to test the functionality, lets create HelloJob that outputs greetings to console.

public class HelloJob : IJob
{
	public async Task Execute(IJobExecutionContext context)
	{
		await Console.Out.WriteLineAsync("Greetings from HelloJob!");
	}
}

To do something interesting, you need code just after Start() method, before the Task.Delay.

// define the job and tie it to our HelloJob class
IJobDetail job = JobBuilder.Create<HelloJob>()
	.WithIdentity("job1", "group1")
	.Build();

// Trigger the job to run now, and then repeat every 10 seconds
ITrigger trigger = TriggerBuilder.Create()
	.WithIdentity("trigger1", "group1")
	.StartNow()
	.WithSimpleSchedule(x => x
		.WithIntervalInSeconds(10)
		.RepeatForever())
	.Build();

// Tell quartz to schedule the job using our trigger
await scheduler.ScheduleJob(job, trigger);

// You could also schedule multiple triggers for the same job with
// await scheduler.ScheduleJob(job, new List<ITrigger>() { trigger1, trigger2 }, replace: true);

The complete console application will now look like this

using System;
using System.Threading.Tasks;

using Quartz;
using Quartz.Impl;
using Quartz.Logging;

namespace QuartzSampleApp
{
 public class Program
 {
 private static async Task Main(string[] args)
 {
 LogProvider.SetCurrentLogProvider(new ConsoleLogProvider());

 // Grab the Scheduler instance from the Factory
 StdSchedulerFactory factory = new StdSchedulerFactory();
 IScheduler scheduler = await factory.GetScheduler();

 // and start it off
 await scheduler.Start();

 // define the job and tie it to our HelloJob class
 IJobDetail job = JobBuilder.Create<HelloJob>()
 .WithIdentity("job1", "group1")
 .Build();

 // Trigger the job to run now, and then repeat every 10 seconds
 ITrigger trigger = TriggerBuilder.Create()
 .WithIdentity("trigger1", "group1")
 .StartNow()
 .WithSimpleSchedule(x => x
 .WithIntervalInSeconds(10)
 .RepeatForever())
 .Build();

 // Tell quartz to schedule the job using our trigger
 await scheduler.ScheduleJob(job, trigger);

 // some sleep to show what's happening
 await Task.Delay(TimeSpan.FromSeconds(60));

 // and last shut down the scheduler when you are ready to close your program
 await scheduler.Shutdown();

 Console.WriteLine("Press any key to close the application");
 Console.ReadKey();
 }

 // simple log provider to get something to the console
 private class ConsoleLogProvider : ILogProvider
 {
 public Logger GetLogger(string name)
 {
 return (level, func, exception, parameters) =>
 {
 if (level >= LogLevel.Info && func != null)
 {
 Console.WriteLine("[" + DateTime.Now.ToLongTimeString() + "] [" + level + "] " + func(), parameters);
 }
 return true;
 };
 }

 public IDisposable OpenNestedContext(string message)
 {
 throw new NotImplementedException();
 }

 public IDisposable OpenMappedContext(string key, object value, bool destructure = false)
 {
 throw new NotImplementedException();
 }
 }
 }

 public class HelloJob : IJob
 {
 public async Task Execute(IJobExecutionContext context)
 {
 await Console.Out.WriteLineAsync("Greetings from HelloJob!");
 }
 }
}

Creating and initializing database

In order to use SQL persistence storage for Quartz and enabling features like clustering, you need to create a database and initialize the schema objects using SQL scripts. First you need to create a database and credentials for Quartz. After you have a database that Quartz will be able to connect to, you also need to create database tables and indexes that Quartz needs for successful operation.

You can find latest DDL scripts in Quartz's GitHub repository and they are also contained in the ZIP archive distribution. There are also thirty party additions to Quartz that enable other types of storage, like NoSQL databases. You can search for them on NuGet.

Now go have some fun exploring Quartz.NET! You can continue by reading .