I want to brainstorm about a thing I thought about. On the current app im designing, Im using the microsoft appblock for exceptionmanagement. It allow me to easily publish exceptions.

The app is a client-server winforms app. It contains businesslogic at an appserver, as well as some webservices installed on the appserver that allow the client to perform some advanced features. When I thought about exception management, that came into mind was that I should create a database that stored all exceptions from all tiers and from all apps. For example, if an exception occured on a client, who want to visit that computer and open a logfile to read about it, or to have the customer mail teh logfile to our support? The best way would be for the exception to travel to the database where it is logged, and a mail is sent to our support, notifying them that an exception has occured. The webservices and the business logic and DAL should ALL use the same component for handling exceptions... no matter where it occured, it should be logged on the database. Then it is very easy for an admin or support to browse that database through some fancy .net GUI...

That means that ALL exceptions in an app, no matter WHERE it occured (in tier1, 2 or 3) or at a different physical location (client) all are stored at teh same place!!


what do you think about such an idea? Is it practically? How should I encapsulate the application block so I can allow it to be published as a webservice?

thank you for your comments!! Im looking forard to a rewarding discussion about this!!

kind regards
Henrik