Click here to Skip to main content
15,867,704 members

Comments by Nigel Mackay (Top 4 by date)

Nigel Mackay 29-Jun-11 8:28am View    
Works fine, after adding UseShellExecute=false and changing ProcessWindowStyle.Minimized to CreateNoWindow=true. It ignored the windowminimized.
Nigel Mackay 29-Jun-11 5:36am View    
Mmmm, makes sense. Instead of my app waiting for the worker to finishe, the worker just gets on with the job until finished or cancelled. And modifying the existing code is mostly a question of just moving it around into the correct procedures. I can also make my app respond to the progress reports and move file names from the waiting-list to the done-list.
Much appreciated.
Nigel Mackay 29-Jun-11 5:25am View    
Yes, I am going to have to try an alternative approach. The problem is the the called process processes a file, with a different filename for output. So I add a prefix to the outfile, then when processing is finished I delete the source file and rename the outfile. Can't do this until the external process is finished. In fact, can't go on to the next file until it is finished the current one. So I have to sit there waiting for it to finishe. It is not a case of going on with other things in the meantime. I am going to have to implement some sort of queuing system for a separate thread.
Nigel Mackay 29-Jun-11 5:00am View    
Will give it a go. BackgroundWorker is just a lot easier to use.