[Mono-bugs] [Bug 55790][Maj] Changed - Can't pass arguments to a new process (Process.StartInfo.Arguments)

bugzilla-daemon@bugzilla.ximian.com bugzilla-daemon@bugzilla.ximian.com
Fri, 19 Mar 2004 01:03:37 -0500 (EST)

Please do not reply to this email- if you want to comment on the bug, go to the
URL shown below and enter your comments there.

Changed by gonzalo@ximian.com.


--- shadow/55790	2004-03-18 23:28:05.000000000 -0500
+++ shadow/55790.tmp.3329	2004-03-19 01:03:37.000000000 -0500
@@ -1,14 +1,14 @@
 Bug#: 55790
 Product: Mono: Class Libraries
 Version: unspecified
+OS: unknown
 OS Details: 
-Status: NEW   
+Status: RESOLVED   
+Resolution: FIXED
+Severity: Unknown
 Priority: Major
 Component: CORLIB
 AssignedTo: mono-bugs@ximian.com                            
 ReportedBy: umbrook0@cs.umanitoba.ca               
 QAContact: mono-bugs@ximian.com
 TargetMilestone: ---
@@ -58,6 +58,21 @@
 If you substitute something like /usr/bin/man for /bin/echo, you can see
 that the program is executed, but with no arguments (i.e. it will print an
 error message "What manual page do you want?").
 There's nothing particular about "Hello, world.": using "Hello" with no
 space and no comma causes the same problem.
+------- Additional Comments From gonzalo@ximian.com  2004-03-19 01:03 -------
+Since a few days ago, we honor the UseShellExecute value which means
+that if you don't set it to false, the command is run under *nix as:
+$SHELL -c program args
+and under windows as:
+$COMSPEC /c program args
+Under windows it's not needed, but in *nix we have to quote the
+program and arguments like: $SHELL -c 'program args'.
+This is fixed in CVS. As a workaround if you don't want to update to
+CVS, set process.StartInfo.UseShellExecute to false.