[Mono-bugs] [Bug 80019][Nor] New - Process.BeginOutputReadline() causes exception

[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 mgolisch at tuxhost.de.

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

--- shadow/80019	2006-11-23 09:08:47.000000000 -0500
+++ shadow/80019.tmp.29620	2006-11-23 09:08:47.000000000 -0500
@@ -0,0 +1,47 @@
+Bug#: 80019
+Product: Mono: Class Libraries
+Version: 1.2
+OS: other
+OS Details: gentoo linux,ubuntu edgy
+Status: NEW   
+Resolution: 
+Severity: 
+Priority: Normal
+Component: System
+AssignedTo: mono-bugs at ximian.com                            
+ReportedBy: mgolisch at tuxhost.de               
+QAContact: mono-bugs at ximian.com
+TargetMilestone: ---
+URL: 
+Cc: 
+Summary: Process.BeginOutputReadline() causes exception
+
+Description of Problem:
+a call to Process.BeginOutputReadline() causes an invalid operation exception.
+
+Steps to reproduce the problem:
+1. Create a ProcessStartInfo object and assign needed values to it.
+2. do Process.Start(psi); and then assign an eventhanlder to the
+outputdatarecieved event and call beginoutputreadline()
+
+Actual Results:
+Unhandled Exception: System.InvalidOperationException: Standard output has
+not been redirected or process has not been started.
+  at System.Diagnostics.Process.BeginOutputReadLine () [0x00000]
+  at (wrapper remoting-invoke-with-check)
+System.Diagnostics.Process:BeginOutputReadLine ()
+  at process.Program.Main (System.String[] args) [0x00000]
+
+
+Expected Results:
+get data of new lines in the outputbuffer send to my eventhandler method
+
+How often does this happen? 
+everytime
+
+Additional Information:
+i know that the process started cause i can see its output on the terminal
+and i checked that it didnt exit before i call Beginoutputreadline.
+But if i create the Process object by hand and dont use a seperate
+ProcessStartInfo object and register the eventhandler bevore i call
+proc.Start() it seems to work well.