<Type Name="Process" FullName="System.Diagnostics.Process">

<TypeSignature Language="C#" Value="public class Process : System.ComponentModel.Component, IDisposable" FrameworkAlternate="net-10.0;net-11.0;net-5.0;net-6.0;net-7.0;net-8.0;net-9.0" />

<TypeSignature Language="ILAsm" Value=".class public auto ansi beforefieldinit Process extends System.ComponentModel.Component implements class System.IDisposable" FrameworkAlternate="net-10.0;net-11.0;net-5.0;net-6.0;net-7.0;net-8.0;net-9.0" />

<TypeSignature Language="DocId" Value="T:System.Diagnostics.Process" />

<TypeSignature Language="VB.NET" Value="Public Class Process&#xA;Inherits Component&#xA;Implements IDisposable" FrameworkAlternate="net-10.0;net-11.0;net-5.0;net-6.0;net-7.0;net-8.0;net-9.0" />

<TypeSignature Language="F#" Value="type Process = class&#xA; inherit Component&#xA; interface IDisposable" FrameworkAlternate="net-10.0;net-11.0;net-5.0;net-6.0;net-7.0;net-8.0;net-9.0" />

<TypeSignature Language="C++ CLI" Value="public ref class Process : System::ComponentModel::Component, IDisposable" FrameworkAlternate="net-10.0;net-11.0;net-5.0;net-6.0;net-7.0;net-8.0;net-9.0" />

<TypeSignature Language="C#" Value="public class Process : IDisposable" FrameworkAlternate="netcore-1.0;netcore-1.1" />

<TypeSignature Language="ILAsm" Value=".class public auto ansi beforefieldinit Process extends System.Object implements class System.IDisposable" FrameworkAlternate="netcore-1.0;netcore-1.1" />

<TypeSignature Language="VB.NET" Value="Public Class Process&#xA;Implements IDisposable" FrameworkAlternate="netcore-1.0;netcore-1.1" />

<TypeSignature Language="F#" Value="type Process = class&#xA; interface IDisposable" FrameworkAlternate="netcore-1.0;netcore-1.1" />

<TypeSignature Language="C++ CLI" Value="public ref class Process : IDisposable" FrameworkAlternate="netcore-1.0;netcore-1.1" />

<TypeSignature Language="C#" Value="public class Process : System.ComponentModel.Component" FrameworkAlternate="netcore-2.0;netcore-2.1;netcore-2.2;netcore-3.0;netcore-3.1;netframework-1.1;netframework-2.0;netframework-3.0;netframework-3.5;netframework-4.0;netframework-4.5;netframework-4.5.1;netframework-4.5.2;netframework-4.6;netframework-4.6.1;netframework-4.6.2;netframework-4.7;netframework-4.7.1;netframework-4.7.2;netframework-4.8;netframework-4.8.1;netstandard-2.0;netstandard-2.1" />

<TypeSignature Language="ILAsm" Value=".class public auto ansi beforefieldinit Process extends System.ComponentModel.Component" FrameworkAlternate="netcore-2.0;netcore-2.1;netcore-2.2;netcore-3.0;netcore-3.1;netframework-1.1;netframework-2.0;netframework-3.0;netframework-3.5;netframework-4.0;netframework-4.5;netframework-4.5.1;netframework-4.5.2;netframework-4.6;netframework-4.6.1;netframework-4.6.2;netframework-4.7;netframework-4.7.1;netframework-4.7.2;netframework-4.8;netframework-4.8.1;netstandard-2.0;netstandard-2.1" />

<TypeSignature Language="VB.NET" Value="Public Class Process&#xA;Inherits Component" FrameworkAlternate="netcore-2.0;netcore-2.1;netcore-2.2;netcore-3.0;netcore-3.1;netframework-1.1;netframework-2.0;netframework-3.0;netframework-3.5;netframework-4.0;netframework-4.5;netframework-4.5.1;netframework-4.5.2;netframework-4.6;netframework-4.6.1;netframework-4.6.2;netframework-4.7;netframework-4.7.1;netframework-4.7.2;netframework-4.8;netframework-4.8.1;netstandard-2.0;netstandard-2.1" />

<TypeSignature Language="F#" Value="type Process = class&#xA; inherit Component" FrameworkAlternate="netcore-2.0;netcore-2.1;netcore-2.2;netcore-3.0;netcore-3.1;netframework-1.1;netframework-2.0;netframework-3.0;netframework-3.5;netframework-4.0;netframework-4.5;netframework-4.5.1;netframework-4.5.2;netframework-4.6;netframework-4.6.1;netframework-4.6.2;netframework-4.7;netframework-4.7.1;netframework-4.7.2;netframework-4.8;netframework-4.8.1;netstandard-2.0;netstandard-2.1" />

<TypeSignature Language="C++ CLI" Value="public ref class Process : System::ComponentModel::Component" FrameworkAlternate="netcore-2.0;netcore-2.1;netcore-2.2;netcore-3.0;netcore-3.1;netframework-1.1;netframework-2.0;netframework-3.0;netframework-3.5;netframework-4.0;netframework-4.5;netframework-4.5.1;netframework-4.5.2;netframework-4.6;netframework-4.6.1;netframework-4.6.2;netframework-4.7;netframework-4.7.1;netframework-4.7.2;netframework-4.8;netframework-4.8.1;netstandard-2.0;netstandard-2.1" />

<AssemblyInfo>

<AssemblyName>System.Diagnostics.Process</AssemblyName>

<AssemblyVersion>4.1.0.0</AssemblyVersion>

<AssemblyVersion>4.2.0.0</AssemblyVersion>

<AssemblyVersion>4.2.1.0</AssemblyVersion>

<AssemblyVersion>4.2.2.0</AssemblyVersion>

<AssemblyVersion>5.0.0.0</AssemblyVersion>

<AssemblyVersion>6.0.0.0</AssemblyVersion>

<AssemblyVersion>7.0.0.0</AssemblyVersion>

<AssemblyVersion>8.0.0.0</AssemblyVersion>

<AssemblyVersion>9.0.0.0</AssemblyVersion>

<AssemblyVersion>10.0.0.0</AssemblyVersion>

<AssemblyVersion>11.0.0.0</AssemblyVersion>

</AssemblyInfo>

<AssemblyInfo>

<AssemblyName>System</AssemblyName>

<AssemblyVersion>1.0.5000.0</AssemblyVersion>

<AssemblyVersion>2.0.0.0</AssemblyVersion>

<AssemblyVersion>2.0.5.0</AssemblyVersion>

<AssemblyVersion>4.0.0.0</AssemblyVersion>

</AssemblyInfo>

<AssemblyInfo>

<AssemblyName>netstandard</AssemblyName>

<AssemblyVersion>2.0.0.0</AssemblyVersion>

<AssemblyVersion>2.1.0.0</AssemblyVersion>

</AssemblyInfo>

<TypeForwardingChain>

<TypeForwarding From="netstandard" FromVersion="2.1.0.0" To="System.Diagnostics.Process" ToVersion="10.0.0.0" FrameworkAlternate="net-10.0" />

<TypeForwarding From="netstandard" FromVersion="2.1.0.0" To="System.Diagnostics.Process" ToVersion="11.0.0.0" FrameworkAlternate="net-11.0" />

<TypeForwarding From="netstandard" FromVersion="2.1.0.0" To="System.Diagnostics.Process" ToVersion="5.0.0.0" FrameworkAlternate="net-5.0" />

<TypeForwarding From="netstandard" FromVersion="2.1.0.0" To="System.Diagnostics.Process" ToVersion="6.0.0.0" FrameworkAlternate="net-6.0" />

<TypeForwarding From="netstandard" FromVersion="2.1.0.0" To="System.Diagnostics.Process" ToVersion="7.0.0.0" FrameworkAlternate="net-7.0" />

<TypeForwarding From="netstandard" FromVersion="2.1.0.0" To="System.Diagnostics.Process" ToVersion="8.0.0.0" FrameworkAlternate="net-8.0" />

<TypeForwarding From="netstandard" FromVersion="2.1.0.0" To="System.Diagnostics.Process" ToVersion="9.0.0.0" FrameworkAlternate="net-9.0" />

</TypeForwardingChain>

<Base>

<BaseTypeName>System.ComponentModel.Component</BaseTypeName>

<BaseTypeName FrameworkAlternate="netcore-1.0;netcore-1.1">System.Object</BaseTypeName>

</Base>

<Interfaces>

<Interface FrameworkAlternate="net-10.0;net-11.0;net-5.0;net-6.0;net-7.0;net-8.0;net-9.0;netcore-1.0;netcore-1.1">

<InterfaceName>System.IDisposable</InterfaceName>

</Interface>

</Interfaces>

<Attributes>

<Attribute FrameworkAlternate="net-10.0;net-11.0;net-5.0;net-6.0;net-7.0;net-8.0;net-9.0;netframework-4.0;netframework-4.5;netframework-4.5.1;netframework-4.5.2;netframework-4.6;netframework-4.6.1;netframework-4.6.2;netframework-4.7;netframework-4.7.1;netframework-4.7.2;netframework-4.8;netframework-4.8.1">

<AttributeName Language="C#">[System.ComponentModel.Designer("System.Diagnostics.Design.ProcessDesigner, System.Design, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a")]</AttributeName>

<AttributeName Language="F#">[&lt;System.ComponentModel.Designer("System.Diagnostics.Design.ProcessDesigner, System.Design, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a")&gt;]</AttributeName>

</Attribute>

<Attribute FrameworkAlternate="net-10.0;net-11.0;net-8.0;net-9.0">

<AttributeName Language="C#">[System.Runtime.CompilerServices.Nullable(0)]</AttributeName>

<AttributeName Language="F#">[&lt;System.Runtime.CompilerServices.Nullable(0)&gt;]</AttributeName>

</Attribute>

<Attribute FrameworkAlternate="netframework-1.1;netframework-2.0;netframework-3.0;netframework-3.5;netframework-4.0;netframework-4.5;netframework-4.5.1;netframework-4.5.2;netframework-4.6;netframework-4.6.1;netframework-4.6.2;netframework-4.7;netframework-4.7.1;netframework-4.7.2;netframework-4.8;netframework-4.8.1;netstandard-2.0;netstandard-2.1">

<AttributeName Language="C#">[System.ComponentModel.DefaultEvent("Exited")]</AttributeName>

<AttributeName Language="F#">[&lt;System.ComponentModel.DefaultEvent("Exited")&gt;]</AttributeName>

</Attribute>

