DemiCode Scheduler 1.1.4

Release notes for version 1.1.4 including both fixes and improvements .

• Disposing Scheduler from eventhandlers caused instance to not dispose
  An event handler attached to Scheduler.ScheduledAlarm or any ISchedule.Alarm that would dispose the scheduler instance, would cause that instance to continue to operate. This has been resolved by the Scheduler internally removing all event handlers attached to it as well as clearing out all ISchedule instances on Dispose().
• Write back to the original config file
  The SchedulerConfiguration sample code overwrites the loaded configuration file passing in the original configuration file name. This caused the .Net Configuration system to throw an exception. SchedulerSettingsManager now handles this so that passing in the same filename that was used to load the configuration section works as expected.
• Debugging Scheduler
  Added documentation on how to diagnose problems in the Scheduler using built-in logging features.
• License key overloads in SchedulerFactory
  In the previous version some Create methods in the SchedulerFactory did not accept a license key. This made it impossible to configure schedulers from configuration files while providing the license key in code. This is now resolved with the addition of the SchedulerFactory.WithLicense() method. This method enables the above-mentioned scenario as well as keeping the SchedulerFactory interface as simple as possible.
• Long delays when initializing Scheduler
  Some users reported a several-seconds delay when accessing the Scheduler classes. This is related to the loading of digitally signed assemblies. When an assembly is digitally signed, the .Net Framework will call out to a third-party site (e.g. VeriSign.com) for certificate validation. If the site cannot be reached, the call will time-out incurring an extra delay when loading the assembly. The check occurs once types in an assembly are referenced, e.g. with a call to SchedulerFactory.Create, causing the call to seemingly take several seconds to complete. To work around this problem, the Scheduler installer now contains an option to install unsigned copies of the assemblies. These assemblies can be used in environments where access to external web sites is blocked, or digital certificates otherwise is not feasible.
• XML reference documentation
  XML reference documentation is now included for all assemblies. These files are necessary to get code comment in IntelliSense in IDEs like Visual Studio.