Different processes will not ensure multiple instances of your utility are safe. For example, if the thing uses a temp file and the name is hardcoded, or derived by using the system time, you will have issues.
If you do determine that multiple instances of your utility are undesirable, then the simplest way to prevent that would be to use a named mutex. ms-help://MS.VSCC/MS.MSDNVS/cpguide/html/cpconmutex.htm Keep Smilin' Ed Stegman -----Original Message----- From: dotnet discussion [mailto:[EMAIL PROTECTED]]On Behalf Of Erick Thompson Sent: Monday, May 20, 2002 7:30 PM To: [EMAIL PROTECTED] Subject: Multiple threads and external utility I have an application that uses an external process/utility (pdftotext.exe) that is normally called from a command window. I use ProcessStartInfo and Process to manage the external utility. There are multiple threads running this application. My concern is that if two thread try to use the application at the same time, there will be problems, as I don't know if the utility is thread safe. By using a process object, am I avoiding threading problems because a new process is created, so the threads will never cross? If not, what is best way to make sure that only one thread at a time is using the external utility. Thanks, Erick You can read messages from the DOTNET archive, unsubscribe from DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com. You can read messages from the DOTNET archive, unsubscribe from DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
