tags:

views:

58

answers:

2

How should I go about collecting exceptions and putting them into an AggregateException to re-throw?

For my specific code, I have a loop and will have zero or more exceptions thrown from a part of the code. I was hoping to just add the new exceptions to the AggregateException as they arise, but the documentation sort of indicates that it should be constructed with all the Exceptions at once (there is no method to add an Exception to the object).

And what about creating a new AE every time and just including the previous AE in the list of exceptions? Seems a hokey way to do it.

Any better ideas?

+1  A: 

The simplest way would be to add the exceptions to a List until you were ready to throw the AggregateException.

It seems strange to me that you would want to return the old exceptions the next time you create an AggregateException, but if you kept your List around, you could just build a new AggregateException from this.

bbudge
+1  A: 

Are you talking about something like this?

var exceptions = new List<Exception>();
foreach (var item in items) {
    try {
        DoSomething(item);

    } catch (Exception ex) {
        exceptions.Add(ex);
    }
}

if (exceptions.Count > 0)
    throw new AggregateException(
        "Encountered errors while trying to do something.",
        exceptions
    );

Seems like the most logical way to me.

Dan Tao
That's how I ended up implementing it. I didn't know if there was a 'standard' way of using the AE, but this way is simple and obvious and works.
Pat