[Mono-bugs] [Bug 450499] New: Exited Event Not Fired When Accessing HasExited Property

bugzilla_noreply at novell.com bugzilla_noreply at novell.com
Mon Dec 1 10:16:14 EST 2008


           Summary: Exited Event Not Fired When Accessing HasExited Property
           Product: Mono: Class Libraries
           Version: 2.2.x
          Platform: 32bit
        OS/Version: Windows XP
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: System
        AssignedTo: mono-bugs at lists.ximian.com
        ReportedBy: cbutor at gmail.com
         QAContact: mono-bugs at lists.ximian.com
                CC: billholmes54 at gmail.com
          Found By: Community User

Created an attachment (id=256987)
 --> (https://bugzilla.novell.com/attachment.cgi?id=256987)
Test program to reproduce Process exited event handling on mono

When a program has been exited and the process' HasExited property is checked,
the Exited Event is not published.  Even though this may seem like an abnormal
operation, this is actually the current functionality in .NET (but does not
appear in any of .NET's documentation for the System.Diagnostics.Process
class).  If the attached test program is run on .NET with the
EnableRaisingEvents flag set to true for the process running an external
application, the exited event is received.  However, if the line setting that
flag is commented out but the HasExited property is accessed post program
exiting, the exited event is also received.  When run on any version of mono,
the first scenerio is ok - with the EnableRaisingEvents flag set to true the
exited event is observed.  However, when the flag is not set and the HasExited
property is accessed, the test program never receives the exited event.

Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.

More information about the mono-bugs mailing list