Add documentation for Process.Kill(bool entireProcessTree) (#2828)

* Add documentation for Process.Kill(bool entireProcessTree)

* Update Process.xml

* minor fix: parm summary in single line

* Address feedback

* Address Feedback

* Fixed bad xml element

Author: wtgodbe

xml/System.Diagnostics/Process.xml

@@ -705,7 +705,7 @@ process.BeginOutputReadLine();
           <format type="text/markdown"><![CDATA[  
 
 ## Remarks  
- 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 <xref:System.Diagnostics.Process.CloseMainWindow%2A> 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 <xref:System.Diagnostics.Process.CloseMainWindow%2A> 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 <xref:System.Diagnostics.Process.Kill%2A> method. The behavior of <xref:System.Diagnostics.Process.CloseMainWindow%2A> 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 <xref:System.Diagnostics.Process.CloseMainWindow%2A> 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 <xref:System.Diagnostics.Process.CloseMainWindow%2A> 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 <xref:System.Diagnostics.Process.Kill%2A> method. The behavior of <xref:System.Diagnostics.Process.CloseMainWindow%2A> 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 <xref:System.Diagnostics.Process.Kill%2A>. <xref:System.Diagnostics.Process.Kill%2A> causes an abnormal process termination, and should be used only when necessary. <xref:System.Diagnostics.Process.CloseMainWindow%2A> enables an orderly termination of the process and closes all windows, so it is preferable for applications with an interface. If <xref:System.Diagnostics.Process.CloseMainWindow%2A> fails, you can use <xref:System.Diagnostics.Process.Kill%2A> to terminate the process. <xref:System.Diagnostics.Process.Kill%2A> 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
         <altmember cref="M:System.Diagnostics.Process.GetProcessById(System.Int32,System.String)" />
       </Docs>
     </Member>
+    <MemberGroup MemberName="Kill">
+      <Docs>
+        <summary>To be added.</summary>
+        <remarks>
+          <format type="text/markdown"><![CDATA[  
+  
+## Remarks  
+
+The `Kill` method forces a termination of the process, while <xref:System.Diagnostics.Process.CloseMainWindow%2A> 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 <xref:System.Diagnostics.Process.CloseMainWindow%2A> 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 <xref:System.Diagnostics.Process.CloseMainWindow%2A> 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 <xref:System.Diagnostics.Process.CloseMainWindow%2A> 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 <xref:System.Diagnostics.Process.Kill%2A> method executes asynchronously. 
+> After calling the `Kill` method, call the <xref:System.Diagnostics.Process.WaitForExit%2A> method to wait for the process to exit, or check the <xref:System.Diagnostics.Process.HasExited%2A> property to determine if the process has exited.
+
+> [!NOTE]
+> The <xref:System.Diagnostics.Process.WaitForExit%2A> method and the <xref:System.Diagnostics.Process.HasExited%2A> property do not reflect the status of descendant processes.
+> When `Kill(entireProcessTree: true)` is used, <xref:System.Diagnostics.Process.WaitForExit%2A> and <xref:System.Diagnostics.Process.HasExited%2A> 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.
+<xref:System.Diagnostics.Process.CloseMainWindow%2A> enables an orderly termination of the process and closes all windows, so it is preferable for applications with an interface. 
+If <xref:System.Diagnostics.Process.CloseMainWindow%2A> 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 <xref:System.Diagnostics.Process.CloseMainWindow%2A> 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 <xref:System.ComponentModel.Win32Exception> is thrown for Access Denied.
+  
+ ]]></format>
+        </remarks>        
+      </Docs>
+    </MemberGroup>    
     <Member MemberName="Kill">
       <MemberSignature Language="C#" Value="public void Kill ();" />
       <MemberSignature Language="ILAsm" Value=".method public hidebysig instance void Kill() cil managed" />
@@ -2086,33 +2129,12 @@ There are problems accessing the performance counter API's used to get process i
       <Parameters />
       <Docs>
         <summary>Immediately stops the associated process.</summary>
-        <remarks>
-          <format type="text/markdown"><![CDATA[  
-  
-## Remarks  
- <xref:System.Diagnostics.Process.Kill%2A> forces a termination of the process, while <xref:System.Diagnostics.Process.CloseMainWindow%2A> 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 <xref:System.Diagnostics.Process.CloseMainWindow%2A> 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 <xref:System.Diagnostics.Process.CloseMainWindow%2A> 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 <xref:System.Diagnostics.Process.Kill%2A> method. The behavior of <xref:System.Diagnostics.Process.CloseMainWindow%2A> 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 <xref:System.Diagnostics.Process.Kill%2A> method executes asynchronously. After calling the <xref:System.Diagnostics.Process.Kill%2A> method, call the <xref:System.Diagnostics.Process.WaitForExit%2A> method to wait for the process to exit, or check the <xref:System.Diagnostics.Process.HasExited%2A> 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 <xref:System.Diagnostics.Process.Kill%2A>. <xref:System.Diagnostics.Process.Kill%2A> causes an abnormal process termination and should be used only when necessary. <xref:System.Diagnostics.Process.CloseMainWindow%2A> enables an orderly termination of the process and closes all windows, so it is preferable for applications with an interface. If <xref:System.Diagnostics.Process.CloseMainWindow%2A> fails, you can use <xref:System.Diagnostics.Process.Kill%2A> to terminate the process. <xref:System.Diagnostics.Process.Kill%2A> is the only way to terminate processes that do not have graphical interfaces.  
-  
- You can call <xref:System.Diagnostics.Process.Kill%2A> and <xref:System.Diagnostics.Process.CloseMainWindow%2A> 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 <xref:System.Diagnostics.Process.Kill%2A> method is made while the process is currently terminating, a <xref:System.ComponentModel.Win32Exception> is thrown for Access Denied.  
-  
- ]]></format>
-        </remarks>
+        <remarks>To be added.</remarks>
         <exception cref="T:System.ComponentModel.Win32Exception">The associated process could not be terminated.  
 
  -or-  
 
- The process is terminating.  
-  
- -or-  
-  
- The associated process is a Win16 executable.</exception>
+ The process is terminating.</exception>
         <exception cref="T:System.NotSupportedException">You are attempting to call <see cref="M:System.Diagnostics.Process.Kill" /> for a process that is running on a remote computer. The method is available only for processes running on the local computer.</exception>
         <exception cref="T:System.InvalidOperationException">The process has already exited.  
 
@@ -2150,9 +2172,29 @@ There are problems accessing the performance counter API's used to get process i
         <Parameter Name="entireProcessTree" Type="System.Boolean" Index="0" FrameworkAlternate="netcore-3.0" />
       </Parameters>
       <Docs>
-        <param name="entireProcessTree">To be added.</param>
-        <summary>To be added.</summary>
-        <remarks>To be added.</remarks>
+        <param name="entireProcessTree"><see langword="true" /> to kill the associated process and its descendants; <see langword="false" /> to kill only the associated process.</param>
+        <summary>Immediately stops the associated process, and optionally its child/descendent processes.</summary>
+        <remarks>When <paramref name="entireProcessTree" /> is set to <see langword="true" />, 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.</remarks>
+        <exception cref="T:System.ComponentModel.Win32Exception">The associated process could not be terminated.  
+  
+ -or-  
+  
+ The process is terminating.</exception>
+        <exception cref="T:System.NotSupportedException">You are attempting to call <see cref="M:System.Diagnostics.Process.Kill" /> for a process that is running on a remote computer. The method is available only for processes running on the local computer.</exception>
+        <exception cref="T:System.InvalidOperationException">The process has already exited.  
+  
+ -or-  
+  
+ There is no process associated with this <see cref="T:System.Diagnostics.Process" /> object.
+
+-or-
+
+The calling process is a member of the associated process' descendant tree.</exception>
+        <exception cref="T:System.AggregateException">Not all processes in the associated process' descendant tree could be terminated.</exception>
+        <permission cref="F:System.Security.Permissions.SecurityAction.LinkDemand">for full trust for the immediate caller. This member cannot be used by partially trusted code.</permission>
+        <altmember cref="M:System.Environment.Exit(System.Int32)" />
+        <altmember cref="M:System.Diagnostics.Process.CloseMainWindow" />
+        <altmember cref="M:System.Diagnostics.Process.Start" />
       </Docs>
     </Member>
     <Member MemberName="LeaveDebugMode">
@@ -6213,4 +6255,4 @@ There is a similar issue when you read all text from both the standard output an
       </Docs>
     </Member>
   </Members>
-</Type>
+</Type>