<< Quicklearn BizTalk 2006 R2 Deep Dive course | Back on "track" >>

System.Exception vs. General Exception

by eliasen 12. december 2007 18:53

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

d3fde447-1f94-46af-94e9-f80858a2f22f|0|.0

Tags:

BizTalk 2004 | BizTalk 2006

Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))Hi all When developing BizTalk 2009 solutions using Visual Studio .NET 2008 on Windows Server 2008,...Issues with BizTalk 2009 on VS.NET 2008Hi all I have been running into too many issues with BizTalk 2009 on VS.NET 2008 lately. This post ...fatal error X1001: unknown system exceptionHiI ran into this one a while ago. I couldn't find any information about the error on the internet, ...

Comments (4) -

Andy C. Mater

21-12-2007 15:10:32 #

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.

Jan Eliasen

21-12-2007 17:54:27 #

Hi

Glad I could help

--
eliasen

Jereme

06-11-2008 20:16:31 #

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?

Jan Eliasen

09-11-2008 00:26:44 #

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

Add comment

Name* Required Please choose another name

E-mail*

Country Country flag

5+5 =

b i u quote

Comment
Preview

Notify me when new comments are added

Month List

2006
- juli (1)
- august (4)
- september (5)
- oktober (4)
- november (1)
- december (6)
2007
- januar (5)
- marts (2)
- april (2)
- juni (1)
- juli (1)
- august (2)
- september (3)
- oktober (5)
- november (3)
- december (2)
2008
- januar (1)
- februar (1)
- marts (1)
- maj (1)
- juli (1)
- august (2)
- september (4)
- oktober (2)
- november (20)
- december (6)
2009
- januar (1)
- februar (1)
- marts (6)
- april (8)
- maj (3)
- juni (6)
- juli (15)
- september (3)
- oktober (15)
- november (3)
- december (2)
2010
- januar (4)
- februar (1)
- marts (3)
- april (4)
- maj (2)
- juni (1)
- juli (5)
- august (4)
- september (1)
- oktober (4)
- november (1)
2011
- januar (1)
- marts (1)
- maj (2)
- juli (1)
- august (3)
- september (2)

System.Exception vs. General Exception