http://ayende.comAyende @ RahienCopyright (C) Ayende Rahien 2004 - 2021 (c) 202660Maybe you can take a look at the following: http://weblogs.asp.net/rashid/archive/2007/09/19/new-project-asp-net-ajax-exception-logging.aspx http://ayende.com/3084/asp-net-ajax-error-handling-and-wtf#comment11http://ayende.com/3084/asp-net-ajax-error-handling-and-wtf#comment11Mon, 07 Jan 2008 14:15:17 GMTASP.NET in some places is the worst Microsoft framework I have ever seen. The only kind of unsolvable problems my team hits periodically is the underpowered serialization model whiich is also nearly unextensible. http://ayende.com/3084/asp-net-ajax-error-handling-and-wtf#comment10http://ayende.com/3084/asp-net-ajax-error-handling-and-wtf#comment10Mon, 07 Jan 2008 09:51:56 GMTDesperate times call for desperate measures - I wouldn't seriously consider introducing PostSharp at such a later hour either, that way lays madness. I wonder what the rationale to write it that way was to begin with. http://ayende.com/3084/asp-net-ajax-error-handling-and-wtf#comment9http://ayende.com/3084/asp-net-ajax-error-handling-and-wtf#comment9Sun, 06 Jan 2008 20:29:28 GMTI probably could, but I don't want to introduce it now. Going to byte code weaving just to get logging on exceptions is crazy. http://ayende.com/3084/asp-net-ajax-error-handling-and-wtf#comment8http://ayende.com/3084/asp-net-ajax-error-handling-and-wtf#comment8Sun, 06 Jan 2008 20:24:54 GMTUgh... that's not pleasant! Just a thought - but couldn't you get at least get partial exception coverage (excluding serialization issues occurring outside of the method call) by using PostSharp with an OnException aspect - at least you're only having to decorate each class with a single attribute to get some logging then. Admittedly not a nice solution... but it's better then no logging at all ;o) http://ayende.com/3084/asp-net-ajax-error-handling-and-wtf#comment7http://ayende.com/3084/asp-net-ajax-error-handling-and-wtf#comment7Sun, 06 Jan 2008 20:11:12 GMTEl, Error handling is a key part of any product. Sorry, getting it wrong. Getting it _that_ wrong is very bad. Getting it _that_ wrong and having no way in to fix it, even worse. http://ayende.com/3084/asp-net-ajax-error-handling-and-wtf#comment6http://ayende.com/3084/asp-net-ajax-error-handling-and-wtf#comment6Sun, 06 Jan 2008 19:13:04 GMTIt's still a very young product, and script services are brand new. This is the kind of feedback they would like, but probably with a little less derision and scorn. http://ayende.com/3084/asp-net-ajax-error-handling-and-wtf#comment5http://ayende.com/3084/asp-net-ajax-error-handling-and-wtf#comment5Sun, 06 Jan 2008 18:55:48 GMTFred, It is not unhandled. It is handled in a way that is not appropriate. http://ayende.com/3084/asp-net-ajax-error-handling-and-wtf#comment4http://ayende.com/3084/asp-net-ajax-error-handling-and-wtf#comment4Sun, 06 Jan 2008 17:59:01 GMTIf it is throwing an exception, could you use the AppDomain UnhandledException event to trap those that are not passed through the application_error? http://ayende.com/3084/asp-net-ajax-error-handling-and-wtf#comment3http://ayende.com/3084/asp-net-ajax-error-handling-and-wtf#comment3Sun, 06 Jan 2008 17:01:27 GMTJustin, No, there isn't a script manager involved, because I am talking specifically about using script services only. http://ayende.com/3084/asp-net-ajax-error-handling-and-wtf#comment2http://ayende.com/3084/asp-net-ajax-error-handling-and-wtf#comment2Sun, 06 Jan 2008 15:41:26 GMTI'm assuming you're working with ASP.Net on this one. You should use the ScriptManager.AsyncPostBackError event. If you inherited from ScriptManager before using it - just write some in "myScriptManager" that catchs the exception and logs it. If you havn't inherited the ScriptManager but are using a BasePage you can get the ScriptManager via: "ScriptManager.GetCurrent(this.Page)" and then hook up into it's events. Additionally, using the "AsyncPostBackErrorMessage" you can change the error message to something friendly like "Something happened. We logged it. Don't worry about it" from inside the event's EventHandler. http://ayende.com/3084/asp-net-ajax-error-handling-and-wtf#comment1http://ayende.com/3084/asp-net-ajax-error-handling-and-wtf#comment1Sun, 06 Jan 2008 15:35:49 GMT