<Attribute FrameworkAlternate="netframework-1.1;netframework-2.0;netframework-3.0;netframework-3.5;netframework-4.0;netframework-4.5;netframework-4.5.1;netframework-4.5.2;netframework-4.6;netframework-4.6.1;netframework-4.6.2;netframework-4.7;netframework-4.7.1;netframework-4.7.2;netframework-4.8;netframework-4.8.1;netstandard-2.0;netstandard-2.1">

<AttributeName Language="C#">[System.ComponentModel.DefaultProperty("StartInfo")]</AttributeName>

<AttributeName Language="F#">[&lt;System.ComponentModel.DefaultProperty("StartInfo")&gt;]</AttributeName>

</Attribute>

<Attribute FrameworkAlternate="netframework-1.1">

<AttributeName Language="C#">[System.ComponentModel.Designer("System.Diagnostics.Design.ProcessDesigner, System.Design, Version=1.0.5000.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a")]</AttributeName>

<AttributeName Language="F#">[&lt;System.ComponentModel.Designer("System.Diagnostics.Design.ProcessDesigner, System.Design, Version=1.0.5000.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a")&gt;]</AttributeName>

</Attribute>

<Attribute FrameworkAlternate="netframework-2.0;netframework-3.0;netframework-3.5">

<AttributeName Language="C#">[System.ComponentModel.Designer("System.Diagnostics.Design.ProcessDesigner, System.Design, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a")]</AttributeName>

<AttributeName Language="F#">[&lt;System.ComponentModel.Designer("System.Diagnostics.Design.ProcessDesigner, System.Design, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a")&gt;]</AttributeName>

</Attribute>

<Attribute FrameworkAlternate="netframework-2.0;netframework-3.0;netframework-3.5;netframework-4.0;netframework-4.5;netframework-4.5.1;netframework-4.5.2;netframework-4.6;netframework-4.6.1;netframework-4.6.2;netframework-4.7;netframework-4.7.1;netframework-4.7.2;netframework-4.8;netframework-4.8.1">

<AttributeName Language="C#">[System.Diagnostics.MonitoringDescription("ProcessDesc")]</AttributeName>

<AttributeName Language="F#">[&lt;System.Diagnostics.MonitoringDescription("ProcessDesc")&gt;]</AttributeName>

</Attribute>

</Attributes>

<Docs>

<summary>Provides access to local and remote processes and enables you to start and stop local system processes.</summary>

<remarks>

