Geek asks and answers

Is there a way to “handle” Environment.FailFast?

Thus, our application has a beautiful central exception handler in which information about exceptions is logged, common windows are displayed for users, and shutdown is beautifully elegant. However, we now have a third-party component that from time to time (and potentially for well-founded reasons) calls Environment.FailFast. This removes our application from the water and looks terrible for our users. Is there a way to handle Environment.FailFast in an elegant way?

+3
source share
2 answers

I don’t see a way, according to various entries in MSDN, this is a complicated process termination. Any code that you create for processing will be in this process. It also does not run final blocks or any finalizers awaiting completion, so I assume that it will not provide any events or intercepts to allow the execution of custom code. In some ways this makes sense, otherwise it may not work “quickly”, and it claims to be used only in cases of extreme damage to the process.

http://msdn.microsoft.com/en-us/library/dd289241

I see two three parameters:

  • Send a request to the seller to change the code and delete this call.
  • Find a new supplier.
  • @RB. DLL , . , , " ". , 1 2!

MSDN:

- try/finally .

FailFast Windows , , . Microsoft.

FailFast Exit, , try/finally .

+4

.

, Process.Start.

, , FailFast. , -2146232797...

+2

More articles:


All Articles