Technically you don't need to add it to your project...you just need to make sure that the assembly is in the same directory as your program so it can be loaded at run-time. If that file can't be loaded at run-time then you can't use the log4net bindings.
Previous versions of IBatisNet would default to using IBatisNet.Common.Logging.Impl.ConsoleLoggerFA if the specified log library could not be loaded or was not specified. This behavior was changed because the default ConsoleLogger is relatively slow when you have a lot of configuration files and there is noticeable slow down in application start time. The NoOpLogger is being used now. IBatisNet was throwing an exception about being unable to load IBatisNet.Common.Logging.Log4Net but it was being swallowed by the NoOpLogger. I agree that is difficult to debug. Perhaps we should mimic what log4net does when there are major configuration errors: output a single message to Console and to System.Diagnostics.Trace. ----- Original Message ---- From: Bill Sorensen <[EMAIL PROTECTED]> To: [email protected] Sent: Wednesday, December 27, 2006 4:42:51 PM Subject: Logging tip This might be worth adding to the documentation - it's probably obvious to many people, but it took me hours to figure out. To use Log4Net with iBATIS, you must add a reference to IBatisNet.Common.Logging.Log4Net to your project. Thanks, Bill Sorensen