<format type="text/markdown"><![CDATA[

## Remarks

A <xref:System.Diagnostics.Process> component provides access to a process that is running on a computer. A process, in the simplest terms, is a running app. A thread is the basic unit to which the operating system allocates processor time. A thread can execute any part of the code of the process, including parts currently being executed by another thread.

The <xref:System.Diagnostics.Process> component is a useful tool for starting, stopping, controlling, and monitoring apps. You can use the <xref:System.Diagnostics.Process> component, to obtain a list of the processes that are running, or you can start a new process. A <xref:System.Diagnostics.Process> component is used to access system processes. After a <xref:System.Diagnostics.Process> component has been initialized, it can be used to obtain information about the running process. Such information includes the set of threads, the loaded modules (.dll and .exe files), and performance information such as the amount of memory the process is using.

This type implements the <xref:System.IDisposable> interface. When you have finished using the type, you should dispose of it either directly or indirectly. To dispose of the type directly, call its <xref:System.IDisposable.Dispose%2A> method in a `try`/`finally` block. To dispose of it indirectly, use a language construct such as `using` (in C#) or `Using` (in Visual Basic). For more information, see the "Using an Object that Implements IDisposable" section in the <xref:System.IDisposable> interface documentation.

[!INCLUDE [untrusted-data-class-note](~/includes/untrusted-data-class-note.md)]

> [!NOTE]

> 32-bit processes cannot access the modules of a 64-bit process. If you try to get information about a 64-bit process from a 32-bit process, you will get a <xref:System.ComponentModel.Win32Exception> exception. A 64-bit process, on the other hand, can access the modules of a 32-bit process.

The process component obtains information about a group of properties all at once. After the <xref:System.Diagnostics.Process> component has obtained information about one member of any group, it will cache the values for the other properties in that group and not obtain new information about the other members of the group until you call the <xref:System.Diagnostics.Process.Refresh%2A> method. Therefore, a property value is not guaranteed to be any newer than the last call to the <xref:System.Diagnostics.Process.Refresh%2A> method. The group breakdowns are operating-system dependent.

If you have a path variable declared in your system using quotes, you must fully qualify that path when starting any process found in that location. Otherwise, the system will not find the path. For example, if `c:\mypath` is not in your path, and you add it using quotation marks: `path = %path%;"c:\mypath"`, you must fully qualify any process in `c:\mypath` when starting it.

A system process is uniquely identified on the system by its process identifier. Like many Windows resources, a process is also identified by its handle, which might not be unique on the computer. A handle is the generic term for an identifier of a resource. The operating system persists the process handle, which is accessed through the <xref:System.Diagnostics.Process.Handle%2A> property of the <xref:System.Diagnostics.Process> component, even when the process has exited. Thus, you can get the process's administrative information, such as the <xref:System.Diagnostics.Process.ExitCode%2A> (usually either zero for success or a nonzero error code) and the <xref:System.Diagnostics.Process.ExitTime%2A>. Handles are an extremely valuable resource, so leaking handles is more virulent than leaking memory.

On macOS, the following properties return 0:

- <xref:System.Diagnostics.Process.PeakVirtualMemorySize64>

- <xref:System.Diagnostics.Process.PrivateMemorySize64>

- <xref:System.Diagnostics.Process.PeakWorkingSet64>

> [!NOTE]

> This class contains a link demand and an inheritance demand at the class level that applies to all members. A <xref:System.Security.SecurityException> is thrown when either the immediate caller or the derived class does not have full-trust permission. For details about security demands, see [Link Demands](/dotnet/framework/misc/link-demands).

<a name="Core"></a>

## .NET Core Notes

In .NET Framework, the <xref:System.Diagnostics.Process> class by default uses <xref:System.Console> encodings, which are typically code page encodings, for the input, output, and error streams. For example code, on systems whose culture is English (United States), code page 437 is the default encoding for the <xref:System.Console> class. However, .NET Core may make only a limited subset of these encodings available. If this is the case, it uses <xref:System.Text.Encoding.UTF8%2A?displayProperty=nameWithType> as the default encoding.

If a <xref:System.Diagnostics.Process> object depends on specific code page encodings, you can still make them available by doing the following *before* you call any <xref:System.Diagnostics.Process> methods:

1. Retrieve the <xref:System.Text.EncodingProvider> object from the <xref:System.Text.CodePagesEncodingProvider.Instance%2A?displayProperty=nameWithType> property.

2. Pass the <xref:System.Text.EncodingProvider> object to the <xref:System.Text.Encoding.RegisterProvider%2A?displayProperty=nameWithType> method to make the additional encodings supported by the encoding provider available.

The <xref:System.Diagnostics.Process> class will then automatically use the default system encoding rather than UTF8, provided that you have registered the encoding provider before calling any <xref:System.Diagnostics.Process> methods.

## Examples

The following example uses an instance of the <xref:System.Diagnostics.Process> class to start a process.

:::code language="csharp" source="~/snippets/csharp/System.Diagnostics/Process/Overview/processstart.cs" id="Snippet1":::

:::code language="fsharp" source="~/snippets/fsharp/System.Diagnostics/Process/Overview/processstart.fs" id="Snippet1":::

:::code language="vb" source="~/snippets/visualbasic/System.Diagnostics/Process/Overview/processstart.vb" id="Snippet1":::

The following example uses the <xref:System.Diagnostics.Process> class itself and a static <xref:System.Diagnostics.Process.Start%2A> method to start a process.

:::code language="csharp" source="~/snippets/csharp/System.Diagnostics/Process/Overview/processstartstatic.cs":::

:::code language="fsharp" source="~/snippets/fsharp/System.Diagnostics/Process/Overview/processstartstatic.fs":::

:::code language="vb" source="~/snippets/visualbasic/System.Diagnostics/Process/Overview/processstartstatic.vb":::

The following F# example defines a `runProc` function that starts a process, captures all output and error information, and records the number of milliseconds that the process has run. The `runProc` function has three parameters: the name of application to launch, the arguments to supply to the application, and the starting directory.

:::code language="fsharp" source="~/snippets/fsharp/VS_Snippets_CLR_System/system.diagnostics.process/fs/Start1.fs" id="Snippet1":::

The code for the `runProc` function was written by [ImaginaryDevelopment](http://fssnip.net/authors/ImaginaryDevelopment) and is available under the [Microsoft Public License](https://opensource.org/licenses/ms-pl).

]]></format>

</remarks>

<altmember cref="M:System.Diagnostics.Process.Start" />

<altmember cref="T:System.Diagnostics.ProcessStartInfo" />

<altmember cref="M:System.Diagnostics.Process.CloseMainWindow" />

<altmember cref="M:System.Diagnostics.Process.Kill" />

<altmember cref="T:System.Diagnostics.ProcessThread" />

</Docs>

<Members>

<Member MemberName=".ctor">

<MemberSignature Language="C#" Value="public Process ();" />

<MemberSignature Language="ILAsm" Value=".method public hidebysig specialname rtspecialname instance void .ctor() cil managed" />

<MemberSignature Language="DocId" Value="M:System.Diagnostics.Process.#ctor" />

<MemberSignature Language="VB.NET" Value="Public Sub New ()" />

<MemberSignature Language="C++ CLI" Value="public:&#xA; Process();" />

<MemberType>Constructor</MemberType>

<AssemblyInfo>

<AssemblyName>System.Diagnostics.Process</AssemblyName>

<AssemblyVersion>4.1.0.0</AssemblyVersion>

<AssemblyVersion>4.2.0.0</AssemblyVersion>

<AssemblyVersion>4.2.1.0</AssemblyVersion>

<AssemblyVersion>4.2.2.0</AssemblyVersion>

<AssemblyVersion>5.0.0.0</AssemblyVersion>

<AssemblyVersion>6.0.0.0</AssemblyVersion>

<AssemblyVersion>7.0.0.0</AssemblyVersion>

<AssemblyVersion>8.0.0.0</AssemblyVersion>

<AssemblyVersion>9.0.0.0</AssemblyVersion>

<AssemblyVersion>10.0.0.0</AssemblyVersion>

<AssemblyVersion>11.0.0.0</AssemblyVersion>

</AssemblyInfo>

<AssemblyInfo>

<AssemblyName>System</AssemblyName>

<AssemblyVersion>1.0.5000.0</AssemblyVersion>

<AssemblyVersion>2.0.0.0</AssemblyVersion>

<AssemblyVersion>2.0.5.0</AssemblyVersion>

<AssemblyVersion>4.0.0.0</AssemblyVersion>

</AssemblyInfo>

<AssemblyInfo>

<AssemblyName>netstandard</AssemblyName>

<AssemblyVersion>2.0.0.0</AssemblyVersion>

<AssemblyVersion>2.1.0.0</AssemblyVersion>

</AssemblyInfo>

<Parameters />

<Docs>

<summary>Initializes a new instance of the <see cref="T:System.Diagnostics.Process" /> class.</summary>

<remarks>

<format type="text/markdown"><![CDATA[

## Remarks

If you do not specify the <xref:System.Diagnostics.Process.MachineName%2A> property, the default is the local computer, (".").

You have two options for associating a new <xref:System.Diagnostics.Process> component with a process on the computer. The first option is to use the constructor to create the <xref:System.Diagnostics.Process> component, set the appropriate members of the <xref:System.Diagnostics.Process.StartInfo%2A> property and call <xref:System.Diagnostics.Process.Start%2A> to associate the <xref:System.Diagnostics.Process> with a new system process. The second option is to associate the <xref:System.Diagnostics.Process> with a running system process by using <xref:System.Diagnostics.Process.GetProcessById%2A> or one of the <xref:System.Diagnostics.Process.GetProcesses%2A> return values.

If you use a `static` overload of the <xref:System.Diagnostics.Process.Start%2A> method to start a new system process, the method creates a new <xref:System.Diagnostics.Process> component and associates it with the process.

When the <xref:System.Diagnostics.ProcessStartInfo.UseShellExecute%2A?displayProperty=nameWithType> property is set to its default value, `true`, you can start applications and documents in a way that is similar to using the `Run` dialog box of the Windows `Start` menu. When <xref:System.Diagnostics.ProcessStartInfo.UseShellExecute%2A?displayProperty=nameWithType> is `false`, you can start only executables.

Any executable file that you can call from the command line can be started in one of two ways: by setting the appropriate members of the <xref:System.Diagnostics.Process.StartInfo%2A> property and calling the <xref:System.Diagnostics.Process.Start%2A> method with no parameters, or by passing the appropriate parameter to the `static` <xref:System.Diagnostics.Process.Start%2A> member.

You can create a <xref:System.Diagnostics.Process> component by using the constructor, one of the static <xref:System.Diagnostics.Process.Start%2A> overloads, or any of the <xref:System.Diagnostics.Process.GetProcessById%2A>, <xref:System.Diagnostics.Process.GetProcesses%2A>, or <xref:System.Diagnostics.Process.GetProcessesByName%2A> methods. After you have done so, you have a view into the associated process. This is not a dynamic view that updates itself automatically when the process properties have changed in memory. Instead, you must call <xref:System.Diagnostics.Process.Refresh%2A> for the component to update the <xref:System.Diagnostics.Process> property information in your application.

]]></format>

</remarks>

</Docs>

</Member>

<Member MemberName="BasePriority">

<MemberSignature Language="C#" Value="public int BasePriority { get; }" />

<MemberSignature Language="ILAsm" Value=".property instance int32 BasePriority" />

<MemberSignature Language="DocId" Value="P:System.Diagnostics.Process.BasePriority" />

<MemberSignature Language="VB.NET" Value="Public ReadOnly Property BasePriority As Integer" />

<MemberSignature Language="F#" Value="member this.BasePriority : int" Usage="System.Diagnostics.Process.BasePriority" />

<MemberSignature Language="C++ CLI" Value="public:&#xA; property int BasePriority { int get(); };" />

<MemberType>Property</MemberType>

<AssemblyInfo>

<AssemblyName>System.Diagnostics.Process</AssemblyName>

<AssemblyVersion>4.1.0.0</AssemblyVersion>

<AssemblyVersion>4.2.0.0</AssemblyVersion>

<AssemblyVersion>4.2.1.0</AssemblyVersion>

<AssemblyVersion>4.2.2.0</AssemblyVersion>

<AssemblyVersion>5.0.0.0</AssemblyVersion>

<AssemblyVersion>6.0.0.0</AssemblyVersion>

<AssemblyVersion>7.0.0.0</AssemblyVersion>

<AssemblyVersion>8.0.0.0</AssemblyVersion>

<AssemblyVersion>9.0.0.0</AssemblyVersion>

<AssemblyVersion>10.0.0.0</AssemblyVersion>

<AssemblyVersion>11.0.0.0</AssemblyVersion>

</AssemblyInfo>

<AssemblyInfo>

<AssemblyName>System</AssemblyName>

<AssemblyVersion>1.0.5000.0</AssemblyVersion>

<AssemblyVersion>2.0.0.0</AssemblyVersion>

<AssemblyVersion>2.0.5.0</AssemblyVersion>

<AssemblyVersion>4.0.0.0</AssemblyVersion>

</AssemblyInfo>

<AssemblyInfo>

<AssemblyName>netstandard</AssemblyName>

<AssemblyVersion>2.0.0.0</AssemblyVersion>

<AssemblyVersion>2.1.0.0</AssemblyVersion>

</AssemblyInfo>

<Attributes>

<Attribute FrameworkAlternate="netframework-1.1;netframework-2.0;netframework-3.0;netframework-3.5;netframework-4.0;netframework-4.5;netframework-4.5.1;netframework-4.5.2;netframework-4.6;netframework-4.6.1;netframework-4.6.2;netframework-4.7;netframework-4.7.1;netframework-4.7.2;netframework-4.8;netframework-4.8.1;netstandard-2.0;netstandard-2.1">

<AttributeName Language="C#">[System.ComponentModel.DesignerSerializationVisibility(System.ComponentModel.DesignerSerializationVisibility.Hidden)]</AttributeName>

<AttributeName Language="F#">[&lt;System.ComponentModel.DesignerSerializationVisibility(System.ComponentModel.DesignerSerializationVisibility.Hidden)&gt;]</AttributeName>

</Attribute>

<Attribute FrameworkAlternate="netframework-1.1;netframework-2.0;netframework-3.0;netframework-3.5;netframework-4.0;netframework-4.5;netframework-4.5.1;netframework-4.5.2;netframework-4.6;netframework-4.6.1;netframework-4.6.2;netframework-4.7;netframework-4.7.1;netframework-4.7.2;netframework-4.8;netframework-4.8.1">

<AttributeName Language="C#">[System.Diagnostics.MonitoringDescription("ProcessBasePriority")]</AttributeName>

<AttributeName Language="F#">[&lt;System.Diagnostics.MonitoringDescription("ProcessBasePriority")&gt;]</AttributeName>

</Attribute>

</Attributes>

<ReturnValue>

<ReturnType>System.Int32</ReturnType>

</ReturnValue>

<Docs>

<summary>Gets the base priority of the associated process.</summary>

<value>The base priority, which is computed from the <see cref="P:System.Diagnostics.Process.PriorityClass" /> of the associated process.</value>

<remarks>

<format type="text/markdown"><![CDATA[

## Remarks

The value returned by this property represents the most recently refreshed base priority of the process. To get the most up to date base priority, you need to call <xref:System.Diagnostics.Process.Refresh> method first.

The <xref:System.Diagnostics.Process.BasePriority%2A> of the process is the starting priority for threads created within the associated process. You can view information about the base priority through the System Monitor's Priority Base counter.

Based on the time elapsed or other boosts, the operating system can change the base priority when a process should be placed ahead of others.

The <xref:System.Diagnostics.Process.BasePriority%2A> property lets you view the starting priority assigned to a process. However, because it is read-only, you cannot use the <xref:System.Diagnostics.Process.BasePriority%2A> to set the priority of the process. To change the priority, use the <xref:System.Diagnostics.Process.PriorityClass%2A> property. The <xref:System.Diagnostics.Process.BasePriority%2A> is viewable using the System Monitor, while the <xref:System.Diagnostics.Process.PriorityClass%2A> is not. Both the <xref:System.Diagnostics.Process.BasePriority%2A> and the <xref:System.Diagnostics.Process.PriorityClass%2A> can be viewed programmatically. The following table shows the relationship between <xref:System.Diagnostics.Process.BasePriority%2A> values and <xref:System.Diagnostics.Process.PriorityClass%2A> values.

|BasePriority|PriorityClass|

|------------------|-------------------|

|4|<xref:System.Diagnostics.ProcessPriorityClass.Idle>|

|8|<xref:System.Diagnostics.ProcessPriorityClass.Normal>|

|13|<xref:System.Diagnostics.ProcessPriorityClass.High>|

|24|<xref:System.Diagnostics.ProcessPriorityClass.RealTime>|

## Examples

The following example starts an instance of Notepad. The example then retrieves and displays various properties of the associated process. The example detects when the process exits, and displays the process's exit code.

:::code language="csharp" source="~/snippets/csharp/System.Diagnostics/Process/BasePriority/source.cs" id="Snippet1":::

:::code language="fsharp" source="~/snippets/fsharp/System.Diagnostics/Process/BasePriority/source.fs" id="Snippet1":::

:::code language="vb" source="~/snippets/visualbasic/System.Diagnostics/Process/BasePriority/source.vb" id="Snippet1":::

]]></format>

</remarks>

<exception cref="T:System.InvalidOperationException">The process has exited.

-or-

The process has not started, so there is no process ID.</exception>

<altmember cref="P:System.Diagnostics.Process.PriorityClass" />

<altmember cref="T:System.Diagnostics.ProcessPriorityClass" />

<altmember cref="T:System.Diagnostics.ThreadPriorityLevel" />

</Docs>

</Member>

<Member MemberName="BeginErrorReadLine">

<MemberSignature Language="C#" Value="public void BeginErrorReadLine ();" />

<MemberSignature Language="ILAsm" Value=".method public hidebysig instance void BeginErrorReadLine() cil managed" />

<MemberSignature Language="DocId" Value="M:System.Diagnostics.Process.BeginErrorReadLine" />

<MemberSignature Language="VB.NET" Value="Public Sub BeginErrorReadLine ()" />

<MemberSignature Language="F#" Value="member this.BeginErrorReadLine : unit -&gt; unit" Usage="process.BeginErrorReadLine " />

<MemberSignature Language="C++ CLI" Value="public:&#xA; void BeginErrorReadLine();" />

<MemberType>Method</MemberType>

<AssemblyInfo>

<AssemblyName>System.Diagnostics.Process</AssemblyName>

<AssemblyVersion>4.1.0.0</AssemblyVersion>

<AssemblyVersion>4.2.0.0</AssemblyVersion>

<AssemblyVersion>4.2.1.0</AssemblyVersion>

<AssemblyVersion>4.2.2.0</AssemblyVersion>

<AssemblyVersion>5.0.0.0</AssemblyVersion>

<AssemblyVersion>6.0.0.0</AssemblyVersion>

<AssemblyVersion>7.0.0.0</AssemblyVersion>

<AssemblyVersion>8.0.0.0</AssemblyVersion>

<AssemblyVersion>9.0.0.0</AssemblyVersion>

<AssemblyVersion>10.0.0.0</AssemblyVersion>

<AssemblyVersion>11.0.0.0</AssemblyVersion>

</AssemblyInfo>

<AssemblyInfo>

<AssemblyName>System</AssemblyName>

<AssemblyVersion>2.0.0.0</AssemblyVersion>

<AssemblyVersion>2.0.5.0</AssemblyVersion>

<AssemblyVersion>4.0.0.0</AssemblyVersion>

</AssemblyInfo>

<AssemblyInfo>

<AssemblyName>netstandard</AssemblyName>

<AssemblyVersion>2.0.0.0</AssemblyVersion>

<AssemblyVersion>2.1.0.0</AssemblyVersion>

</AssemblyInfo>

<Attributes>

<Attribute FrameworkAlternate="netframework-2.0;netframework-3.0;netframework-3.5;netframework-4.0;netframework-4.5;netframework-4.5.1;netframework-4.5.2;netframework-4.6;netframework-4.6.1;netframework-4.6.2;netframework-4.7;netframework-4.7.1;netframework-4.7.2;netframework-4.8;netframework-4.8.1">

<AttributeName Language="C#">[System.Runtime.InteropServices.ComVisible(false)]</AttributeName>

<AttributeName Language="F#">[&lt;System.Runtime.InteropServices.ComVisible(false)&gt;]</AttributeName>

</Attribute>

</Attributes>

<ReturnValue>

<ReturnType>System.Void</ReturnType>

</ReturnValue>

<Parameters />

<Docs>

<summary>Begins asynchronous read operations on the redirected <see cref="P:System.Diagnostics.Process.StandardError" /> stream of the application.</summary>

<remarks>

<format type="text/markdown"><![CDATA[

## Remarks

The <xref:System.Diagnostics.Process.StandardError%2A> stream can be read synchronously or asynchronously. Methods such as <xref:System.IO.StreamReader.Read%2A>, <xref:System.IO.StreamReader.ReadLine%2A>, and <xref:System.IO.StreamReader.ReadToEnd%2A> perform synchronous read operations on the error output stream of the process. These synchronous read operations do not complete until the associated <xref:System.Diagnostics.Process> writes to its <xref:System.Diagnostics.Process.StandardError%2A> stream, or closes the stream.

In contrast, <xref:System.Diagnostics.Process.BeginErrorReadLine%2A> starts asynchronous read operations on the <xref:System.Diagnostics.Process.StandardError%2A> stream. This method enables the designated event handler for the stream output and immediately returns to the caller, which can perform other work while the stream output is directed to the event handler.

Follow these steps to perform asynchronous read operations on <xref:System.Diagnostics.Process.StandardError%2A> for a <xref:System.Diagnostics.Process> :

1. Set <xref:System.Diagnostics.ProcessStartInfo.UseShellExecute%2A> to `false`.

2. Set <xref:System.Diagnostics.ProcessStartInfo.RedirectStandardError%2A> to `true`.

3. Add your event handler to the <xref:System.Diagnostics.Process.ErrorDataReceived> event. The event handler must match the <xref:System.Diagnostics.DataReceivedEventHandler?displayProperty=nameWithType> delegate signature.

4. Start the <xref:System.Diagnostics.Process>.

5. Call <xref:System.Diagnostics.Process.BeginErrorReadLine%2A> for the <xref:System.Diagnostics.Process>. This call starts asynchronous read operations on <xref:System.Diagnostics.Process.StandardError%2A>.

When asynchronous read operations start, the event handler is called each time the associated <xref:System.Diagnostics.Process> writes a line of text to its <xref:System.Diagnostics.Process.StandardError%2A> stream.

You can cancel an asynchronous read operation by calling <xref:System.Diagnostics.Process.CancelErrorRead%2A>. The read operation can be canceled by the caller or by the event handler. After canceling, you can call <xref:System.Diagnostics.Process.BeginErrorReadLine%2A> again to resume asynchronous read operations.

> [!NOTE]

> You cannot mix asynchronous and synchronous read operations on a redirected stream. Once the redirected stream of a <xref:System.Diagnostics.Process> is opened in either asynchronous or synchronous mode, all further read operations on that stream must be in the same mode. For example, do not follow <xref:System.Diagnostics.Process.BeginErrorReadLine%2A> with a call to <xref:System.IO.StreamReader.ReadLine%2A> on the <xref:System.Diagnostics.Process.StandardError%2A> stream, or vice versa. However, you can read two different streams in different modes. For example, you can call <xref:System.Diagnostics.Process.BeginErrorReadLine%2A> and then call <xref:System.IO.StreamReader.ReadLine%2A> for the <xref:System.Diagnostics.Process.StandardOutput%2A> stream.

## Examples

The following example uses the `net view` command to list the available network resources on a remote computer. The user supplies the target computer name as a command-line argument. The user can also supply a file name for error output. The example collects the output of the net command, waits for the process to finish, and then writes the output results to the console. If the user supplies the optional error file, the example writes errors to the file.

:::code language="csharp" source="~/snippets/csharp/System.Diagnostics/DataReceivedEventArgs/Overview/net_async.cs" id="Snippet2":::

:::code language="fsharp" source="~/snippets/fsharp/System.Diagnostics/DataReceivedEventArgs/Overview/net_async.fs" id="Snippet2":::

:::code language="vb" source="~/snippets/visualbasic/System.Diagnostics/DataReceivedEventArgs/Overview/net_async.vb" id="Snippet2":::

]]></format>

</remarks>

<exception cref="T:System.InvalidOperationException">The <see cref="P:System.Diagnostics.ProcessStartInfo.RedirectStandardError" /> property is <see langword="false" />.

-or-

An asynchronous read operation is already in progress on the <see cref="P:System.Diagnostics.Process.StandardError" /> stream.

-or-

The <see cref="P:System.Diagnostics.Process.StandardError" /> stream has been used by a synchronous read operation.</exception>

<altmember cref="P:System.Diagnostics.ProcessStartInfo.RedirectStandardError" />

<altmember cref="P:System.Diagnostics.Process.StandardError" />

<altmember cref="E:System.Diagnostics.Process.ErrorDataReceived" />

<altmember cref="T:System.Diagnostics.DataReceivedEventHandler" />

<altmember cref="M:System.Diagnostics.Process.CancelErrorRead" />

</Docs>

</Member>

<Member MemberName="BeginOutputReadLine">

<MemberSignature Language="C#" Value="public void BeginOutputReadLine ();" />

<MemberSignature Language="ILAsm" Value=".method public hidebysig instance void BeginOutputReadLine() cil managed" />

<MemberSignature Language="DocId" Value="M:System.Diagnostics.Process.BeginOutputReadLine" />

<MemberSignature Language="VB.NET" Value="Public Sub BeginOutputReadLine ()" />

<MemberSignature Language="F#" Value="member this.BeginOutputReadLine : unit -&gt; unit" Usage="process.BeginOutputReadLine " />

<MemberSignature Language="C++ CLI" Value="public:&#xA; void BeginOutputReadLine();" />

<MemberType>Method</MemberType>

<AssemblyInfo>

<AssemblyName>System.Diagnostics.Process</AssemblyName>

<AssemblyVersion>4.1.0.0</AssemblyVersion>

<AssemblyVersion>4.2.0.0</AssemblyVersion>

<AssemblyVersion>4.2.1.0</AssemblyVersion>

<AssemblyVersion>4.2.2.0</AssemblyVersion>

<AssemblyVersion>5.0.0.0</AssemblyVersion>

<AssemblyVersion>6.0.0.0</AssemblyVersion>

<AssemblyVersion>7.0.0.0</AssemblyVersion>

<AssemblyVersion>8.0.0.0</AssemblyVersion>

<AssemblyVersion>9.0.0.0</AssemblyVersion>

<AssemblyVersion>10.0.0.0</AssemblyVersion>

<AssemblyVersion>11.0.0.0</AssemblyVersion>

</AssemblyInfo>

<AssemblyInfo>

<AssemblyName>System</AssemblyName>

<AssemblyVersion>2.0.0.0</AssemblyVersion>

<AssemblyVersion>2.0.5.0</AssemblyVersion>

<AssemblyVersion>4.0.0.0</AssemblyVersion>

</AssemblyInfo>

<AssemblyInfo>

<AssemblyName>netstandard</AssemblyName>

<AssemblyVersion>2.0.0.0</AssemblyVersion>

<AssemblyVersion>2.1.0.0</AssemblyVersion>

</AssemblyInfo>

<Attributes>

<Attribute FrameworkAlternate="netframework-2.0;netframework-3.0;netframework-3.5;netframework-4.0;netframework-4.5;netframework-4.5.1;netframework-4.5.2;netframework-4.6;netframework-4.6.1;netframework-4.6.2;netframework-4.7;netframework-4.7.1;netframework-4.7.2;netframework-4.8;netframework-4.8.1">

<AttributeName Language="C#">[System.Runtime.InteropServices.ComVisible(false)]</AttributeName>

<AttributeName Language="F#">[&lt;System.Runtime.InteropServices.ComVisible(false)&gt;]</AttributeName>

</Attribute>

</Attributes>

<ReturnValue>

<ReturnType>System.Void</ReturnType>

</ReturnValue>

<Parameters />

<Docs>

<summary>Begins asynchronous read operations on the redirected <see cref="P:System.Diagnostics.Process.StandardOutput" /> stream of the application.</summary>

<remarks>

<format type="text/markdown"><![CDATA[

## Remarks

The <xref:System.Diagnostics.Process.StandardOutput%2A> stream can be read synchronously or asynchronously. Methods such as <xref:System.IO.StreamReader.Read%2A>, <xref:System.IO.StreamReader.ReadLine%2A>, and <xref:System.IO.StreamReader.ReadToEnd%2A> perform synchronous read operations on the output stream of the process. These synchronous read operations do not complete until the associated <xref:System.Diagnostics.Process> writes to its <xref:System.Diagnostics.Process.StandardOutput%2A> stream, or closes the stream.

In contrast, <xref:System.Diagnostics.Process.BeginOutputReadLine%2A> starts asynchronous read operations on the <xref:System.Diagnostics.Process.StandardOutput%2A> stream. This method enables a designated event handler for the stream output and immediately returns to the caller, which can perform other work while the stream output is directed to the event handler.

Follow these steps to perform asynchronous read operations on <xref:System.Diagnostics.Process.StandardOutput%2A> for a <xref:System.Diagnostics.Process> :

1. Set <xref:System.Diagnostics.ProcessStartInfo.UseShellExecute%2A> to `false`.

2. Set <xref:System.Diagnostics.ProcessStartInfo.RedirectStandardOutput%2A> to `true`.

3. Add your event handler to the <xref:System.Diagnostics.Process.OutputDataReceived> event. The event handler must match the <xref:System.Diagnostics.DataReceivedEventHandler?displayProperty=nameWithType> delegate signature.

4. Start the <xref:System.Diagnostics.Process>.

5. Call <xref:System.Diagnostics.Process.BeginOutputReadLine%2A> for the <xref:System.Diagnostics.Process>. This call starts asynchronous read operations on <xref:System.Diagnostics.Process.StandardOutput%2A>.

When asynchronous read operations start, the event handler is called each time the associated <xref:System.Diagnostics.Process> writes a line of text to its <xref:System.Diagnostics.Process.StandardOutput%2A> stream.

You can cancel an asynchronous read operation by calling <xref:System.Diagnostics.Process.CancelOutputRead%2A>. The read operation can be canceled by the caller or by the event handler. After canceling, you can call <xref:System.Diagnostics.Process.BeginOutputReadLine%2A> again to resume asynchronous read operations.

> [!NOTE]

> You cannot mix asynchronous and synchronous read operations on a redirected stream. Once the redirected stream of a <xref:System.Diagnostics.Process> is opened in either asynchronous or synchronous mode, all further read operations on that stream must be in the same mode. For example, do not follow <xref:System.Diagnostics.Process.BeginOutputReadLine%2A> with a call to <xref:System.IO.StreamReader.ReadLine%2A> on the <xref:System.Diagnostics.Process.StandardOutput%2A> stream, or vice versa. However, you can read two different streams in different modes. For example, you can call <xref:System.Diagnostics.Process.BeginOutputReadLine%2A> and then call <xref:System.IO.StreamReader.ReadLine%2A> for the <xref:System.Diagnostics.Process.StandardError%2A> stream.

## Examples

The following example illustrates how to perform asynchronous read operations on the redirected <xref:System.Diagnostics.Process.StandardOutput%2A> stream of the `sort` command. The `sort` command is a console application that reads and sorts text input.

The example creates an event delegate for the `SortOutputHandler` event handler and associates it with the <xref:System.Diagnostics.Process.OutputDataReceived> event. The event handler receives text lines from the redirected <xref:System.Diagnostics.Process.StandardOutput%2A> stream, formats the text, and writes the text to the screen.

:::code language="csharp" source="~/snippets/csharp/System.Diagnostics/DataReceivedEventArgs/Overview/sort_async.cs" id="Snippet1":::

:::code language="fsharp" source="~/snippets/fsharp/System.Diagnostics/DataReceivedEventArgs/Overview/sort_async.fs" id="Snippet1":::

:::code language="vb" source="~/snippets/visualbasic/System.Diagnostics/DataReceivedEventArgs/Overview/sort_async.vb" id="Snippet1":::

]]></format>

</remarks>

<exception cref="T:System.InvalidOperationException">The <see cref="P:System.Diagnostics.ProcessStartInfo.RedirectStandardOutput" /> property is <see langword="false" />.

-or-

An asynchronous read operation is already in progress on the <see cref="P:System.Diagnostics.Process.StandardOutput" /> stream.

-or-

The <see cref="P:System.Diagnostics.Process.StandardOutput" /> stream has been used by a synchronous read operation.</exception>

<altmember cref="P:System.Diagnostics.ProcessStartInfo.RedirectStandardOutput" />

<altmember cref="P:System.Diagnostics.Process.StandardOutput" />

<altmember cref="E:System.Diagnostics.Process.OutputDataReceived" />

<altmember cref="T:System.Diagnostics.DataReceivedEventHandler" />

<altmember cref="M:System.Diagnostics.Process.CancelOutputRead" />

</Docs>

</Member>

<Member MemberName="CancelErrorRead">

<MemberSignature Language="C#" Value="public void CancelErrorRead ();" />

<MemberSignature Language="ILAsm" Value=".method public hidebysig instance void CancelErrorRead() cil managed" />

<MemberSignature Language="DocId" Value="M:System.Diagnostics.Process.CancelErrorRead" />

<MemberSignature Language="VB.NET" Value="Public Sub CancelErrorRead ()" />

<MemberSignature Language="F#" Value="member this.CancelErrorRead : unit -&gt; unit" Usage="process.CancelErrorRead " />

<MemberSignature Language="C++ CLI" Value="public:&#xA; void CancelErrorRead();" />

<MemberType>Method</MemberType>

<AssemblyInfo>

<AssemblyName>System.Diagnostics.Process</AssemblyName>

<AssemblyVersion>4.1.0.0</AssemblyVersion>

<AssemblyVersion>4.2.0.0</AssemblyVersion>

<AssemblyVersion>4.2.1.0</AssemblyVersion>

<AssemblyVersion>4.2.2.0</AssemblyVersion>

<AssemblyVersion>5.0.0.0</AssemblyVersion>

<AssemblyVersion>6.0.0.0</AssemblyVersion>

<AssemblyVersion>7.0.0.0</AssemblyVersion>

<AssemblyVersion>8.0.0.0</AssemblyVersion>

<AssemblyVersion>9.0.0.0</AssemblyVersion>

<AssemblyVersion>10.0.0.0</AssemblyVersion>

<AssemblyVersion>11.0.0.0</AssemblyVersion>

</AssemblyInfo>

<AssemblyInfo>

<AssemblyName>System</AssemblyName>

<AssemblyVersion>2.0.0.0</AssemblyVersion>

<AssemblyVersion>2.0.5.0</AssemblyVersion>

<AssemblyVersion>4.0.0.0</AssemblyVersion>

</AssemblyInfo>

<AssemblyInfo>

<AssemblyName>netstandard</AssemblyName>

<AssemblyVersion>2.0.0.0</AssemblyVersion>

<AssemblyVersion>2.1.0.0</AssemblyVersion>

</AssemblyInfo>

<Attributes>

<Attribute FrameworkAlternate="netframework-2.0;netframework-3.0;netframework-3.5;netframework-4.0;netframework-4.5;netframework-4.5.1;netframework-4.5.2;netframework-4.6;netframework-4.6.1;netframework-4.6.2;netframework-4.7;netframework-4.7.1;netframework-4.7.2;netframework-4.8;netframework-4.8.1">

<AttributeName Language="C#">[System.Runtime.InteropServices.ComVisible(false)]</AttributeName>

<AttributeName Language="F#">[&lt;System.Runtime.InteropServices.ComVisible(false)&gt;]</AttributeName>

</Attribute>

</Attributes>

<ReturnValue>

<ReturnType>System.Void</ReturnType>

</ReturnValue>

<Parameters />

<Docs>

<summary>Cancels the asynchronous read operation on the redirected <see cref="P:System.Diagnostics.Process.StandardError" /> stream of an application.</summary>

<remarks>

<format type="text/markdown"><![CDATA[

## Remarks

<xref:System.Diagnostics.Process.BeginErrorReadLine%2A> starts an asynchronous read operation on the <xref:System.Diagnostics.Process.StandardError%2A> stream. <xref:System.Diagnostics.Process.CancelErrorRead%2A> ends the asynchronous read operation.

After canceling, you can resume the asynchronous read operation by calling <xref:System.Diagnostics.Process.BeginErrorReadLine%2A> again.

When you call <xref:System.Diagnostics.Process.CancelErrorRead%2A>, all in-progress read operations for <xref:System.Diagnostics.Process.StandardError%2A> are completed and then the event handler is disabled. All further redirected output to <xref:System.Diagnostics.Process.StandardError%2A> will be lost. If you re-enable the event handler with a call to <xref:System.Diagnostics.Process.BeginErrorReadLine%2A>, asynchronous read operations resume. If you want to change the event handler before resuming asynchronous read operations, you must remove the existing event handler before adding the new event handler:

```csharp

// At this point the DataReceivedEventHandler(ErrorHandler1)

// has executed a CancelErrorRead.

// Remove the prior event handler.

process.ErrorDataReceived -=

new DataReceivedEventHandler(ErrorHandler1);

// Register a new event handler.

process.ErrorDataReceived +=

new DataReceivedEventHandler(ErrorHandler2);

// Call the corresponding BeginErrorReadLine.

process.BeginErrorReadLine();

```

> [!NOTE]

> You cannot mix asynchronous and synchronous read operations on the redirected <xref:System.Diagnostics.Process.StandardError%2A> stream. Once the redirected stream of a <xref:System.Diagnostics.Process> is opened in either asynchronous or synchronous mode, all further read operations on that stream must be in the same mode. If you cancel an asynchronous read operation on <xref:System.Diagnostics.Process.StandardError%2A> and then need to read from the stream again, you must use <xref:System.Diagnostics.Process.BeginErrorReadLine%2A> to resume asynchronous read operations. Do not follow <xref:System.Diagnostics.Process.CancelErrorRead%2A> with a call to the synchronous read methods of <xref:System.Diagnostics.Process.StandardError%2A> such as <xref:System.IO.StreamReader.Read%2A>, <xref:System.IO.StreamReader.ReadLine%2A>, or <xref:System.IO.StreamReader.ReadToEnd%2A>.

## Examples

The following example starts the `nmake` command with user supplied arguments. The error and output streams are read asynchronously; the collected text lines are displayed to the console as well as written to a log file. If the command output exceeds a specified number of lines, the asynchronous read operations are canceled.

:::code language="csharp" source="~/snippets/csharp/System.Diagnostics/DataReceivedEventArgs/Overview/nmake_async.cs" id="Snippet3":::

:::code language="fsharp" source="~/snippets/fsharp/System.Diagnostics/DataReceivedEventArgs/Overview/nmake_async.fs" id="Snippet3":::

:::code language="vb" source="~/snippets/visualbasic/System.Diagnostics/DataReceivedEventArgs/Overview/nmake_async.vb" id="Snippet3":::

]]></format>

</remarks>

<exception cref="T:System.InvalidOperationException">The <see cref="P:System.Diagnostics.Process.StandardError" /> stream is not enabled for asynchronous read operations.</exception>

<altmember cref="M:System.Diagnostics.Process.BeginErrorReadLine" />

<altmember cref="P:System.Diagnostics.ProcessStartInfo.RedirectStandardError" />

<altmember cref="P:System.Diagnostics.Process.StandardError" />

<altmember cref="E:System.Diagnostics.Process.ErrorDataReceived" />

<altmember cref="T:System.Diagnostics.DataReceivedEventHandler" />

</Docs>

</Member>

<Member MemberName="CancelOutputRead">

<MemberSignature Language="C#" Value="public void CancelOutputRead ();" />

<MemberSignature Language="ILAsm" Value=".method public hidebysig instance void CancelOutputRead() cil managed" />

<MemberSignature Language="DocId" Value="M:System.Diagnostics.Process.CancelOutputRead" />

<MemberSignature Language="VB.NET" Value="Public Sub CancelOutputRead ()" />

<MemberSignature Language="F#" Value="member this.CancelOutputRead : unit -&gt; unit" Usage="process.CancelOutputRead " />

<MemberSignature Language="C++ CLI" Value="public:&#xA; void CancelOutputRead();" />

<MemberType>Method</MemberType>

<AssemblyInfo>

<AssemblyName>System.Diagnostics.Process</AssemblyName>

<AssemblyVersion>4.1.0.0</AssemblyVersion>

<AssemblyVersion>4.2.0.0</AssemblyVersion>

<AssemblyVersion>4.2.1.0</AssemblyVersion>

<AssemblyVersion>4.2.2.0</AssemblyVersion>

<AssemblyVersion>5.0.0.0</AssemblyVersion>

<AssemblyVersion>6.0.0.0</AssemblyVersion>

<AssemblyVersion>7.0.0.0</AssemblyVersion>

<AssemblyVersion>8.0.0.0</AssemblyVersion>

<AssemblyVersion>9.0.0.0</AssemblyVersion>

<AssemblyVersion>10.0.0.0</AssemblyVersion>

<AssemblyVersion>11.0.0.0</AssemblyVersion>

</AssemblyInfo>

<AssemblyInfo>

<AssemblyName>System</AssemblyName>

<AssemblyVersion>2.0.0.0</AssemblyVersion>

<AssemblyVersion>2.0.5.0</AssemblyVersion>

<AssemblyVersion>4.0.0.0</AssemblyVersion>

</AssemblyInfo>

<AssemblyInfo>

<AssemblyName>netstandard</AssemblyName>

<AssemblyVersion>2.0.0.0</AssemblyVersion>

<AssemblyVersion>2.1.0.0</AssemblyVersion>

</AssemblyInfo>

<Attributes>

<Attribute FrameworkAlternate="netframework-2.0;netframework-3.0;netframework-3.5;netframework-4.0;netframework-4.5;netframework-4.5.1;netframework-4.5.2;netframework-4.6;netframework-4.6.1;netframework-4.6.2;netframework-4.7;netframework-4.7.1;netframework-4.7.2;netframework-4.8;netframework-4.8.1">

<AttributeName Language="C#">[System.Runtime.InteropServices.ComVisible(false)]</AttributeName>

<AttributeName Language="F#">[&lt;System.Runtime.InteropServices.ComVisible(false)&gt;]</AttributeName>

</Attribute>

</Attributes>

<ReturnValue>

<ReturnType>System.Void</ReturnType>

</ReturnValue>

<Parameters />

<Docs>

<summary>Cancels the asynchronous read operation on the redirected <see cref="P:System.Diagnostics.Process.StandardOutput" /> stream of an application.</summary>

<remarks>

<format type="text/markdown"><![CDATA[

## Remarks

<xref:System.Diagnostics.Process.BeginOutputReadLine%2A> starts an asynchronous read operation on the <xref:System.Diagnostics.Process.StandardOutput%2A> stream. <xref:System.Diagnostics.Process.CancelOutputRead%2A> ends the asynchronous read operation.

After canceling, you can resume asynchronous read operations by calling <xref:System.Diagnostics.Process.BeginOutputReadLine%2A> again.

When you call <xref:System.Diagnostics.Process.CancelOutputRead%2A>, all in-progress read operations for <xref:System.Diagnostics.Process.StandardOutput%2A> are completed and then the event handler is disabled. All further redirected output to <xref:System.Diagnostics.Process.StandardOutput%2A> is saved in a buffer. If you re-enable the event handler with a call to <xref:System.Diagnostics.Process.BeginOutputReadLine%2A>, the saved output is sent to the event handler and asynchronous read operations resume. If you want to change the event handler before resuming asynchronous read operations, you must remove the existing event handler before adding the new event handler:

```csharp

// At this point the DataReceivedEventHandler(OutputHandler1)

// has executed a CancelOutputRead.

// Remove the prior event handler.

process.OutputDataReceived -=

new DataReceivedEventHandler(OutputHandler1);

// Register a new event handler.

process.OutputDataReceived +=

new DataReceivedEventHandler(OutputHandler2);

// Call the corresponding BeginOutputReadLine.

process.BeginOutputReadLine();

```

> [!NOTE]

> You cannot mix asynchronous and synchronous read operations on the redirected <xref:System.Diagnostics.Process.StandardOutput%2A> stream. Once the redirected stream of a <xref:System.Diagnostics.Process> is opened in either asynchronous or synchronous mode, all further read operations on that stream must be in the same mode. If you cancel an asynchronous read operation on <xref:System.Diagnostics.Process.StandardOutput%2A> and then need to read from the stream again, you must use <xref:System.Diagnostics.Process.BeginOutputReadLine%2A> to resume asynchronous read operations. Do not follow <xref:System.Diagnostics.Process.CancelOutputRead%2A> with a call to the synchronous read methods of <xref:System.Diagnostics.Process.StandardOutput%2A> such as <xref:System.IO.StreamReader.Read%2A>, <xref:System.IO.StreamReader.ReadLine%2A>, or <xref:System.IO.StreamReader.ReadToEnd%2A>.

## Examples

The following example starts the `nmake` command with user supplied arguments. The error and output streams are read asynchronously; the collected text lines are displayed to the console as well as written to a log file. If the command output exceeds a specified number of lines, the asynchronous read operations are canceled.

:::code language="csharp" source="~/snippets/csharp/System.Diagnostics/DataReceivedEventArgs/Overview/nmake_async.cs" id="Snippet3":::

:::code language="fsharp" source="~/snippets/fsharp/System.Diagnostics/DataReceivedEventArgs/Overview/nmake_async.fs" id="Snippet3":::

:::code language="vb" source="~/snippets/visualbasic/System.Diagnostics/DataReceivedEventArgs/Overview/nmake_async.vb" id="Snippet3":::

]]></format>

</remarks>

<exception cref="T:System.InvalidOperationException">The <see cref="P:System.Diagnostics.Process.StandardOutput" /> stream is not enabled for asynchronous read operations.</exception>

<altmember cref="M:System.Diagnostics.Process.BeginOutputReadLine" />

<altmember cref="P:System.Diagnostics.ProcessStartInfo.RedirectStandardOutput" />

<altmember cref="P:System.Diagnostics.Process.StandardOutput" />

<altmember cref="E:System.Diagnostics.Process.OutputDataReceived" />

<altmember cref="T:System.Diagnostics.DataReceivedEventHandler" />

</Docs>

</Member>

<Member MemberName="Close">

<MemberSignature Language="C#" Value="public void Close ();" />

<MemberSignature Language="ILAsm" Value=".method public hidebysig instance void Close() cil managed" />

<MemberSignature Language="DocId" Value="M:System.Diagnostics.Process.Close" />

<MemberSignature Language="VB.NET" Value="Public Sub Close ()" />

<MemberSignature Language="F#" Value="member this.Close : unit -&gt; unit" Usage="process.Close " />

<MemberSignature Language="C++ CLI" Value="public:&#xA; void Close();" />

<MemberType>Method</MemberType>

<AssemblyInfo>

<AssemblyName>System</AssemblyName>

<AssemblyVersion>1.0.5000.0</AssemblyVersion>

<AssemblyVersion>2.0.0.0</AssemblyVersion>

<AssemblyVersion>2.0.5.0</AssemblyVersion>

<AssemblyVersion>4.0.0.0</AssemblyVersion>

</AssemblyInfo>

<AssemblyInfo>

<AssemblyName>netstandard</AssemblyName>

<AssemblyVersion>2.0.0.0</AssemblyVersion>

<AssemblyVersion>2.1.0.0</AssemblyVersion>

</AssemblyInfo>

<AssemblyInfo>

<AssemblyName>System.Diagnostics.Process</AssemblyName>

<AssemblyVersion>4.2.0.0</AssemblyVersion>

<AssemblyVersion>4.2.1.0</AssemblyVersion>

<AssemblyVersion>4.2.2.0</AssemblyVersion>

<AssemblyVersion>5.0.0.0</AssemblyVersion>

<AssemblyVersion>6.0.0.0</AssemblyVersion>

<AssemblyVersion>7.0.0.0</AssemblyVersion>

<AssemblyVersion>8.0.0.0</AssemblyVersion>

<AssemblyVersion>9.0.0.0</AssemblyVersion>

<AssemblyVersion>10.0.0.0</AssemblyVersion>

<AssemblyVersion>11.0.0.0</AssemblyVersion>

</AssemblyInfo>

<ReturnValue>

<ReturnType>System.Void</ReturnType>

</ReturnValue>

<Parameters />

<Docs>

<summary>Frees all the resources that are associated with this component.</summary>

<remarks>

<format type="text/markdown"><![CDATA[

## Remarks

The <xref:System.Diagnostics.Process.Close%2A> method causes the process to stop waiting for exit if it was waiting, closes the process handle, and clears process-specific properties. <xref:System.Diagnostics.Process.Close%2A> does not close the standard output, input, and error readers and writers in case they are being referenced externally.

> [!NOTE]

> The <xref:System.Diagnostics.Process.Dispose%2A> method calls <xref:System.Diagnostics.Process.Close%2A>. Placing the <xref:System.Diagnostics.Process> object in a `using` block disposes of resources without the need to call <xref:System.Diagnostics.Process.Close%2A>.

## Examples

The following example starts an instance of Notepad. It then retrieves the physical memory usage of the associated process at 2-second intervals for a maximum of 10 seconds. The example detects whether the process exits before 10 seconds have elapsed. The example closes the process if it is still running after 10 seconds.

:::code language="csharp" source="~/snippets/csharp/System.Diagnostics/Process/Close/process_refresh.cs" id="Snippet1":::

:::code language="fsharp" source="~/snippets/fsharp/System.Diagnostics/Process/Close/process_refresh.fs" id="Snippet1":::

:::code language="vb" source="~/snippets/visualbasic/System.Diagnostics/Process/Close/process_refresh.vb" id="Snippet1":::

]]></format>

</remarks>

</Docs>

</Member>

<Member MemberName="CloseMainWindow">

<MemberSignature Language="C#" Value="public bool CloseMainWindow ();" />

<MemberSignature Language="ILAsm" Value=".method public hidebysig instance bool CloseMainWindow() cil managed" />

<MemberSignature Language="DocId" Value="M:System.Diagnostics.Process.CloseMainWindow" />

<MemberSignature Language="VB.NET" Value="Public Function CloseMainWindow () As Boolean" />

<MemberSignature Language="F#" Value="member this.CloseMainWindow : unit -&gt; bool" Usage="process.CloseMainWindow " />

<MemberSignature Language="C++ CLI" Value="public:&#xA; bool CloseMainWindow();" />

<MemberType>Method</MemberType>

<AssemblyInfo>

<AssemblyName>System</AssemblyName>

<AssemblyVersion>1.0.5000.0</AssemblyVersion>

<AssemblyVersion>2.0.0.0</AssemblyVersion>

<AssemblyVersion>2.0.5.0</AssemblyVersion>

<AssemblyVersion>4.0.0.0</AssemblyVersion>

</AssemblyInfo>

<AssemblyInfo>

<AssemblyName>netstandard</AssemblyName>

<AssemblyVersion>2.0.0.0</AssemblyVersion>

<AssemblyVersion>2.1.0.0</AssemblyVersion>

</AssemblyInfo>

<AssemblyInfo>

<AssemblyName>System.Diagnostics.Process</AssemblyName>

<AssemblyVersion>4.2.0.0</AssemblyVersion>

<AssemblyVersion>4.2.1.0</AssemblyVersion>

<AssemblyVersion>4.2.2.0</AssemblyVersion>

<AssemblyVersion>5.0.0.0</AssemblyVersion>

<AssemblyVersion>6.0.0.0</AssemblyVersion>

<AssemblyVersion>7.0.0.0</AssemblyVersion>

<AssemblyVersion>8.0.0.0</AssemblyVersion>

<AssemblyVersion>9.0.0.0</AssemblyVersion>

<AssemblyVersion>10.0.0.0</AssemblyVersion>

<AssemblyVersion>11.0.0.0</AssemblyVersion>

</AssemblyInfo>

<ReturnValue>

<ReturnType>System.Boolean</ReturnType>

</ReturnValue>

<Parameters />

<Docs>

<summary>Closes a process that has a user interface by sending a close message to its main window.</summary>

<returns>

<see langword="true" /> if the close message was successfully sent; <see langword="false" /> if the associated process does not have a main window or if the main window is disabled (for example if a modal dialog is being shown).</returns>

<remarks>

<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 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.

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.

## Examples

The following example starts an instance of Notepad. It then retrieves the physical memory usage of the associated process at 2 second intervals for a maximum of 10 seconds. The example detects whether the process exits before 10 seconds have elapsed. The example closes the process if it is still running after 10 seconds.

:::code language="csharp" source="~/snippets/csharp/System.Diagnostics/Process/Close/process_refresh.cs" id="Snippet1":::

:::code language="fsharp" source="~/snippets/fsharp/System.Diagnostics/Process/Close/process_refresh.fs" id="Snippet1":::

:::code language="vb" source="~/snippets/visualbasic/System.Diagnostics/Process/Close/process_refresh.vb" id="Snippet1":::

]]></format>

