Quartz.NET - Version Migration Guide

Version Migration Guide

This document outlines changes needed per version upgrade basis. You need to check the steps for each version you are jumping over. You should also check the complete change log.

If you are a new user starting with the latest version, you don’t need to follow this guide. Just jump right to the tutorial

Upgrading to 3.0 from 2.x

Quartz jumped to async/await world and added support for .NET Core with 3.0 release so most significant changes can be found on APIs and functionality available depending on whether you target full .NET Framework or the .NET Core.

Database schema changes

** None so far **

Migrating HolidayCalendar binary format

If you have HolidayCalendars stored in database in binary format (just stored with AdoJobStore). You need to first load them with Quartz 2.4 and then re-store them. This will make the serialization use format that is not dependant on precense of C5 library.

Thread pool changes

  • SimpleThreadPool was removed altogether and it’s now a synonym for DefaultThreadPool
  • Jobs are now ran in CLR thread pool
  • ThreadCount parameter still limits how many items will be queued at most to CLR thread pool
  • Thread priority is no longer supported, you need to remove threadPriority parameter

API Changes

Scheduler and job API methods now are based on Tasks. This reflects how you define your jobs and operate with scheduler.


You now need to make sure that you have proper awaits in place when you operate with the scheduler:

// operating with scheduler is now Task-based and requires appropriate awaits
await scheduler.ScheduleJob(job, trigger);
await scheduler.Start();
await sched.Shutdown(waitForJobsToComplete: true);


Job’s Execute method now returns a Task and can easily contain async code:

// Jobs now return tasks from their Execute methods
public class MyJob : IJob
    public async Task Execute(IJobExecutionContext context)
        // dummy 1ms sleep
        await Task.Delay(1);

If you don’t have any async’ness in your job, you can just return Task.CompletedTask at the end of Execute method (available from .NET 4.6 onwards).

IInterruptableJob interface has been removed. You need to check for IJobExecutionContext’s CancellationToken.IsCancellationRequested to determine whether job interruption has been requested.

IStatefulJob interface that was obsoleted in 2.x has been removed, you should use DisallowConcurrentExecution and PersistJobDataAfterExecution attributes to achieve your goal.

Other APIs

If you have created custom implementations of services used by Quartz, you’re going to need to adapt your code to be async-based.

Configuration changes

You need to now explicitly state whether you want to use binary or json serialization if you are using persistent job store (AdoJobStore) when you configure your scheduler.

  • For existing setups you should use the old binary serialization to ensure things work like before
  • For new projects the JSON serialization is recommended as it should be marginally faster and more robust as it’s not dealing with binary versioning issues
  • Binary is not supported when targeting .NET Core!

Configuring binary serialization strategy, only works against full .NET Framework

var properties = new NameValueCollection
	["quartz.jobStore.type"] = "Quartz.Impl.AdoJobStore.JobStoreTX, Quartz",
	// "binary" is alias for "Quartz.Simpl.BinaryObjectSerializer, Quartz" 
	["quartz.serializer.type"] = "binary"
ISchedulerFactory sf = new StdSchedulerFactory(properties);

Configuring JSON serialization strategy, works against both full .NET framwork and .NET Core.

var properties = new NameValueCollection
	["quartz.jobStore.type"] = "Quartz.Impl.AdoJobStore.JobStoreTX, Quartz",
	// "json" is alias for "Quartz.Simpl.JsonObjectSerializer, Quartz.Serialization.Json" 
	["quartz.serializer.type"] = "json"
ISchedulerFactory sf = new StdSchedulerFactory(properties);

C5 Collections

C5 Collections are no longer ILMerged inside Quartz, .NET 4.5 offers the needed collections.


Common.Logging has been replaced with LibLog to reduce dependencies to none. LibLog should automatically detect your logging framework of choice if it’s supported.


Remoting has been removed and will be replaced with HTTP JSON/RESTish based solution in later release.





Project Supporters

SourceForge.net Logo