Passive registration in an existing .NET web application?

Question

I just started working on the ASP.NET 2.0 Web Application browser. As in the case of many applications with abandoned fields, the architecture and, in particular, the architecture of the exception log are inconsistent and in some places are absent or incorrect (swallowing exceptions, re-throwing, using them for control logic, etc.)

As a starting point for all this to be controlled, I would just like to make a complete capture of all the exceptions that are excluded in the application and put them somewhere in the form of a database table. Unfortunately, the explication code, which in the application will last many days and possibly weeks of work, so this eliminates the possibility of manual coding (for example, put logger.log everywhere) and things like log4net and nlog. What I am looking for another, easier solution to the problem.

After some quick reading here, I came across various technologies such as:

• Aspect-oriented programming, for example
  • Attribute based
  • Post sharp library
  • Microsoft Unity
  • Unity Castle
• Web handlers
  • ELMAH
  • Others?

? , , . , , , , .

EDIT:

, , , **** **** ( , , ). Elmah ? , ?

Answer 1

elmah . , , . , - , .

. , , web.config. 10 .

Answer 2

. ASP.NET. , .

, , , . , ( ), - , DAL.

---

Enterprise Library , Design for Operations , , ':

, Windows.

. -, Visual Team Team System Management (TSMMD). TSMMD . , ( ) . System Center Operations Manager 2007. , , Microsoft Windows.

Answer 3

Consider using the Aspect Oriented Framework to enter your registration code at the initial compilation time. Registration is an AOP training application, so most packages should be able to meet your requirements.

Here is a good list of AOP libraries. http://www.bodden.de/tools/aop-dot-net/

I played AOP in .NET about 4 years ago, it looks like libraries have matured significantly since then.