title: Usage of Exception handling block in Enterprise Library
body: <p>We have a ASP.NET application that uses the Exception Handling Application block to log our exception to a database (using logging block indirectly).  This all working perfect.  However, since it is using the exception handling block to log data, everytime we wanted to log, we'll have to new'd a System.Exception object.  Since we are not throwing exception, there are no performance issue.  However, we do have to create a new exception object everytime we want to log something.  Is this a bad design?</p>