grennis wrote:
They lost their own frickin' key pair. You trust them with your code?
The log4net project is already suffering, and this is a major setback which, to me, pushes them into obscurity. Please switch to something more robust i.e. Enterprise Library Logging.
Well, I'm not giving them my code, but I do trust them for logging. Log4net (and log4j before that) has been around for a long time, is stable and very configurable. The key pair issue is a problem for many, but it is what it is. The point of using a "final" release is still a key point for many companies, and the key pair issue doesn't lower the quality of code in the 1.2.10 release.
NLog looks like a good alternative, but I haven't used it first-hand so I can't say for sure. Microsoft's "Enterprise" libraries are all fairly amateur code IMHO.
Rather than swap one logging implementation for another, I would prefer to see a logging abstraction put in place, similar to Apache's commons-logging; perhaps
Castle's logging service. This way, people can choose what logging implementation they prefer and not have to deal with these hard dependency issues. Fans of Enterprise Library Logging could probably have that added to the abstraction as well. This way everyone's preferences are met and coupling is lowered.
Cheers,
Kevin