Quartz.Serialization.SystemTextJson
3.10.0
Prefix Reserved
See the version list below for details.
dotnet add package Quartz.Serialization.SystemTextJson --version 3.10.0
NuGet\Install-Package Quartz.Serialization.SystemTextJson -Version 3.10.0
<PackageReference Include="Quartz.Serialization.SystemTextJson" Version="3.10.0" />
paket add Quartz.Serialization.SystemTextJson --version 3.10.0
#r "nuget: Quartz.Serialization.SystemTextJson, 3.10.0"
// Install Quartz.Serialization.SystemTextJson as a Cake Addin #addin nuget:?package=Quartz.Serialization.SystemTextJson&version=3.10.0 // Install Quartz.Serialization.SystemTextJson as a Cake Tool #tool nuget:?package=Quartz.Serialization.SystemTextJson&version=3.10.0
::: tip JSON is recommended persistent format to store data in database for greenfield projects. You should also strongly consider setting useProperties to true to restrict key-values to be strings. :::
Quartz.Serialization.SystemTextJson provides JSON serialization support for job stores using System.Text.Json facilities to handle the actual serialization process.
Installation
You need to add NuGet package reference to your project which uses Quartz.
Install-Package Quartz.Serialization.SystemTextJson
Configuring
Classic property-based configuration
var properties = new NameValueCollection
{
["quartz.jobStore.type"] = "Quartz.Impl.AdoJobStore.JobStoreTX, Quartz",
["quartz.serializer.type"] = "stj"
};
ISchedulerFactory schedulerFactory = new StdSchedulerFactory(properties);
Configuring using scheduler builder
var config = SchedulerBuilder.Create();
config.UsePersistentStore(store =>
{
// it's generally recommended to stick with
// string property keys and values when serializing
store.UseProperties = true;
store.UseGenericDatabase(dbProvider, db =>
db.ConnectionString = "my connection string"
);
store.UseSystemTextJsonSerializer();
});
ISchedulerFactory schedulerFactory = config.Build();
Migrating from binary serialization
There's now official solution for migration as there can be quirks in every setup, but there's a recipe that can work for you.
- Configure custom serializer like
MigratorSerializer
below that can read binary serialization format and writes JSON format - Either let system gradually migrate as it's running or create a program which loads and writes back to DB all relevant serialized assets
Example hybrid serializer
public class MigratorSerializer : IObjectSerializer
{
private BinaryObjectSerializer binarySerializer;
private SystemTextJsonObjectSerializer jsonSerializer;
public MigratorSerializer()
{
this.binarySerializer = new BinaryObjectSerializer();
// you might need custom configuration, see sections about customizing
// in documentation
this.jsonSerializer = new SystemTextJsonObjectSerializer();
}
public T DeSerialize<T>(byte[] data) where T : class
{
try
{
// Attempt to deserialize data as JSON
var result = this.jsonSerializer.DeSerialize<T>(data);
return result;
}
catch (JsonReaderException)
{
// Presumably, the data was not JSON, we instead use the binary serializer
return this.binarySerializer.DeSerialize<T>(data);
}
}
public void Initialize()
{
this.binarySerializer.Initialize();
this.jsonSerializer.Initialize();
}
public byte[] Serialize<T>(T obj) where T : class
{
return this.jsonSerializer.Serialize<T>(obj);
}
}
Customizing JSON.NET
If you need to customize JSON.NET settings, you need to inherit custom implementation and override CreateSerializerSettings
.
class CustomJsonSerializer : SystemTextJsonObjectSerializer
{
protected override JsonSerializerOptions CreateSerializerOptions()
{
var options = base.CreateSerializerOptions();
options.Converters.Add(new MyCustomConverter());
return options;
}
}
And then configure it to use
store.UseSerializer<CustomJsonSerializer>();
// or
"quartz.serializer.type" = "MyProject.CustomJsonSerializer, MyProject"
Product | Versions Compatible and additional computed target framework versions. |
---|---|
.NET | net5.0 was computed. net5.0-windows was computed. net6.0 was computed. net6.0-android was computed. net6.0-ios was computed. net6.0-maccatalyst was computed. net6.0-macos was computed. net6.0-tvos was computed. net6.0-windows was computed. net7.0 was computed. net7.0-android was computed. net7.0-ios was computed. net7.0-maccatalyst was computed. net7.0-macos was computed. net7.0-tvos was computed. net7.0-windows was computed. net8.0 is compatible. net8.0-android was computed. net8.0-browser was computed. net8.0-ios was computed. net8.0-maccatalyst was computed. net8.0-macos was computed. net8.0-tvos was computed. net8.0-windows was computed. |
.NET Core | netcoreapp2.0 was computed. netcoreapp2.1 was computed. netcoreapp2.2 was computed. netcoreapp3.0 was computed. netcoreapp3.1 was computed. |
.NET Standard | netstandard2.0 is compatible. netstandard2.1 was computed. |
.NET Framework | net461 was computed. net462 is compatible. net463 was computed. net47 was computed. net471 was computed. net472 was computed. net48 was computed. net481 was computed. |
MonoAndroid | monoandroid was computed. |
MonoMac | monomac was computed. |
MonoTouch | monotouch was computed. |
Tizen | tizen40 was computed. tizen60 was computed. |
Xamarin.iOS | xamarinios was computed. |
Xamarin.Mac | xamarinmac was computed. |
Xamarin.TVOS | xamarintvos was computed. |
Xamarin.WatchOS | xamarinwatchos was computed. |
-
.NETFramework 4.6.2
- Quartz (>= 3.10.0)
- System.Text.Json (>= 8.0.3)
-
.NETStandard 2.0
- Quartz (>= 3.10.0)
- System.Text.Json (>= 8.0.3)
-
net8.0
- Quartz (>= 3.10.0)
NuGet packages (2)
Showing the top 2 NuGet packages that depend on Quartz.Serialization.SystemTextJson:
Package | Downloads |
---|---|
Reddoxx.Quartz.MongoDbJobStore
MongoDb job-store implementation for the quartz-scheduler |
|
Shinya.Scheduling.Quartz.Serialization.SystemTextJson
Shinya.Framework |
GitHub repositories
This package is not used by any popular GitHub repositories.