</remarks>

<exception cref="T:System.InvalidOperationException">The process has already exited.

-or-

No process is associated with this <see cref="T:System.Diagnostics.Process" /> object.</exception>

</Docs>

</Member>

<Member MemberName="Dispose">

<MemberSignature Language="C#" Value="public void Dispose ();" />

<MemberSignature Language="ILAsm" Value=".method public hidebysig newslot virtual instance void Dispose() cil managed" />

<MemberSignature Language="DocId" Value="M:System.Diagnostics.Process.Dispose" />

<MemberSignature Language="VB.NET" Value="Public Sub Dispose ()" />

<MemberSignature Language="F#" Value="abstract member Dispose : unit -&gt; unit&#xA;override this.Dispose : unit -&gt; unit" Usage="process.Dispose " />

<MemberSignature Language="C++ CLI" Value="public:&#xA; virtual void Dispose();" />

<MemberType>Method</MemberType>

<Implements>

<InterfaceMember>M:System.IDisposable.Dispose</InterfaceMember>

</Implements>

<AssemblyInfo>

<AssemblyName>System.Diagnostics.Process</AssemblyName>

<AssemblyVersion>4.1.0.0</AssemblyVersion>

</AssemblyInfo>

<AssemblyInfo>

<AssemblyName>netstandard</AssemblyName>

