http://ayende.comAyende @ RahienCopyright (C) Ayende Rahien 2004 - 2021 (c) 202660Justin, Users see that all the time, that is the error that is thrown in VS. To find the real details, you have to dig deep, that isn't a nice thing to do to people http://ayende.com/87041/rant-who-thought-this-was-a-good-idea#comment11http://ayende.com/87041/rant-who-thought-this-was-a-good-idea#comment11Fri, 09 Sep 2011 08:44:18 GMTAyende, It seems like .ToString() will print out all of the aggregated exceptions still, so it should work with loggers fine (unless you have some type of custom formatter that does more than just ToString()'s the exception). It's only in the debugger that you'll see this issue. The message should say "One or more errors occurred." Which is sort of redundant considering the name of the Exception.http://ayende.com/87041/rant-who-thought-this-was-a-good-idea#comment10http://ayende.com/87041/rant-who-thought-this-was-a-good-idea#comment10Thu, 08 Sep 2011 19:57:50 GMTJustin, I would state that if your class need special handling, separate from all other classes of the same type, your class is brokenhttp://ayende.com/87041/rant-who-thought-this-was-a-good-idea#comment9http://ayende.com/87041/rant-who-thought-this-was-a-good-idea#comment9Thu, 08 Sep 2011 19:45:28 GMTYour error logger would have to special case AggregateExceptions, that is a pain in the ass that's true.http://ayende.com/87041/rant-who-thought-this-was-a-good-idea#comment8http://ayende.com/87041/rant-who-thought-this-was-a-good-idea#comment8Thu, 08 Sep 2011 18:34:21 GMTJustin, That assumes that I actually have the debugger there. And that is is responding. What about log messages, users errors, emails to the mailing list, all of which show that error.http://ayende.com/87041/rant-who-thought-this-was-a-good-idea#comment7http://ayende.com/87041/rant-who-thought-this-was-a-good-idea#comment7Thu, 08 Sep 2011 16:52:03 GMTClick the "View Detail" link and it will show you the exceptions it has aggregated.http://ayende.com/87041/rant-who-thought-this-was-a-good-idea#comment6http://ayende.com/87041/rant-who-thought-this-was-a-good-idea#comment6Thu, 08 Sep 2011 16:41:03 GMTJustin, It _could_ show me the exceptions that it had internally. In 99% of the cases, it only have a single exception, anywayhttp://ayende.com/87041/rant-who-thought-this-was-a-good-idea#comment5http://ayende.com/87041/rant-who-thought-this-was-a-good-idea#comment5Thu, 08 Sep 2011 16:27:40 GMTIt's an aggregate exception, which couldn't have a useful message anyway. You have to go look into the exceptions that it has aggregated to get the useful messages. It's a property, just expand it.http://ayende.com/87041/rant-who-thought-this-was-a-good-idea#comment4http://ayende.com/87041/rant-who-thought-this-was-a-good-idea#comment4Thu, 08 Sep 2011 15:57:42 GMTWell at least it allows you to programmatically determine what the exact cause was ;-) Curiously this is not the case for most exceptions. Especially IOException gives you about nothing to which you can react programmatically. There are not error codes.http://ayende.com/87041/rant-who-thought-this-was-a-good-idea#comment3http://ayende.com/87041/rant-who-thought-this-was-a-good-idea#comment3Thu, 08 Sep 2011 13:54:30 GMTCould be worse. The Secure Store Service API in SharePoint 2010 likes to throw exceptions that are declared internal.http://ayende.com/87041/rant-who-thought-this-was-a-good-idea#comment2http://ayende.com/87041/rant-who-thought-this-was-a-good-idea#comment2Thu, 08 Sep 2011 13:16:06 GMTLooks like someone used the resource file key instead of the value ;) http://ayende.com/87041/rant-who-thought-this-was-a-good-idea#comment1http://ayende.com/87041/rant-who-thought-this-was-a-good-idea#comment1Thu, 08 Sep 2011 09:26:39 GMT