How to correctly unwrap a TargetInvocationException? [duplicate]

Question

I am writing a component which, at the top level, invokes a method via reflection. To make my component easier to use, I'd like to catch any exceptions thrown by the invoked method and unwrap them.

Thus, I have something like:

try { method.Invoke(obj, args); }
catch (TargetInvocationException ex) {
    throw ex.InnerException;
}

However, this blows away the inner exception stack trace. I can't use just throw here (because I'm rethrowing a different exception object). What can I do in my catch block to make sure that the original exception type, message, and stack trace all get through?

No need to place tags in your question title. Tagging correctly is sufficient. — spender
– spender, Commented Jul 9, 2013 at 18:19
Why do you think it makes it easier to confuse the stack trace? — John Saunders
– John Saunders, Commented Jul 9, 2013 at 18:58

Community · Accepted Answer · 2017-05-23 12:17:11Z

37

As answered here, starting with .NET 4.5 you can use the ExceptionDispatchInfo class to unwrap the inner exception.

try
{
    someMethod.Invoke();
}
catch(TargetInvocationException ex)
{
    ExceptionDispatchInfo.Capture(ex.InnerException).Throw();
}

edited May 23, 2017 at 12:17

CommunityBot

11 silver badge

answered Oct 10, 2014 at 15:29

Dusty

4,0012 gold badges31 silver badges42 bronze badges

Sign up to request clarification or add additional context in comments.

1 Comment

Zwirbelbart Over a year ago

Should be marked as the answer. Had the same problem and it was driving me crazy.

Collectives™ on Stack Overflow

How to correctly unwrap a TargetInvocationException? [duplicate]

1 Answer 1

1 Comment

Linked

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

1 Comment

Linked

Related