</AssemblyInfo>

<AssemblyInfo>

<AssemblyName>System</AssemblyName>

</AssemblyInfo>

<ReturnValue>

<ReturnType>System.Void</ReturnType>

</ReturnValue>

<Parameters />

<Docs>

<summary>Performs application-defined tasks associated with freeing, releasing, or resetting unmanaged resources.</summary>

<remarks>To be added.</remarks>

</Docs>

</Member>

<Member MemberName="Dispose">

<MemberSignature Language="C#" Value="protected override void Dispose (bool disposing);" FrameworkAlternate="net-10.0;net-11.0;net-5.0;net-6.0;net-7.0;net-8.0;net-9.0;netcore-2.0;netcore-2.1;netcore-2.2;netcore-3.0;netcore-3.1;netframework-1.1;netframework-2.0;netframework-3.0;netframework-3.5;netframework-4.0;netframework-4.5;netframework-4.5.1;netframework-4.5.2;netframework-4.6;netframework-4.6.1;netframework-4.6.2;netframework-4.7;netframework-4.7.1;netframework-4.7.2;netframework-4.8;netframework-4.8.1;netstandard-2.0;netstandard-2.1" />

<MemberSignature Language="ILAsm" Value=".method familyhidebysig virtual instance void Dispose(bool disposing) cil managed" FrameworkAlternate="net-10.0;net-11.0;net-5.0;net-6.0;net-7.0;net-8.0;net-9.0;netcore-2.0;netcore-2.1;netcore-2.2;netcore-3.0;netcore-3.1;netframework-1.1;netframework-2.0;netframework-3.0;netframework-3.5;netframework-4.0;netframework-4.5;netframework-4.5.1;netframework-4.5.2;netframework-4.6;netframework-4.6.1;netframework-4.6.2;netframework-4.7;netframework-4.7.1;netframework-4.7.2;netframework-4.8;netframework-4.8.1;netstandard-2.0;netstandard-2.1" />

