1-to-1 native and direct replecement of System.Diagnostics.Process. Simply switch to it with "using KS.Diagnostics".

Most of the Process methods are supported. For more request them here: https://discord.gg/qdQQrjZneS

Supported OS:

• Windows x64

Experimental:

• Windows Arm64
• Linux x64
• Osx Intel x64
• Osx Arm64
• Windows 2019 Server x64 (also win7 embedded)

Implemented features:

System.Diagnostics.Process:

- StartInfo

- Start()

- Dispose()

- StartInfo

- EnableRaisingEvents

- Exited

- OutputDataReceived

- ErrorDataReceived

- BeginOutputReadLine()

- BeginErrorReadLine()

- CancelOutputRead()

- WaitForExit()

- GetProcesses()

- GetProcesses(string)

- GetProcessesByName(string)

- GetProcessesByName(string,string)

- Kill()

- Kill(bool)

- ProcessName

- Id

- ExitCode

- StartTime

- EndTime

- StandardInput.BaseStream.Write(byte[], count, offset) (currently small mem allocation)

- StandardInput.BaseStream.Write(IntPtr, count, offset) (no alloc)

- StandardInput.BaseStream.Flush()

- StandardInput.BaseStream.Close()

- StandardInput.Close()

- TotalProcessorTime

System.Diagnostics.ProcessStartInfo:

- FileName

- Arguments

- UseShellExecute

- RedirectStandardOutput

- RedirectStandardError

- CreateNoWindow

- WorkingDirectory

- Verb

- Verbs

Differences due to native code:

• OutputDataReceived object sender is always null
• Exited object sender is always null and EventArgs is always empty
• Exceptions may crash the application, make sure none can occur (for ex. wrong file path) Update: Exceptions shouldn't crash anymore and are rethrown as ExternalException, use Exception.HResult to check for specific type