Yes, this should probably not change on windows due to .net.
On Tue, Mar 4, 2014 at 3:12 PM, Charlie Poole <char...@nunit.com> wrote: > Can I assume this only applies to Linux? In the past, when I used > Process.Create > from a Mono app on Windows, the secondary process ran under MS .NET. > > Consequently, in order to work on both platforms, NUnit actually runs mono > again when it is already running under mono and launches its agent process. > > Charlie > > On Tue, Mar 4, 2014 at 9:21 AM, Rodrigo Kumpera <kump...@gmail.com> wrote: > > Hey Guys, > > > > I've been looking on how to fix those two bugs: > > https://bugzilla.xamarin.com/show_bug.cgi?id=17831 > > https://bugzilla.xamarin.com/show_bug.cgi?id=17820 > > > > And one option we're contemplating is to switch the behavior of > > Process.Create > > when launching managed assemblies to first try to use the currently > running > > runtime > > before delegating to one in PATH. > > > > Currently if you run a program that uses Process.Create with a runtime > not > > located in path, > > the launched process will use mono from the PATH, which to some sounds > > surprising. > > > > Does anyone know of any app that will break with such change of behavior? > > > > This probably only affects embedders and mono hackers. > > > > -- > > Rodrigo > > > > _______________________________________________ > > Mono-devel-list mailing list > > Mono-devel-list@lists.ximian.com > > http://lists.ximian.com/mailman/listinfo/mono-devel-list > > > _______________________________________________ > Mono-devel-list mailing list > Mono-devel-list@lists.ximian.com > http://lists.ximian.com/mailman/listinfo/mono-devel-list >
_______________________________________________ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
