DryIoc Exeption in a Contructor of a Dependecy does tunnel through Resolve call

[jogibear9988]

We have a Dependecy wich throws a Exceptin in a constructor.

On a other Place, we use the Container to Resolve a Interface wich has the failing class as Parameter.

there we get this exception after a Timeout:

Is it possible to configure DryIoc to fail directly with the first exception?

[dadhi]

Could you provide a small repro/illustrating test?

[jogibear9988]

My first minimal example does work as it should: https://dotnetfiddle.net/TNKroS
I now look whats different in our code.

[jogibear9988]

I now found it. The first call raises the exception, the second one throws this error:

https://dotnetfiddle.net/N2GdDR

[jogibear9988]

maybe it's possible to store the exception and rethrow it? is that allowed?

[dadhi]

@jogibear9988 Looking...

[jogibear9988]

https://dotnetfiddle.net/nudfxA
So seems a rethrow is allowed or works.
So maybe you could store the Exception when a Singelton could not be created, and rethrow when it's resolved again.