Skip to content

Differences with Core.WinService

For those who had developed schedules for Core.WinService, it is important to remark that this is not the same application as the Core.WinService. The main differences are the following:

  • Schedules Loading: At Core.WinService, the Quartz's triggers and schedules were loaded from CORE DB and stored in memory. However, the Infrastructure Scheduler has its own DB and uses the tables provided by Quartz.NET.

  • Configuration: At the Core.WinService app.config file, on the Quartz configuration section, it was possible to change any of the Quartz configuration values. Now, on the Infrastructure Scheduler we only limit to configure limited options at the appsettings.json file from the application layer.

  • Usage: This is the most important point, Core.WinService scheduler registered both kind of schedules, infrastructure and business. As for now, the infrastructure scheduler is responsible for infrastructure schedules, it is still to be designed how we are going to manage the business schedules.