There are couple of built-in ways to configure Quartz.NET, here's a small comparison.
- Code based configuration
- You use the scheduler API to create/update/delete jobs and triggers
- Schedules and jobs configured by hard coding naturally require recompilation, using a UI or such with scheduler API and persistent job store is a different story
- XML Configuration
- You can schedule jobs and watch XML file for changes
- See Can quartz.net reconfigure jobs when config file changes? for example of watching for file changes
- There is no tooling available as far as I know besides intellisense with Visual Studio when you have the XSD file associated with XML file
Then again, you have job store options. You can use any job store regardless of the way you configure your scheduler/jobs/triggers.
- RAMJobStore
- Fastest (but usually not a factor) and simplest to setup job store but no way to recover from missed trigger fires caused by server reboots etc
- AdoJobStore
- Stores triggers, jobs and their states between restarts and allows you to run Quartz.NET clustered for fail-over and scale
There are also couple web based administration UI available, see Any open-source admin UI for quartz.NET for details.
The Quartz.NET tutorial is always a good place to start too.