diff --git a/xml/System.Diagnostics/Process.xml b/xml/System.Diagnostics/Process.xml index 6cf57c43a53..ffc47a0e0f5 100644 --- a/xml/System.Diagnostics/Process.xml +++ b/xml/System.Diagnostics/Process.xml @@ -705,7 +705,7 @@ process.BeginOutputReadLine(); sends a request to close to the main window, which, in a well-formed application, closes child windows and revokes all running message loops for the application. The request to exit the process by calling does not force the application to quit. The application can ask for user verification before quitting, or it can refuse to quit. To force the application to quit, use the method. The behavior of is identical to that of a user closing an application's main window using the system menu. Therefore, the request to exit the process by closing the main window does not force the application to quit immediately. + When a process is executing, its message loop is in a wait state. The message loop executes every time a Windows message is sent to the process by the operating system. Calling sends a request to close the main window, which, in a well-formed application, closes child windows and revokes all running message loops for the application. The request to exit the process by calling does not force the application to quit. The application can ask for user verification before quitting, or it can refuse to quit. To force the application to quit, use the method. The behavior of is identical to that of a user closing an application's main window using the system menu. Therefore, the request to exit the process by closing the main window does not force the application to quit immediately. Data edited by the process or resources allocated to the process can be lost if you call . causes an abnormal process termination, and should be used only when necessary. enables an orderly termination of the process and closes all windows, so it is preferable for applications with an interface. If fails, you can use to terminate the process. is the only way to terminate processes that do not have graphical interfaces. @@ -2054,6 +2054,49 @@ There are problems accessing the performance counter API's used to get process i + + + To be added. + + only requests a termination. +When a process with a graphical interface is executing, its message loop is in a wait state. +The message loop executes every time a Windows message is sent to the process by the operating system. +Calling sends a request to close the main window, which, in a well-formed application, closes child windows and revokes all running message loops for the application. +The request to exit the process by calling does not force the application to quit. +The application can ask for user verification before quitting, or it can refuse to quit. +To force the application to quit, use the `Kill` method. + +The behavior of is identical to that of a user closing an application's main window using the system menu. +Therefore, the request to exit the process by closing the main window does not force the application to quit immediately. + +> [!NOTE] +> The method executes asynchronously. +> After calling the `Kill` method, call the method to wait for the process to exit, or check the property to determine if the process has exited. + +> [!NOTE] +> The method and the property do not reflect the status of descendant processes. +> When `Kill(entireProcessTree: true)` is used, and will indicate that exiting has completed after the given process exits, even if all descendants have not yet exited. + +Data edited by the process or resources allocated to the process can be lost if you call `Kill`. +`Kill` causes an abnormal process termination and should be used only when necessary. + enables an orderly termination of the process and closes all windows, so it is preferable for applications with an interface. +If fails, you can use `Kill` to terminate the process. +`Kill` is the only way to terminate processes that do not have graphical interfaces. + +You can call `Kill` and only for processes that are running on the local computer. +You cannot cause processes on remote computers to exit. You can only view information for processes running on remote computers. + +> [!NOTE] +> If the call to the `Kill` method is made while the process is currently terminating, a is thrown for Access Denied. + + ]]> + + + @@ -2086,33 +2129,12 @@ There are problems accessing the performance counter API's used to get process i Immediately stops the associated process. - - forces a termination of the process, while only requests a termination. When a process with a graphical interface is executing, its message loop is in a wait state. The message loop executes every time a Windows message is sent to the process by the operating system. Calling sends a request to close to the main window, which, in a well-formed application, closes child windows and revokes all running message loops for the application. The request to exit the process by calling does not force the application to quit. The application can ask for user verification before quitting, or it can refuse to quit. To force the application to quit, use the method. The behavior of is identical to that of a user closing an application's main window using the system menu. Therefore, the request to exit the process by closing the main window does not force the application to quit immediately. - -> [!NOTE] -> The method executes asynchronously. After calling the method, call the method to wait for the process to exit, or check the property to determine if the process has exited. - - Data edited by the process or resources allocated to the process can be lost if you call . causes an abnormal process termination and should be used only when necessary. enables an orderly termination of the process and closes all windows, so it is preferable for applications with an interface. If fails, you can use to terminate the process. is the only way to terminate processes that do not have graphical interfaces. - - You can call and only for processes that are running on the local computer. You cannot cause processes on remote computers to exit. You can only view information for processes running on remote computers. - -> [!NOTE] -> If the call to the method is made while the process is currently terminating, a is thrown for Access Denied. - - ]]> - + To be added. The associated process could not be terminated. -or- - The process is terminating. - - -or- - - The associated process is a Win16 executable. + The process is terminating. You are attempting to call for a process that is running on a remote computer. The method is available only for processes running on the local computer. The process has already exited. @@ -2150,9 +2172,29 @@ There are problems accessing the performance counter API's used to get process i - To be added. - To be added. - To be added. + to kill the associated process and its descendants; to kill only the associated process. + Immediately stops the associated process, and optionally its child/descendent processes. + When is set to , processes where the call lacks permissions to view details are silently skipped by the descendant termination process because the termination process is unable to determine whether those processes are descendants. + The associated process could not be terminated. + + -or- + + The process is terminating. + You are attempting to call for a process that is running on a remote computer. The method is available only for processes running on the local computer. + The process has already exited. + + -or- + + There is no process associated with this object. + +-or- + +The calling process is a member of the associated process' descendant tree. + Not all processes in the associated process' descendant tree could be terminated. + for full trust for the immediate caller. This member cannot be used by partially trusted code. + + + @@ -6213,4 +6255,4 @@ There is a similar issue when you read all text from both the standard output an - \ No newline at end of file +