Re: TargetInvocationException makes no sense

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

From: Dmitriy Lapshin [C# / .NET MVP] (x-code_at_no-spam-please.hotpop.com)
Date: 02/17/04 

Date: Tue, 17 Feb 2004 17:45:14 +0200

Yeah it would be a nice feature so you might wish to suggest it to the
Visual Studio team.
One can browse the chain by adding the exception variable to the Watch
window and expanding the InnerException nodes. 

-- 
Dmitriy Lapshin [C# / .NET MVP]
X-Unity Test Studio
http://www.x-unity.net/teststudio.aspx
Bring the power of unit testing to VS .NET IDE
"Uri Dor" <replace_yu_ar_eye@mivzak.com> wrote in message
news:eQZP$ZW9DHA.1672@TK2MSFTNGP12.phx.gbl...
> wouldn't it be nice if the debugger's exception message allowed my to
> dig into that chain?
>
> Dmitriy Lapshin [C# / .NET MVP] wrote:
>
> > Hi,
> >
> > This exception is usually thrown when a remoting call is made across
> > application domain boundaries. It is not that meaningless if you know
where
> > to look for details. The key property is InnerException - you should
examine
> > this one to obtain the real exception occured. Chances are this property
> > will contain another TargetInvocationException instance - so you should
> > continue digging into the InnerException chain until you've found
something
> > meaningful.
> >

Relevant Pages