[Mono-bugs] [Bug 61946][Nor] Changed - Process.Start throws wrong exception when file not found

[bugzilla-daemon at bugzilla.ximian.com]

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 at ximian.com.

http://bugzilla.ximian.com/show_bug.cgi?id=61946

--- shadow/61946	2005-05-10 21:43:15.000000000 -0400
+++ shadow/61946.tmp.32480	2005-05-29 23:03:34.000000000 -0400
@@ -1,13 +1,13 @@
 Bug#: 61946
 Product: Mono: Runtime
 Version: unspecified
 OS: unknown
 OS Details: Server 2003
-Status: NEW   
-Resolution: 
+Status: RESOLVED   
+Resolution: WONTFIX
 Severity: Unknown
 Priority: Normal
 Component: misc
 AssignedTo: gonzalo at ximian.com                            
 ReportedBy: monobugs at radeldudel.de               
 QAContact: mono-bugs at ximian.com
@@ -38,6 +38,15 @@
 How often does this happen? 
 everytime
 
 ------- Additional Comments From bmaurer at users.sf.net  2005-05-10 18:00 -------
 In bash, the exit code 127 means "process not found". We need to check
 for this in the runtime.
+
+------- Additional Comments From gonzalo at ximian.com  2005-05-29 23:03 -------
+And tcsh returns 1, and cmd.exe returns 1...
+So there's really no way I know to tell if the shell didn't find the
+file or the program executed returned that status, apart from the
+differences between shells.
+
+I'd recommend setting 'UseShellExecute' to false so that the program
+is not executed using a shell.