But note that
TerminateProcess is asynchronous. So you’d have to wait on the process handle to be sure it is done.
Process.Kill() does that for your.
Process.Kill() also runs asynchronously. So you’ll have to use
WaitForExit() to wait for termination to complete – if you care.
Frankly, I wouldn’t bother. Of course there is always the (remote?) chance that some “arbitrary”
InvalidOperationExcepion bubbles up out of that line of code, that is not related to the process no longer being there or the
Process object to be in an invalid state, but in reality I think you can just go with the try/catch around the
In addition, depending on your application, you could consider logging this kill anyway, since it seems some sort of last resort measure. In that case log the actual
InvalidOperationException with it. If things go strange, you at least have your logs to check why the
Having all that said, you might also want to consider catching / handling
Win32Exception for the same reasons.