log4net死了吗? [英] Is log4net dead?

问题描述

我正在寻找一个日志记录框架，并且 log4net 似乎很流行.最新版本是2年前.尚未为.net 3.0或3.5甚至Visual Studio 2008进行过更新.是否应该考虑更新的内容(除了entlib)?

I'm looking for a logging framework and it seems log4net is or was very popular. The last release was over 2 years ago. It has not been updated for .net 3.0 or 3.5 or even visual studio 2008. Is there something more recent (other then entlib) I should be considering?

推荐答案

Log4j(这是log4net的基础)多年来没有更新.同一作者还有其他替代方法(slf4j和logback)以及其他替代方法，但是log4j仍然被大量使用.它还没有死，只是到了真正不需要它的地步.没有任何东西可以证明这项工作是合理的，也不会破坏向后兼容性.当这发生在商业项目上时，公司必须为产品发明其他目的或做其他事情，而产品确实会消失.在开放源代码中，并非如此.

Log4j (which was the basis for log4net) hasn't been updated in years. There are other alternatives from the same author (slf4j and logback) and others, but log4j is still used plenty and plenty viable. It isn't dead, it just got to the point where there was nothing more really was needed for it. Nothing that justified the work or wouldn't break backwards compatability. When that happens to a commercial project, the company has to invent a whole other purpose for the product or do something else and the product does indeed die. In open source, not really.

作为一个比较点，JUnit多年来基本上一无所获.然后Java获得了注释，JUnit获得了竞争(TestNG)，并且它突然又在发展.现在，原始开发人员可能不会在每种情况下都出现在周围，但是随后该项目将被分叉或改编.例如，TestNG允许从JUnit进行平滑迁移.

As a point of comparison, JUnit was basically going nowhere for years. Then Java got annotations, JUnit got competition (TestNG) and it is suddenly moving along again. Now the original developers may not end up being around in every case, but then the project would be forked or adapted. For example, TestNG allowed a smooth migration path from JUnit.

因此，最重要的是，如果它流行并被使用，它将不会对您造成伤害.

So the bottom line is if it is popular and used, it will not die on you.

这篇关于log4net死了吗?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！