0.7.0

0.6.2...0.7.0

New Features

• #5 Fix/move to common build

View the full list of issues and PRs

API Changes: Proc

Scanned: 📑 1 assemblies(s), Suggested change in version: Major
+ 0 breaking change(s) detected.

+ 🌟 3 new additions
- 🔴 1 removals
- 🔷 0 modifications

---

📑 Proc.dll

 Click here to see the 4 differences 

proc, Version=0.0.0.0, Culture=neutral, PublicKeyToken=96c599bbe3e70f5d 
+ 🌟 System.Reflection.AssemblyDescriptionAttribute::.ctor(System.String) 
+ 🌟 System.Reflection.AssemblyMetadataAttribute::.ctor(System.String,System.String) 
- 🔴 Proc 
+ 🌟 proc.dll 

0.6.2

Misc

• Fix GitHub links
• Bump Proc.Tests.Binary to netcoreapp2.1
• Always run xunit tests in release configuration

0.6.1

Allow WaitForStreamReaders to be null.

0.6.0

Adds Proc.StartRedirected which unlike Proc.Start won't capture and hold onto all console out written lines by default. Furthermore it exposes a console out handler that is line based where as Proc.Start is characterbased.

0.5.0

Rudimentary linux/osx support for SIGINT

dropped netstandard1.3 TFM

0.4.0

• Exec is now a void method that throws on an invalid exit code
• Exec can now be configured with a delegate to assert what constitutes an invalid exit code
• Exec can now be configured to not put arguments and cwd in the exception messages.
• Start no longer writes to output by default again (introduced in 0.3.8)

0.3.8...0.4.0

0.3.8

• add a simple Proc.Exec for the cases when all you want is to execute a command sharing the same console output as the host.

• improved reliability when calling Proc.Start with a consoleout writer. It now reuses the same published stream from subscribelines.

0.3.7...0.3.8

0.3.7

Fixed an issue where WaitHandle.WaitAll. When called from a STA thread it could lock up or throw an exception.

0.3.6

Create an explicit hook for doing something when the wait for streamreaders on exit times out

0.3.5

Additional hardening of ProcessStart() it now tries to read .Id and .ProcessName once (rather than being getter properties before). However, a very fast program can end immediately after calling .Start()and thenprocess.Id` can throw even if its the very next instruction.