Question

I want to know, is there the possibility to ask Unity "do not wrap any user exceptions at resolve time"?

确实,为什么团结为“解放阵线”作总结? 正在改变“建筑服务合同”,IMHO利用团结进行初始化的目标这一事实应当透明,这意味着如果客户等待“新”运营商的IOException,那么即便是使用团结制造物体,也应当使其失效。

其他IoC集装箱是否也一样?

Answer 1

因为。

我知道,这并不是一个完全满意的答案,但我不知道你可以在团结中放弃这一行为——我还要。同意它作出奇怪的设计决定......

However, if you keep your constructors simple, you will not have that problem.

Answer 2

见 ResolutionFailedException.InnerException。

正在改变“建筑服务合同”

什么合同?

IMHO the fact of objects initialization using unity should be transparent

IoC集装箱的一个点是使物体的构造减少重点,从而使开发商能够侧重于增加商业价值。

这意味着,如果客户等待“新”运营商的IOException,那么即使使用团结方式,也应当使其失效。

谁,客户使用希望<代码>IOException的集装箱? 我认为你可能误用你的IoC集装箱。

Answer 3

理由统一归纳了合同方面的所有例外,即确定方法的合同。

在决意消失时,什么申请应当赶上? 支持者确实解决了你知道的那类人扔下了IOException。因此,你在下决心呼吁下对这一例外作出追索。

然后,执行工作发生变化。或只是组合。如今,这些服务会带来其他东西。

Now you ve got a configuration change that will require a code change. Not good.

A second reason that with the wrapped exception the container has a place to put diagnostic information about where in the resolve process the failure occurred.

Answer 4

I had a similar need and found a solution here: catch all unhandled exceptions in ASP.NET Web Api

Here s what I learned when reviewing answers from the linked article:

If you only want to catch the exceptions and log them, then add an IExceptionLogger.
If you want to catch the exception and manipulate the response, then replace IExceptionHandler.
Neither solution captures ALL exceptions. I m still using Application_Error to capture exceptions that aren t caught within my ApiController methods.

友情链接