Robustly detecting an error when starting an app via code

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Simon - 04 Sep 2007 20:26 GMT

Hi everyone,

Can anyone tell me if there is a standard way of detecting an error in a
process that I've started using the .net framework's
System.Diagnostics.Process class?

I need to regularly call a secondary application but be able to tell if
a problem has occured with it and log the error (and then probably
restart it)

Can anyone tell me how to detect the error in the running process?

Thanks to anyone who can advise

Best regards

Simon

Reply to this Message

Nicholas Paldino [.NET/C# MVP] - 04 Sep 2007 20:41 GMT

Simon,

You can't do this in a generic manner. If anything, you have to have
knowledge of the process and how to retrieve any error that occurs in the
process. The only generic way of handling an error is to use the ExitCode
property on the Process class, but even then, the return values are specific
to the application being run.

Signature

- Nicholas Paldino [.NET/C# MVP]
- mvp@spam.guard.caspershouse.com

> Hi everyone,
>
[quoted text clipped - 13 lines]
>
> Simon

Reply to this Message

Ben Voigt [C++ MVP] - 05 Sep 2007 00:55 GMT

> Simon,
>
[quoted text clipped - 3 lines]
> property on the Process class, but even then, the return values are
> specific to the application being run.

In addition to the exit code, you can capture output from a console
application, or some programs can be configured to write a log. Another
option might be to start the process under OS debug and capture
OutputDebugString calls (that's what .NET's TraceListener uses to send
messages by default).

>> Hi everyone,
>>
[quoted text clipped - 13 lines]
>>
>> Simon

Reply to this Message

Simon - 08 Sep 2007 18:01 GMT

Thanks guys - very much appreciated

Reply to this Message

Rate this thread:

Robustly detecting an error when starting an app via code

Free Magazines