Wednesday, 12 December 2007
System.Exception vs. General Exception

So...

People sometimes ask, what is the difference between catching System.Exception and the General Exception in a Catch Exception shape in the orchestration designer in BizTalk.

Off course, an obvious difference is, that with the General Exception, you don't get an object with properties to investigate. But then it seems that the General Exception is useless... surely there is a point to it?

Well, I was curious about this myself, so I investigated a bit, and found this post. So basically, I think the catch of the general exception in BizTalk 2006 is a left over from BizTalk 2004. In BizTalk 2004 it made sense, since you actually have exceptions thrown at you that didn't derive from System.Exception. That is no longer possible in .NET 2.0 - they just haven't removed it from the designer - probably just to be backwards compatible.

That's it...

--
eliasen

BizTalk 2004 | BizTalk 2006
Wednesday, 12 December 2007 19:53:15 (Romance Standard Time, UTC+01:00)  #    Comments [4]  | 
Friday, 21 December 2007 16:10:32 (Romance Standard Time, UTC+01:00)
The timing couldn't be more perfect. I'm investigating a current orchestration and it's error messages and I stumbled upon empty error messages. Now I know the reason why. Thnx.
Andy C. Mater | andy_materAT NOSPAMhotmail dot com
Friday, 21 December 2007 18:54:27 (Romance Standard Time, UTC+01:00)
Hi

Glad I could help :-)

--
eliasen
Jan Eliasen | janAT NOSPAMeliasen dot dk
Thursday, 06 November 2008 21:16:31 (Romance Standard Time, UTC+01:00)
What about errors raised from external components called from an orchestration that are not based on the .Net framework? Wouldn't a failed C++ object call be caught by a General Exception block and not the System.Exception block?
Jereme | jdowns69AT NOSPAMhotmail dot com
Sunday, 09 November 2008 01:26:44 (Romance Standard Time, UTC+01:00)
Hi

No, I don't think so. In order to call the c++ component from your orchestration, you will have to reference it from your project, and this will create a .NET wrapper for it. So exceptions thrown by the c++ component is caught and converted into a .NET exception deriving from System.Exception.

This is my best guess...

--
eliasen
Jan Eliasen | janAT NOSPAMeliasen dot dk
All comments require the approval of the site owner before being displayed.
OpenID
Please login with either your OpenID above, or your details below.
Name
E-mail
Home page

Comment (Some html is allowed: a@href@title, b, blockquote@cite, em, i, strike, strong, sub, sup, u) where the @ means "attribute." For example, you can use <a href="" title=""> or <blockquote cite="Scott">.  

Enter the code shown (prevents robots):
Live Comment Preview

Theme design by Jelle Druyts