Exception Handling in ASP.NET
Common Errors:
1. Divide by Zero
2. Null Reference Exception (Object not initialized)
3. Invalid Input
4. Database connection Timeout
5. Out of Memory Exception
6. Insufficient security credentials
7. H/W or N/W failure
2. Null Reference Exception (Object not initialized)
3. Invalid Input
4. Database connection Timeout
5. Out of Memory Exception
6. Insufficient security credentials
7. H/W or N/W failure
How to prevent unwanted exceptions:
1. Always use Try/Catch/Finally
2. Always use custom error pages
2. Always use custom error pages
Event Viewer:
It is located at Control Panel/Administrative Tools/Event Viewer.
It logs all the application, security and system errors.
Security and system errors are handled by operating system but application errors can be configured.
It logs all the application, security and system errors.
Security and system errors are handled by operating system but application errors can be configured.
Error Modes:
Error modes can be set in web.config file. It can be set to RemoteOnly/Off/On. If you make custom error page, set it to on otherwise RemoteOnly/Off.
Tracing:
Tracing can be done on page level as well as on application level.
Tracing shows Control Tree, Session and Application State, Cookie Collection, Header Collection, Form Collection, QueryString Collection, Server Variables.
Trace.Write command allows user to write on trace window.
Tracing shows Control Tree, Session and Application State, Cookie Collection, Header Collection, Form Collection, QueryString Collection, Server Variables.
Trace.Write command allows user to write on trace window.