Replacing the Error 500 ASP Page - Conclusion
(Page 7 of 7 )
In this article, the ASPError object that was introduced with ASP 3.0 was discussed. This was then related to the use of custom error pages - more specifically the Error 500-100 error page that is displayed when an error occurs on the server during the execution of the script.
A comparison of the functionality between the page that is displayed in ASP 2.0, 3.0, and .NET was made, concluding with a re-implementation of the ASP.NET error page to allow for more rapid debugging.
The re-implementation of the ASP.NET page was followed with coverage on how to use error pages for two different reasons - alerting the end-user to errors, and allowing a developer to have the necessary information to correct such errors. With this information, a less technical error page was developed for end-users before adding further functionality to the development error page.
This functionality included syntax highlighting of the code containing errors, e-mailing of errors to development staff, and the ability to edit and correct the code in-situ. Source-safe integration was then added to allow for the usage of such features in enterprise scale environments.
Finally, the re-use and extension of the code was dealt with - including integration with a bug-tracking system and the replacement of the text-editor with a full-featured one. The result of this article is a replacement for the standard IIS Error 500 page that:
- Makes it simpler to identify errors
- Makes it much simpler to correct these errors
- Allows for more appropriate error messages to be displayed to end-users of the system
The finished error page created in this article| DISCLAIMER: The content provided in this article is not warranted or guaranteed by Developer Shed, Inc. The content provided is intended for entertainment and/or educational purposes in order to introduce to the reader key ideas, concepts, and/or product reviews. As such it is incumbent upon the reader to employ real-world tactics for security and implementation of best practices. We are not liable for any negative consequences that may result from implementing any information covered in our articles or tutorials. If this is a hardware review, it is not recommended to open and/or modify your hardware. |
