Home/ Questions/Q 388515
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-12T15:46:37+00:00

I work for an IT department with about 50+ developers. It used to be

  • 0

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.

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.

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 🙂

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    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
    Alex

    • 0