净记录仪(自己写的VS的log4net /企业记录器/ n日志等)

问题描述:

我的IT部门与有关50岁以上的开发工作。它曾经是约100多个开发人员,但被削减,因为经济衰退。

I work for an IT department with about 50+ developers. It used to be about 100+ developers but was cut because of the recession.

当我们部门是更大的存在作出了雄心勃勃的努力,成立了专门的建筑群。

When our department was bigger there was an ambitious effort made to set up a special architecture group.

一件事这个小组决定做的是创造我们自己的内部记录。他们认为这是我们能一起度过的recources和自己做这样一个简单的任务。现在,我们有与性能和难度查看日志生成一些员工感到沮丧,我们花费的recources基础设施这样的东西,而不是专注于为我们的业务和使用的东西已经存在像log4net的或企业记录器的问题。

One thing this group decided to do was create our own internal logger. They thought it was such a simple task that we could spend recources and do it ourselves. Now we are having issues with performance and difficulty viewing the logs generated and some employees are frustrated that we are spending recources on infrastructure stuff like this instead of focusing on serving our business and using stuff that already exists like log4net or Enterprise Logger.

您可以协助我列出了原因,你应该的没有的创建自己的.NET记录。

Can you assist me in listing up reasons why you should not create your own .net logger.

另外的原因,为什么你的应该的欢迎得到的观点中肯:)

Also reasons for why you should are welcome to get a fair point of view :)

我会采取不同的方法。如何先引入一个公共接口以自己的库,例如通用基础架构库( http://netcommon.sourceforge.net/ )。然后你就可以逐步将所有项目转移到该接口,如果你自己的库达不到大型项目的工作,然后简单地切换到开源框架之一(甚至是商业解决方案)。

I would take a different approach. How about first introducing a common interface to your own library such as Common Infrastructure Libraries (http://netcommon.sourceforge.net/). Then you can gradually move all projects over to that interface and if your own library is not up to the job for large projects then simply switch over to one of the open source frameworks (or even a commercial solution).

HTH 亚历克斯