![]() |
How do I catch unhandled Exceptions in Webservice (2.0)
Hello Everybody!
How do I catch unhandled exceptions in a Webservice application - .Net Framework 2.0? In Windows I can subscribe to the AppDomain.CurrentDomain.UnhandledException event. In ASP.Net applications Application_Error event handler can be used. How do I get a similar functionality in a Webservice application? I would like to be able log errors globally, *on the server side*, without using try/catch blocks all over the code. Thank you, Tomasz |
RE: How do I catch unhandled Exceptions in Webservice (2.0)
Hello Tomasz,
As for the ASP.NET webservice application, the exception handling mechanism of it is quite different from ASP.NET web application. the Application_Error event only works for web page application. For XML Webservice, since all the unhandled exceptions in application are captured and wrappered as a SoapException, also , this exception will be serialized as a Soap <fault> element in SOAP message. #Handling and Throwing Exceptions in XML Web Services http://msdn2.microsoft.com/en-us/library/ds492xtk.aspx If you want to add a global handler to intercept all the exceptions occured in ASP.NET webservice, you may consider creating a custom soapExtension to do the work. Here is a good tech article detailedly discuss on this: #User Friendly ASP.NET Exception Handling http://www.codeproject.com/aspnet/AS...onHandling.asp If you have anything uncleaer on this, please feel free to let me know. Sincerely, Steven Cheng Microsoft MSDN Online Support Lead ================================================== Get notification to my posts through email? Please refer to http://msdn.microsoft.com/subscripti...ult.aspx#notif ications. Note: The MSDN Managed Newsgroup support offering is for non-urgent issues where an initial response from the community or a Microsoft Support Engineer within 1 business day is acceptable. Please note that each follow up response may take approximately 2 business days as the support professional working with you may need further investigation to reach the most efficient resolution. The offering is not appropriate for situations that require urgent, real-time or phone-based interactions or complex project analysis and dump analysis issues. Issues of this nature are best handled working with a dedicated Microsoft Support Engineer by contacting Microsoft Customer Support Services (CSS) at http://msdn.microsoft.com/subscripti...t/default.aspx. ================================================== This posting is provided "AS IS" with no warranties, and confers no rights. |
Re: How do I catch unhandled Exceptions in Webservice (2.0)
Thank you, Steven, I will check those articles out.
Tomasz "Steven Cheng[MSFT]" <stcheng@online.microsoft.com> wrote in message news:K$9FHstOHHA.2080@TK2MSFTNGHUB02.phx.gbl... > Hello Tomasz, > > As for the ASP.NET webservice application, the exception handling > mechanism > of it is quite different from ASP.NET web application. the > Application_Error event only works for web page application. For XML > Webservice, since all the unhandled exceptions in application are captured > and wrappered as a SoapException, also , this exception will be serialized > as a Soap <fault> element in SOAP message. > > #Handling and Throwing Exceptions in XML Web Services > http://msdn2.microsoft.com/en-us/library/ds492xtk.aspx > > If you want to add a global handler to intercept all the exceptions > occured > in ASP.NET webservice, you may consider creating a custom soapExtension to > do the work. Here is a good tech article detailedly discuss on this: > > #User Friendly ASP.NET Exception Handling > http://www.codeproject.com/aspnet/AS...onHandling.asp > > If you have anything uncleaer on this, please feel free to let me know. > > Sincerely, > > Steven Cheng > > Microsoft MSDN Online Support Lead > > > > ================================================== > > Get notification to my posts through email? Please refer to > http://msdn.microsoft.com/subscripti...ult.aspx#notif > ications. > > > > Note: The MSDN Managed Newsgroup support offering is for non-urgent issues > where an initial response from the community or a Microsoft Support > Engineer within 1 business day is acceptable. Please note that each follow > up response may take approximately 2 business days as the support > professional working with you may need further investigation to reach the > most efficient resolution. The offering is not appropriate for situations > that require urgent, real-time or phone-based interactions or complex > project analysis and dump analysis issues. Issues of this nature are best > handled working with a dedicated Microsoft Support Engineer by contacting > Microsoft Customer Support Services (CSS) at > http://msdn.microsoft.com/subscripti...t/default.aspx. > > ================================================== > > > > This posting is provided "AS IS" with no warranties, and confers no > rights. > > > > |
Re: How do I catch unhandled Exceptions in Webservice (2.0)
Sure. If you have any more specific questions about the approach mentioned
in those articles, please feel free to let me know. Sincerely, Steven Cheng Microsoft MSDN Online Support Lead This posting is provided "AS IS" with no warranties, and confers no rights. |
Re: How do I catch unhandled Exceptions in Webservice (2.0)
Hello Tomasz,
Any progress on this or does the SOAP extension means work for you? Please feel free to let me know if there is anything else we can help. Sincerely, Steven Cheng Microsoft MSDN Online Support Lead This posting is provided "AS IS" with no warranties, and confers no rights. |
| All times are GMT. The time now is 04:02 AM. |
Powered by vBulletin®. Copyright ©2000 - 2013, vBulletin Solutions, Inc.
SEO by vBSEO ©2010, Crawlability, Inc.