Quartz.Plugins.TimeZoneConverter
Quartz.NET TimeZoneConverter integration - resolves a trigger's time zone by either its IANA or its Windows id, on either operating system, through https://github.com/mj1856/TimeZoneConverter; Quartz Scheduling Framework for .NET
Install
| Product | Versions |
|---|---|
| .NET |
README
Quartz.Plugins.TimeZoneConverter
Quartz.Plugins.TimeZoneConverter
plugs TimeZoneConverter into Quartz.NET's time zone
lookup, so that both Windows ids (Central America Standard Time) and IANA ids
(America/Guatemala) resolve on either operating system.
Every trigger that names a time zone names it by id, and TimeZoneInfo.FindSystemTimeZoneById answers
with whatever ids the machine happens to know. A schedule written on Windows and run on Linux therefore
throws TimeZoneNotFoundException where the trigger is built or read back — and a schedule kept in a
database is exactly the one that gets moved between them.
Installation
dotnet add package Quartz.Plugins.TimeZoneConverter
Usage
builder.Services.AddQuartz(q => q.UseTimeZoneConverter());
UseTimeZoneConverter hangs off IQuartzBuilder, so the same call configures a scheduler built
without a host.
The call registers a resolver with Quartz.TimeZones, which is what Quartz's own lookups go through:
both spellings then resolve everywhere, and a stored trigger keeps firing after its scheduler moves
host. The registration is process-wide and takes effect at once, so a trigger built before the
scheduler exists resolves its zone too. It is not a plugin — 4.0 retired the one this package used to
ship, along with the quartz.plugin.timeZoneConverter.type key that named it.
Documentation
Changes from Previous Version
Adoption Assessment
A verified publisher signal is available. Assess fit from the package's supported frameworks, license and dependency graph rather than popularity alone.
Related Guides & Workflows
Learn how to evaluate, integrate, or audit this package in your .NET project.