I noticed that as of .NET 2.0, the logging capabilities in System.Diagnostics look like they've gotten more robust. I'm wondering if Log4net will be replaced in favor of System.Diagnostics logging at some point?

IMHO, you should not have to call log4net.Config.XmlConfigurator.Configure() to enable logging, it should be on by default.

Once log4net begins to support it, you will be able to use it through log4net too.



A third-party library shouldn't mess with your application logging settings. XmlConfigurator is not the only way to configure logging in log4net.

I was able to configure Log4net to direct it's output to my System.Diagnostics trace log. That wasn't a problem. The question that I have is, why not just use what's built in if it's sufficiently robust than to have an additional dependency?