<MemberSignature Language="DocId" Value="M:System.Diagnostics.Process.Dispose(System.Boolean)" />

<MemberSignature Language="VB.NET" Value="Protected Overrides Sub Dispose (disposing As Boolean)" FrameworkAlternate="net-10.0;net-11.0;net-5.0;net-6.0;net-7.0;net-8.0;net-9.0;netcore-2.0;netcore-2.1;netcore-2.2;netcore-3.0;netcore-3.1;netframework-1.1;netframework-2.0;netframework-3.0;netframework-3.5;netframework-4.0;netframework-4.5;netframework-4.5.1;netframework-4.5.2;netframework-4.6;netframework-4.6.1;netframework-4.6.2;netframework-4.7;netframework-4.7.1;netframework-4.7.2;netframework-4.8;netframework-4.8.1;netstandard-2.0;netstandard-2.1" />

<MemberSignature Language="F#" Value="override this.Dispose : bool -&gt; unit" Usage="process.Dispose disposing" FrameworkAlternate="net-10.0;net-11.0;net-5.0;net-6.0;net-7.0;net-8.0;net-9.0;netcore-2.0;netcore-2.1;netcore-2.2;netcore-3.0;netcore-3.1;netframework-1.1;netframework-2.0;netframework-3.0;netframework-3.5;netframework-4.0;netframework-4.5;netframework-4.5.1;netframework-4.5.2;netframework-4.6;netframework-4.6.1;netframework-4.6.2;netframework-4.7;netframework-4.7.1;netframework-4.7.2;netframework-4.8;netframework-4.8.1;netstandard-2.0;netstandard-2.1" />

