G
Guest
If I leave a legacy ASP page in my web app, ASP.NET serves the page just
fine. If an error is encountered on the page, however, it doesn't give me
the friendly error message that ASP did. The page I get is the 500 (Internal
Server Error) page. Is there a way I can trap errors in a legacy ASP page
and emit useful diagnostic info?
Thanks!
fine. If an error is encountered on the page, however, it doesn't give me
the friendly error message that ASP did. The page I get is the 500 (Internal
Server Error) page. Is there a way I can trap errors in a legacy ASP page
and emit useful diagnostic info?
Thanks!