Process.Exited broken?

Hello,
Im using the following code to launch an 'attachment' from my program and attach the Exited event handler to it so i know when it has been closed. This way i can then delete the temporary file that i had to create (the attachment is a byte array until they choose to open it).

 

openedFile = new System.Diagnostics.Process();

openedFile.EnableRaisingEvents = true;

openedFile.StartInfo = new System.Diagnostics.ProcessStartInfo(tempPath);

openedFile.Exited += new EventHandler(openedFile_Exited);

openedFile.Start();

My issue is it doesn't fire all the time. If its a .txt and opens in notepad, the event fires fine. If its an .xls and opens in excel, the event is not fired. Why would this be? Is there perhaps a better way of deleting a temporary file?
Any help would be appriciated!

I am not sure, but I assume that the process created by openedFile.Start() might not be the same process that you see. Note that Office programs are single-instance applicaions; I am not sure about Office 2010 but I assume all recent versions of Office are single-instance. So when you start an Office application, the document might be sent to another instance of the application. If that happens, then if you delete the document in the Exited event then either the document won't delete (are you using try/catch?) or it will get taken away from the application before the application is finished with it. I however don't know if that explains the problem you are having.

Perhaps what is happening is that the process executes, then passes the document to another instance, then exits; all so fast that the Exited event is not executed. That is only a guess and is probably not happening, but it is a guess.

Are you sure that the Exited event does not execute, or are you assuming it is not executed just because the file does not get deleted?

1 Reply

Know the answer? Post it — somebody with the same question will find it here.

Sam Hobbs16y ago
I am not sure, but I assume that the process created by openedFile.Start() might not be the same process that you see. Note that Office programs are single-instance applicaions; I am not sure about Office 2010 but I assume all recent versions of Office are single-instance. So when you start an Office application, the document might be sent to another instance of the application. If that happens, then if you delete the document in the Exited event then either the document won't delete (are you using try/catch?) or it will get taken away from the application before the application is finished with it. I however don't know if that explains the problem you are having.

Perhaps what is happening is that the process executes, then passes the document to another instance, then exits; all so fast that the Exited event is not executed. That is only a guess and is probably not happening, but it is a guess.

Are you sure that the Exited event does not execute, or are you assuming it is not executed just because the file does not get deleted?