Upgrading from 3.1.0 to 3.2.2 breaks AdoStore Configuration

Describe the bug

Upgaded from 3.1.0 to 3.2.2, and now my Quartz Scheduler has moved from AdoStore to RAMStore (without changing configuration)

Version used

3.2.2

To Reproduce

I simply upgraded the package from 3.1.0 to 3.2.2 – nothing tricky to reproduce.

Expected behavior

AdoStore would be used for scheduling.

Additional context AppSettings (with removed connection strings):

"Quartz": {
    "quartz.scheduler.instanceId": "AUTO",
    "quartz.scheduler.instanceName": "iModelBridgeService.BackgroundScheduler",
    "quartz.dataSource.myDs.provider": "SqlServer",
    "quartz.dataSource.myDs.connectionString": "connectionStringHere",
    "quartz.jobStore.type": "Quartz.Impl.AdoJobStore.JobStoreTX, Quartz",
    "quartz.jobStore.driverDelegateType": "Quartz.Impl.AdoJobStore.SqlServerDelegate, Quartz",
    "quartz.jobStore.dataSource": "myDs",
    "quartz.jobStore.useProperties": "true",
    "quartz.jobStore.isClustered": "true",
    "quartz.serializer.type": "json"
  },

I do see some changelog notes (in breaking changes section), in regards to removing dependencies on SqlClient. Is this something I need to react to if using Azure SQL for the AdoStore?

[davidhjones]

Closing – seems this issue is resolved. Thanks for the quick help @lahma

[davidhjones]

Done: https://github.com/quartznet/quartznet/pull/1001