Re: [Mono-dev] System.Diagnostics.Process behaves differently in and outside of a NUnit test case

Hi Dan, As I am currently working on the Process class, I am getting a look at your bug. Does setting StandardOutputEncoding = Console.OutputEncoding on the ProcessStartInfo passed to Start fixes your issue? This is the behaviour on .NET, so this is the behaviour that we are going to adopt (at

Re: [Mono-dev] System.Diagnostics.Process behaves differently in and outside of a NUnit test case

Hi Ludovic, On 15 October 2015 at 12:47, Ludovic Henry wrote: > Hi Dan, > > As I am currently working on the Process class, I am getting a look at your > bug. Thanks for taking a look :) > > Does setting StandardOutputEncoding = Console.OutputEncoding on the >

[Mono-dev] System.Diagnostics.Process behaves differently in and outside of a NUnit test case

Hi, This is an issue that I was bitten by a while ago but I didn't post here because I managed to work around it but it looks like something inside mono changed between 3.12 and 4.0.4 which my broke my workaround. The issue basically is I observed my code failing when called from an NUnit test