Issue #2 describes an enhancement that - as a side effect - allows users to move job configuration out of the NCron.exe.config file. By introducing an abstraction over the schedule configuration, it would be possible to also allow users to move this part out of the XML file (the part that currently lives in the <plans> element).

The two enhancements, in combination, makes it possible to move all "business relevant configuration" to a separate configuration system. By allowing configuration to come from arbitrary file, network or database sources, it gets a lot easier to NCron with other systems.

Issue #13 has removed the entire configuration system, and there is no support for have scheduling configuration outside of the service application.

The functionality should be reimplemented in a way that allows registrations like:

service.AddScheduleSource(new SomeScheduleSourceImplementation());

Replaced by issue #14.