Clarify Process.HasExited and that it raises Exited #8379
Conversation
The existing description implied that the Exited event could be raised "before" the user calls HasExited. This wasn't very clear in my opinion - so I've suggested a tweak to make it more explicit by revealing that the HasExited property accessor itself has a side-effect; invoking HasExited if the process has exited.
ghost
added
community-contribution
|
Tagging subscribers to this area: @dotnet/area-system-diagnostics-process Issue DetailsSummaryThe existing description implied that the Exited event could be raised "before" the user calls HasExited. This wasn't very clear in my opinion - so I've suggested a tweak to make it more explicit by revealing that the HasExited property accessor itself has a side-effect; invoking HasExited if the process has exited.
|
kierenj
changed the title
|
Docs Build status updates of commit 1af1cb4: ✅ Validation status: passed
For more details, please refer to the build report. Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report. For any questions, please:
|
|
Learn Build status updates of commit bb90361: ✅ Validation status: passed
For more details, please refer to the build report. Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report. For any questions, please:
|
4 participants
Summary
The existing description implied that the Exited event could be raised "before" the user calls HasExited. This wasn't very clear in my opinion - so I've suggested a tweak to make it more explicit by revealing that the HasExited property accessor itself has a side-effect; invoking HasExited if the process has exited.