On Mon, 2007-06-04 at 17:31 -0400, Miguel de Icaza wrote:
I rather not use the environment variable, for one computing the actual
program name might not be easy. I rather just hard code it to `mono'
and it would be up to the user to set the path name appropriately.
At least in
Hello,
A long time ago, I ran into the issue where Process.Start within mono
doesn't do what is expected. On Windows, it always runs the child process
with Microsoft's framework, which can cause problems if it is remoting back
to the parent process and hits an incompatibility. On other platforms,
Hi Jonathan,
+static gboolean
+is_managed_binary (const gchar *filename)
+{
You can replace this func with something like that:
gboolean
mono_image_is_cil (const char *fname)
{
MonoImageOpenStatus status;
MonoImage *image;
image = mono_image_open_full (fname, status,
On 6/2/07, Jonathan Gilbert [EMAIL PROTECTED] wrote:
Hello,
A long time ago, I ran into the issue where Process.Start within mono
doesn't do what is expected. On Windows, it always runs the child process
with Microsoft's framework, which can cause problems if it is remoting back
to the
Hello Jonathan,
A long time ago, I ran into the issue where Process.Start within mono
doesn't do what is expected. On Windows, it always runs the child process
with Microsoft's framework, which can cause problems if it is remoting back
to the parent process and hits an incompatibility. On
Hey,
I rather not use the environment variable, for one computing the actual
program name might not be easy. I rather just hard code it to `mono'
and it would be up to the user to set the path name appropriately.
At least in Debian, the mono executable is not called mono.
It's cli:
Hey,
Miguel de Icaza wrote:
You can replace this func with something like that:
The problem is that this code lives in io-layer.c and Dick pointed out
that it might be best to not depend on metadata code.
Oh, now I see that the patch is actually changing WAPI's CreateProcess.
This means
I rather not use the environment variable, for one computing the actual
program name might not be easy. I rather just hard code it to `mono'
and it would be up to the user to set the path name appropriately.
At least in Debian, the mono executable is not called mono.
It's cli:
