That's the behaviour I've seen. If you want to handle / log the error, you need to do it in the Application_onerror method, as the ErrorPage is just a client-side redirect.
If you did want to display the error on the error page, you'd have to pass state around, either on the query string, or in one of the Session / Cache etc objects. We use .html files for our Error Pages, rather than dynamic pages - the theory being that if our application ever has an exception that is bad enough for us not to trap it, chances are that it will be broken all over the place :) Kirk -----Original Message----- From: Joćo Pedro Martins [mailto:[EMAIL PROTECTED]] Sent: Tuesday, 7 May 2002 4:18 a.m. To: [EMAIL PROTECTED] Subject: [DOTNET] ErrorPage="url" clears Server.GetLastError() ? The subject says it all. If I trap errors in Application_onerror, all the data pertaining to the data is on the server.getlasterror() structure. If I trap them on a page specified in the aspx page atribute ErrorPage, server.getlasterror() is null. Any help? j -- Joćo Pedro Martins [EMAIL PROTECTED] |create|it| http://www.create.pt http://www.usabilidade.com You can read messages from the DOTNET archive, unsubscribe from DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com. You can read messages from the DOTNET archive, unsubscribe from DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
