Dennis Doomen

I'm trying to come up with a good name for that overload. Something like `WithInnerExceptionAnywhere`. Ideally we would want to make that the default, but then you would need a...

More ideas through [this Twitter feed](https://twitter.com/ddoomen/status/1465302319420121090): * `WithNestedInnerException` * `WithDeepInnerException`

I think that's a great idea and I would prefer `WhoseInnerExceptionChain` to emphasize that that it exposes not just the direct inner exceptions.

I'm all for `WhoseInnerExceptionChain`, but I don't think we should add those two `ContainXX` methods considering how [many of those assertion methods](https://github.com/fluentassertions/fluentassertions/blob/62f0d768a802fbfe630c887afe593b7680eeffcb/Tests/Approval.Tests/ApprovedApi/FluentAssertions/netcoreapp3.0.verified.txt#L414) we already have, including `ContainItemsAssignableTo`.

Yeah, that's true. But then you need `ContainItemsOfExactType` and `ContainSingleOfExactType`.

I prefer `HaveElementsOfType`

> Or using the neat little thing called `OccurrenceConstraint` Hmm, that might not be a bad idea indeed. Wondering what @jnyrup thinks about that.

I like `WhoseInnerExceptionChain` and `WhoseNestedException` equally, but I don't like the use of `ContainItemsAssignableTo`. Not just because it doesn't read very nicely, but also because we most likely care about...

Hi @gabrielrb. Thanks for reporting. The site was in the process of becoming SSL-enabled, and I somehow screwed up the DNS settings. It should be back now.

As is documented [here](https://fluentassertions.com/introduction#subject-identification), you need to run your tests in Debug mode for FA to be able to extract the variable from the stack trace. Otherwise the compiler will...