Microsoft Application Block for .NET
- EXCEPTION
Workflow
The Flow of Logic WHEN The Exception Management Application Block Is Used to Publish An Exception Illustrate In The Preceding Diagram IS FOLLOWS:
1) The Application Throws An Exception, Which Can Be deive from the baseApplicationException Class Provided in The Exception Management Application Block.
2) The application calls The publics The publicationManager class.
3) The ExceptionManager Class Uses The ExceptionManagerSectionHandler Class To Retrieve The Application's Exception Management Settings.
4) The Exception Management Settings in The Application's Configuration File (if any) Are Read to Determine How The Exception Should Be Published.
5) If no settings are found, the exception is published in the Windows Event Log by using the DefaultPublisher class. If the application has exception management settings configured, the publishers listed in the configuration file, which can include the DefaultPublisher class and custom publisher classes ..............................
6) IF An Exception Occurs While Publishing Through a Custom Publisher, The Exception Manager Raises A CustomPublishereXception, And Uses The Default Publisher To Publish It in The Windows Event Log.
Cache's main interface
IEXCEPTIONPUBLISHER
Exception publishers, Exception Framework provides: defaultpublisher (released to the system event log)
IExceptionXMLPublisher
Main type
ExceptionManager
Profile
It is primarily configured for useful exception publishers.
Calling method
ExceptionManager.publish (Exception, AdditionalInfo);
other
To make sure your OS event log feature is started, you should use the ExceptionManagerInstaller class to install it when installing
