Are you using Windows or Linux? As I understand UseShellExecute, when set to "false", Process.Start() will treat the filename as a binary image and attempt to execute it directly. This is really the only option that makes sense under "vanilla" Unix.
On Windows, when UseShellExecute == true, it causes Windows to use the "windows shell" to process the filename. If the filename is a document, Windows will attempt to use an appropriate application to open the document. GNOME and KDE both provide mechanisms equivalent to the Windows Shell from what I understand, but whether to use these or not (and how to choose which one if both are present) seems unclear. Rotor under Linux simply throws an exception if UseShellExecute == true. On Sunday 04 April 2004 12:06 pm, Ivan GuÅvinec wrote: > Hi, > > I stumbled upon then same problem in my project after upgrading to Mono > 0.31. > The workaround with "UseShellExecute = false" works, but I have noticed > a considerable performance penalty. So I wonder: > 1. Is the fact that arguments are not used without UseShellExecute a bug > in Mono 0.31 release? > 2. Is using UseShellExecute = false slower in comparison to > UseShellExecute = true? _______________________________________________ Mono-list maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/mono-list