QuartzNet v3.0.0 Release Notes

Release Date: 2017-12-30 // over 6 years ago
  • NEW FEATURE

    • ๐Ÿ‘ท Task based jobs with async/await support, internals work in async/await manner
    • ๐Ÿ‘Œ Support .NET Core / netstandard 2.0 and .NET Framework 4.5.2 and later
    • ๐Ÿ‘Œ Support for Microsoft.Data.Sqlite via provider name SQLite-Microsoft, the old provider SQLite also still works
    • โž• Added preliminary support for SQL Server Memory-Optimized tables and Quartz.Impl.AdoJobStore.UpdateLockRowSemaphoreMOT
    • ๐Ÿšš Common.Logging removed from dependencies
    • ๐Ÿšš C5 Collections removed from ILMerge process, no longer needed
    • โž• Add support for eager validation of job scheduling XML file on plugin start
    • โž• Add support for extra custom time zone resolver function in TimeZoneUtil

    ๐Ÿ’ฅ BREAKING CHANGES

    • ๐Ÿ“ฆ Jobs and plugins are now in a separate assemblies/NuGet packages Quartz.Jobs and Quartz.Plugins
    • ADO.NET provider names have been simplified, the provider names are without version, e.g. SqlServer-20 => SqlServer
    • API methods have been revisited to mainly use IReadOnlyCollection, this hides both HashSets and Lists
    • LibLog has been hidden as internal (ILog etc), like it was originally intended to be
    • SimpleThreadPool is gone, old owned threads are gone
    • โฑ Scheduler methods have been changed to be Task based, remember to await them
    • ๐Ÿ‘ท IJob interface now returns a task
    • Some IList properties have been changed to IReadOnlyList to properly reflect intent
    • ๐Ÿ‘ SQL Server CE support has been dropped
    • DailyCalendar uses now datetimes for excluded dates and has ISet interface to access them
    • IObjectSerializer has new method, void Initialize(), that has to be implemented
    • ๐Ÿšš IInterruptableJob removed in favor of context's CancellationToken

    KNOWN ISSUES

    • ๐Ÿง Issues with time zone ids between Windows and Linux, they use different ids for the same zone
    • ๐Ÿ‘ No remoting support for .NET Core