title: Has anybody faced with cases, when AggregateException.InnerExceptions.Count > 1?
body: <p>I'm wondering, has anybody faced with cases, when <code>AggregateException.InnerExceptions.Count</code> > 1?</p>
  
  <p>E.g., TPL wraps exception, that was raised in task body, in <code>AggregateException</code>. But I never saw situations, when there was more than one inner exception.</p>
  
  <p>How this can be achieved with TPL?<br>
  How this can be achieved with <em>any</em> FCL (or another widely used library) classes (samples will be useful)? </p>
  
  <p>I know, that there's <em>possibility</em> to build such instance of <code>AggregateException</code>, but the question is about a practice. I'm asking about this, because I want to understand, what is the best way to handle <code>AggregateException</code>.</p>