Hello,
I still prefer the environment variable approach. Are there any serious
disadvantages? Here are some additional thoughts:
And I still think that we will use a hardcoded value for the
interpreter.
- If it isn't going to work to have the code inside CreateProcess, then if
it is
At 10:57 PM 6/4/2007 +0200, Robert Jordan wrote:
Oh, now I see that the patch is actually changing WAPI's CreateProcess.
This means that it won't work on Windows, where the native
native CreateProcess is called instead.
I think it's better to implement this in System.Diagnostics.Process
using an
At 08:06 PM 6/4/2007 +0100, Leszek Ciesielski wrote:
There was some discussion of how this should work here:
http://bugzilla.ximian.com/show_bug.cgi?id=79263
I am still thinking that invoking through
AppDomain.ExecuteAssemblyByName
(http://msdn2.microsoft.com/en-us/library/6d3hh0kx.aspx) would be
