Problem with HasExited and WaitForExit()

danielhasdibs

For some reason, this does not work with MS Word. (at least on my computer)

danielhasdibs

If you can get it to work the other way around (hyperlink opens first, waits for the user to exit, then opens the Word document) that would work for me, too. thanks.

PIEBALDconsult

More info: Outlook uses Word as its editor so when Outlook is open, Word is running, so then the Process.Start merely passes the file to the running instance of Word and exits. Close Outlook, and try again. It worked for me that way, but I still don't have a decent workaround.

DaveyM69

After

danielhasdibs wrote:

WordProcess = System.Diagnostics.Process.Start(psi);

add

WordProcess.StandardOutput.ReadToEnd();

Works on my system (no need for the WaitForExit method call). For some reason the Exited event isn't raised but the HasExited property is correctly set. This is working...

System.Diagnostics.ProcessStartInfo psi = new System.Diagnostics.ProcessStartInfo();
psi.RedirectStandardOutput = true;
psi.WindowStyle = System.Diagnostics.ProcessWindowStyle.Maximized;
psi.UseShellExecute = false;
psi.Arguments = "Help.txt";
psi.FileName = "C:\\Program Files\\Microsoft Office\\Office12\\WINWORD.EXE";

        System.Diagnostics.Process WordProcess = new System.Diagnostics.Process();
        WordProcess.EnableRaisingEvents = true;
        WordProcess = System.Diagnostics.Process.Start(psi);
        WordProcess.StandardOutput.ReadToEnd();
        Console.WriteLine(WordProcess.HasExited);
        System.Diagnostics.Process.Start("Explorer.exe", "http://google.com");

Dave

modified on Friday, February 8, 2008 5:27 PM

Luc Pattyn

Hi, this code works fine on WinXP:

Process proc=Process.Start(@"C:\\test.doc");
log("procName="+proc.ProcessName);
proc.WaitForExit();
log("has exited");

provided no Word process is running yet (if there is, proc is null as per MSDN documentation). PS: I do not use any Office Assistant, I have thrown it out long ago. IIRC there is a small app that "helps" in launching Office components, if that were to intercept the doc extension and then launch WinWord on its own, you would not get winword in procName; you could fix that by explicitly starting winword, with the doc name as an argument tho). :)

Luc Pattyn [Forum Guidelines] [My Articles]

This month's tips: - before you ask a question here, search CodeProject, then Google; - the quality and detail of your question reflects on the effectiveness of the help you are likely to get; - use PRE tags to preserve formatting when showing multi-line code snippets.

DaveyM69

Process.WaitForExit(); and Process.StandardOutput.ReadToEnd(); seem to have the same result. Any idea why the Exited event isn't fired Luc?

Dave

modified on Friday, February 8, 2008 5:44 PM

Luc Pattyn · modified on Friday, February 8, 2008 5:44 PM

:confused: ReadToEnd() did not appear in the original post, nor in my only reply :confused:

Luc Pattyn [Forum Guidelines] [My Articles]

This month's tips: - before you ask a question here, search CodeProject, then Google; - the quality and detail of your question reflects on the effectiveness of the help you are likely to get; - use PRE tags to preserve formatting when showing multi-line code snippets.

DaveyM69

No - I was just comenting that it appears to have the same result

Dave

Guffa

danielhasdibs wrote:

WaitForExit() does nothing

Nothing ever does "nothing". What does it do? Return immediately?

danielhasdibs wrote:

System.Diagnostics.Process WordProcess = new System.Diagnostics.Process();

Why are you creating a new process here? You only throw it away in the next line where you create another new process.

danielhasdibs wrote:

WordProcess = System.Diagnostics.Process.Start(psi);

You should check the return value. If a process is reused instead or starting a new, the return value is null.

Experience is the sum of all the mistakes you have done.

engsrini

Hi Why did you give the wait for exit time as 10000 i.e WordProcess.WaitForExit(10000); if you want the first application to be closed and open the second one do like this WordProcess.WaitForExit();// wait for infinite System.Diagnostics.Process.Start(txt_websiteAddress.Text); And about HasExited property, if any of the word document is open other than the closed document, this property will not get updated. Since Word is single process which launch different instance of editor. Thanks Srini

mav northwind

Hi! I just tried this and it works as expected using this code:

// You can simply use the name of the document to open...
ProcessStartInfo psi = new ProcessStartInfo("C:\\Document.doc");
MessageBox.Show("Starting...");
Process p = Process.Start(psi);
p.WaitForExit();
MessageBox.Show("Finished");

The second message box appears as soon as I close Word. Does this help?

Regards, mav -- Black holes are the places where God divided by 0...

PIEBALDconsult

Add /n as a parameter to WinWord. http://support.microsoft.com/kb/210565[^]

danielhasdibs

Ok, I don't want to be one of those jerks who finds the answer and doesn't share so I have the working code here. I don't know why this didn't work before, but it didn't, and now it does, so I'm happy. System.Diagnostics.ProcessStartInfo psi = new System.Diagnostics.ProcessStartInfo(); psi.RedirectStandardOutput = true; psi.WindowStyle = System.Diagnostics.ProcessWindowStyle.Maximized; psi.UseShellExecute = false; psi.Arguments = txt_Wordfile.Text + " /n"; psi.FileName = WordExe; //string System.Diagnostics.Process WordProcess = new System.Diagnostics.Process(); WordProcess = System.Diagnostics.Process.Start(psi); WordProcess.EnableRaisingEvents = true; while (!WordProcess.HasExited) { ; } WordProcess.Kill(); System.Diagnostics.Process.Start(txt_website.Text); Thanks everyone for your help!

Martin 0

Hello, Just an addintional info. As the Process class implements IDisposable you should call Dispose() to free the memory. You could use an using-block for that reason. using(System.Diagnostics.Process WordProcess = new System.Diagnostics.Process()) { WordProcess = System.Diagnostics.Process.Start(psi); ... } I don't think there is a need to call the "Kill" method after "HasExited" is "true". Same with "EnableRaisingEvents", only needed if you want to handle the "Exited" event. P.S.: Strange, that WaitForExit is not working here.

All the best, Martin