<MemberSignature Language="C++ CLI" Value="protected:&#xA; override void Dispose(bool disposing);" FrameworkAlternate="net-10.0;net-11.0;net-5.0;net-6.0;net-7.0;net-8.0;net-9.0;netcore-2.0;netcore-2.1;netcore-2.2;netcore-3.0;netcore-3.1;netframework-1.1;netframework-2.0;netframework-3.0;netframework-3.5;netframework-4.0;netframework-4.5;netframework-4.5.1;netframework-4.5.2;netframework-4.6;netframework-4.6.1;netframework-4.6.2;netframework-4.7;netframework-4.7.1;netframework-4.7.2;netframework-4.8;netframework-4.8.1;netstandard-2.0;netstandard-2.1" />

<MemberSignature Language="C#" Value="protected virtual void Dispose (bool disposing);" FrameworkAlternate="netcore-1.0;netcore-1.1" />

<MemberSignature Language="ILAsm" Value=".method familyhidebysig newslot virtual instance void Dispose(bool disposing) cil managed" FrameworkAlternate="netcore-1.0;netcore-1.1" />

<MemberSignature Language="VB.NET" Value="Protected Overridable Sub Dispose (disposing As Boolean)" FrameworkAlternate="netcore-1.0;netcore-1.1" />

<MemberSignature Language="F#" Value="abstract member Dispose : bool -&gt; unit&#xA;override this.Dispose : bool -&gt; unit" Usage="process.Dispose disposing" FrameworkAlternate="netcore-1.0;netcore-1.1" />

<MemberSignature Language="C++ CLI" Value="protected:&#xA; virtual void Dispose(bool disposing);" FrameworkAlternate="netcore-1.0;netcore-1.1" />

<MemberType>Method</MemberType>

<AssemblyInfo>

<AssemblyName>System.Diagnostics.Process</AssemblyName>

<AssemblyVersion>4.1.0.0</AssemblyVersion>

<AssemblyVersion>4.2.0.0</AssemblyVersion>

<AssemblyVersion>4.2.1.0</AssemblyVersion>

<AssemblyVersion>4.2.2.0</AssemblyVersion>

<AssemblyVersion>5.0.0.0</AssemblyVersion>

<AssemblyVersion>6.0.0.0</AssemblyVersion>

<AssemblyVersion>7.0.0.0</AssemblyVersion>

<AssemblyVersion>8.0.0.0</AssemblyVersion>

<AssemblyVersion>9.0.0.0</AssemblyVersion>

<AssemblyVersion>10.0.0.0</AssemblyVersion>

