ASP.NET brings administrator's & developers together....REALLY!
One of the most amazing things that ASP.NET and the .NET Framework brings is two different worlds together. What I'm describing is developers and administrators. In my experience, developers main worries are writing code, solving business needs and just assuming the environment (servers, OS etc..) will be available. On the other hand, administrators worry about having a stable environment so users can perform tasks. These two worlds collide, the analogy I think of is like parents and kids. The parents try to maintain a clean, orderly house. Kids on the other hand are good at just throwing stuff all over. Now I'm not saying developers work is kids play. Do you ever remember your parents yelling pick your stuff up, I want things to be safe and clean!! When adding something like a new web-app or component to an environment, it can be a make a production environment unstable and mess things up.
One of the enhancements of ASP.NET offers is writing to the NT/2000 Event log.
What is the event log you ask? This is a place where system, application or security reports errors. These errors can be viewed by using the Event Viewer under administrative tools.
Why is this such a big deal you ask? My experience as an administrator knows for an application to be supportable and exist in a production environment, they need to use the NT/2000 event log. This allows errors to be reported to either the support staff or the administrators who take care of the server(s). With a few lines of code, your web applications now will be able to act just as if they were full blow applications. This also can help if bugs do come up that your applications, thing will be easy to spot. Traditional ASP app's couldn't do this without a bunch of additional coding, installing a 3rd party component or home-grown solution. Part of the .NET framework now can fully support working with the NT/2000 event log.