Provide a logging interface in the core framework

[GoogleCodeExporter]

All serious applications of a cron system will require some level of 
logging. NCron should support logging right out of the box, and the 
service itself should record all job executions and failures to the log.

Logging should be done through an interface, allowing integration with 
third-party logging frameworks.

Original issue reported on code.google.com by jsr%mala...@gtempaccount.com on 6 Jan 2010 at 2:08

[GoogleCodeExporter]

Original comment by jsr%mala...@gtempaccount.com on 7 Jan 2010 at 5:06

• Added labels: Component-Framework

[GoogleCodeExporter]

Default log should ignore debug log entries, and log everything else to the 
Windows 
event log.

Original comment by jsr%mala...@gtempaccount.com on 7 Jan 2010 at 6:07

[GoogleCodeExporter]

NCron.Framework.Logging namespace contains interfaces for logs and log 
factories, as 
well as default implementations using the event log.

NCron.Integration.log4net project contains an implementation of the logging 
interfaces, integrating the popular "log4net" library.

NCron.Service.SchedulingService uses the injected log factory to create log 
instances for each job, providing the log to the job through the CronContext. 
Furthermore, it writes a "info" level message before each job execution, and an 
"error" level message if a job throws an unhandled exception.

NCron.Serice.Program (main entry point) explicitly uses the event log for all 
fatal 
events (unhandled exceptions in NCron itself, or in custom log implementations).

Original comment by jsr%mala...@gtempaccount.com on 17 Jan 2010 at 1:27

• Changed state: Fixed