<AssemblyVersion>11.0.0.0</AssemblyVersion>

</AssemblyInfo>

<AssemblyInfo>

<AssemblyName>System</AssemblyName>

<AssemblyVersion>1.0.5000.0</AssemblyVersion>

<AssemblyVersion>2.0.0.0</AssemblyVersion>

<AssemblyVersion>2.0.5.0</AssemblyVersion>

<AssemblyVersion>4.0.0.0</AssemblyVersion>

</AssemblyInfo>

<AssemblyInfo>

<AssemblyName>netstandard</AssemblyName>

<AssemblyVersion>2.0.0.0</AssemblyVersion>

<AssemblyVersion>2.1.0.0</AssemblyVersion>

</AssemblyInfo>

<ReturnValue>

<ReturnType>System.Void</ReturnType>

</ReturnValue>

<Parameters>

<Parameter Name="disposing" Type="System.Boolean" />

</Parameters>

<Docs>

<param name="disposing">

<see langword="true" /> to release both managed and unmanaged resources; <see langword="false" /> to release only unmanaged resources.</param>

<summary>Release all resources used by this process.</summary>

<remarks>To be added.</remarks>

</Docs>

</Member>

<Member MemberName="EnableRaisingEvents">

<MemberSignature Language="C#" Value="public bool EnableRaisingEvents { get; set; }" />

<MemberSignature Language="ILAsm" Value=".property instance bool EnableRaisingEvents" />

<MemberSignature Language="DocId" Value="P:System.Diagnostics.Process.EnableRaisingEvents" />

<MemberSignature Language="VB.NET" Value="Public Property EnableRaisingEvents As Boolean" />

<MemberSignature Language="F#" Value="member this.EnableRaisingEvents : bool with get, set" Usage="System.Diagnostics.Process.EnableRaisingEvents" />

<MemberSignature Language="C++ CLI" Value="public:&#xA; property bool EnableRaisingEvents { bool get(); void set(bool value); };" />

<MemberType>Property</MemberType>

<AssemblyInfo>

<AssemblyName>System.Diagnostics.Process</AssemblyName>

<AssemblyVersion>4.1.0.0</AssemblyVersion>

<AssemblyVersion>4.2.0.0</AssemblyVersion>

<AssemblyVersion>4.2.1.0</AssemblyVersion>

<AssemblyVersion>4.2.2.0</AssemblyVersion>

<AssemblyVersion>5.0.0.0</AssemblyVersion>

<AssemblyVersion>6.0.0.0</AssemblyVersion>

<AssemblyVersion>7.0.0.0</AssemblyVersion>

<AssemblyVersion>8.0.0.0</AssemblyVersion>

<AssemblyVersion>9.0.0.0</AssemblyVersion>

<AssemblyVersion>10.0.0.0</AssemblyVersion>

<AssemblyVersion>11.0.0.0</AssemblyVersion>

</AssemblyInfo>

<AssemblyInfo>

<AssemblyName>System</AssemblyName>

<AssemblyVersion>1.0.5000.0</AssemblyVersion>

<AssemblyVersion>2.0.0.0</AssemblyVersion>

<AssemblyVersion>2.0.5.0</AssemblyVersion>

<AssemblyVersion>4.0.0.0</AssemblyVersion>

</AssemblyInfo>

<AssemblyInfo>

<AssemblyName>netstandard</AssemblyName>

<AssemblyVersion>2.0.0.0</AssemblyVersion>

<AssemblyVersion>2.1.0.0</AssemblyVersion>

</AssemblyInfo>

<Attributes>

<Attribute FrameworkAlternate="netcore-1.0;netcore-1.1;netcore-2.0;netcore-2.1;netcore-2.2;netcore-3.0;netcore-3.1;netframework-1.1;netframework-2.0;netframework-3.0;netframework-3.5;netframework-4.0;netframework-4.5;netframework-4.5.1;netframework-4.5.2;netframework-4.6;netframework-4.6.1;netframework-4.6.2;netframework-4.7;netframework-4.7.1;netframework-4.7.2;netframework-4.8;netframework-4.8.1;netstandard-2.0;netstandard-2.1">

<AttributeName Language="C#">[System.ComponentModel.DefaultValue(false)]</AttributeName>

<AttributeName Language="F#">[&lt;System.ComponentModel.DefaultValue(false)&gt;]</AttributeName>

</Attribute>

<Attribute FrameworkAlternate="netframework-1.1;netframework-2.0;netframework-3.0;netframework-3.5;netframework-4.0;netframework-4.5;netframework-4.5.1;netframework-4.5.2;netframework-4.6;netframework-4.6.1;netframework-4.6.2;netframework-4.7;netframework-4.7.1;netframework-4.7.2;netframework-4.8;netframework-4.8.1;netstandard-2.0;netstandard-2.1">

<AttributeName Language="C#">[System.ComponentModel.Browsable(false)]</AttributeName>

<AttributeName Language="F#">[&lt;System.ComponentModel.Browsable(false)&gt;]</AttributeName>

</Attribute>

<Attribute FrameworkAlternate="netframework-1.1;netframework-2.0;netframework-3.0;netframework-3.5;netframework-4.0;netframework-4.5;netframework-4.5.1;netframework-4.5.2;netframework-4.6;netframework-4.6.1;netframework-4.6.2;netframework-4.7;netframework-4.7.1;netframework-4.7.2;netframework-4.8;netframework-4.8.1">

<AttributeName Language="C#">[System.Diagnostics.MonitoringDescription("ProcessEnableRaisingEvents")]</AttributeName>

<AttributeName Language="F#">[&lt;System.Diagnostics.MonitoringDescription("ProcessEnableRaisingEvents")&gt;]</AttributeName>

</Attribute>

<Attribute FrameworkAlternate="netframework-4.0">

<AttributeName Language="C#">[get: System.Runtime.TargetedPatchingOptOut("Performance critical to inline this type of method across NGen image boundaries")]</AttributeName>

<AttributeName Language="F#">[&lt;get: System.Runtime.TargetedPatchingOptOut("Performance critical to inline this type of method across NGen image boundaries")&gt;]</AttributeName>

</Attribute>

</Attributes>

<ReturnValue>

<ReturnType>System.Boolean</ReturnType>

</ReturnValue>

<Docs>

<summary>Gets or sets whether the <see cref="E:System.Diagnostics.Process.Exited" /> event should be raised when the process terminates.</summary>

<value>

<see langword="true" /> if the <see cref="E:System.Diagnostics.Process.Exited" /> event should be raised when the associated process is terminated (through either an exit or a call to <see cref="M:System.Diagnostics.Process.Kill" />); otherwise, <see langword="false" />. The default is <see langword="false" />. Note that even if the value of <see cref="P:System.Diagnostics.Process.EnableRaisingEvents" /> is <see langword="false" />, the <see cref="E:System.Diagnostics.Process.Exited" /> event will be raised by the <see cref="P:System.Diagnostics.Process.HasExited" /> property accessor, if it determines that the process has exited.</value>

<remarks>

<format type="text/markdown"><![CDATA[

## Remarks

The <xref:System.Diagnostics.Process.EnableRaisingEvents%2A> property suggests whether the component should be notified when the operating system has shut down a process. The <xref:System.Diagnostics.Process.EnableRaisingEvents%2A> property is used in asynchronous processing to notify your application that a process has exited. To force your application to synchronously wait for an exit event (which interrupts processing of the application until the exit event has occurred), use the <xref:System.Diagnostics.Process.WaitForExit%2A> method.

> [!NOTE]

> If you're using Visual Studio and double-click a <xref:System.Diagnostics.Process> component in your project, an <xref:System.Diagnostics.Process.Exited> event delegate and event handler are automatically generated. Additional code sets the <xref:System.Diagnostics.Process.EnableRaisingEvents%2A> property to `false`. You must change this property to `true` for your event handler to execute when the associated process exits.

If the component's <xref:System.Diagnostics.Process.EnableRaisingEvents%2A> value is `true`, or when <xref:System.Diagnostics.Process.EnableRaisingEvents%2A> is `false` and a <xref:System.Diagnostics.Process.HasExited%2A> check is invoked by the component, the component can access the administrative information for the associated process, which remains stored by the operating system. Such information includes the <xref:System.Diagnostics.Process.ExitTime%2A> and the <xref:System.Diagnostics.Process.ExitCode%2A>.

After the associated process exits, the <xref:System.Diagnostics.Process.Handle%2A> of the component no longer points to an existing process resource. Instead, it can only be used to access the operating system's information about the process resource. The operating system is aware that there are handles to exited processes that haven't been released by <xref:System.Diagnostics.Process> components, so it keeps the <xref:System.Diagnostics.Process.ExitTime%2A> and <xref:System.Diagnostics.Process.Handle%2A> information in memory.

There's a cost associated with watching for a process to exit. If <xref:System.Diagnostics.Process.EnableRaisingEvents%2A> is `true`, the <xref:System.Diagnostics.Process.Exited> event is raised when the associated process terminates. Your procedures for the <xref:System.Diagnostics.Process.Exited> event run at that time.

Sometimes, your application starts a process but doesn't require notification of its closure. For example, your application can start Notepad to allow the user to perform text editing but make no further use of the Notepad application. You can choose to avoid notification when the process exits because it's not relevant to the continued operation of your application. Setting <xref:System.Diagnostics.Process.EnableRaisingEvents%2A> to `false` can save system resources.

## Examples

The following code example creates a process that prints a file. It sets the <xref:System.Diagnostics.Process.EnableRaisingEvents%2A> property to cause the process to raise the <xref:System.Diagnostics.Process.Exited> event when it exits. The <xref:System.Diagnostics.Process.Exited> event handler displays process information.

:::code language="csharp" source="~/snippets/csharp/System.Diagnostics/Process/EnableRaisingEvents/processexitedevent.cs" id="Snippet1":::

:::code language="fsharp" source="~/snippets/fsharp/System.Diagnostics/Process/EnableRaisingEvents/processexitedevent.fs" id="Snippet1":::

:::code language="vb" source="~/snippets/visualbasic/System.Diagnostics/Process/EnableRaisingEvents/processexitedevent.vb" id="Snippet1":::

]]></format>

</remarks>

<altmember cref="M:System.Diagnostics.Process.WaitForExit(System.Int32)" />

<altmember cref="E:System.Diagnostics.Process.Exited" />

<altmember cref="M:System.Diagnostics.Process.CloseMainWindow" />

<altmember cref="M:System.Diagnostics.Process.Kill" />

<altmember cref="P:System.Diagnostics.Process.Handle" />

<altmember cref="P:System.Diagnostics.Process.ExitTime" />