Hi,
What we will do for Microsoft.Scripting.dll
Some said that it is open source so we can use microsoft dll directely.
Other said that we must redo it.
I have commit a start of it in olive module but the size of this dll is
quite bigger than compiler and runtime.
So if we can avoid to redo it
Bump. The patch is updated to current svn head.
I would have created a bugzilla entry for this, but bugzilla page
seems to be dead at the moment.
On 5/7/07, Leszek Ciesielski [EMAIL PROTECTED] wrote:
Hi,
I am again playing with getting evemon to work on mono, this is a next
set of stubs for
Hi,
Had a few minutes of spare time yesterday and just wanted to code a little.
Attached are the results - some classes for System.Design that should help
for the Windows Forms PropertyGrid control to be completely functional.
I currently have to ability to commit myself. So somebody please
Hello,
Bugzilla is up again
___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list
Hello,
Some said that it is open source so we can use microsoft dll
directely.
We will use it directly.
Other said that we must redo it.
They are wrong.
I have commit a start of it in olive module but the size of this dll
is quite bigger than compiler and runtime.
Do not commit this
hello martin,
I recently investigated the mono debugger and it looks quite good and
stable for mono c# development. however, I have some questions...
1) changing variables
the mono web site states that the debugger is able to Inspect and
change static and instance fields, local variables, and
Hello Martin,
I recently investigated the Mono Debugger and it looks quite good and
stable for Mono C# development. However, I have some questions...
1) Changing variables
The Mono web site states that the debugger is able to Inspect and
change static and instance fields, local variables, and
hello martin,
I recently investigated the mono debugger and it looks quite good and
stable for mono c# development. however, I have some questions...
1) changing variables
the mono web site states that the debugger is able to Inspect and
change static and instance fields, local variables, and
Hello,
The Subversion repository is back up in the new location.
They might need to recable it, so the service might go down for a
few minutes today, but should not take more than that.
Miguel
___
Mono-devel-list mailing list
Hello!
I was trying to use the new implementation of Sqlite provider
available now on mono, but I had several problems with it...
First of all it failed to perform BindParameters properly when I tried
to use named parameters. After some debugging it appeared that the
names of parameters are
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
Hello,
All services should be back up, please let me know if anything is
not working, so we can look into it.
Miguel.
Hello,
The Subversion repository is back up in the new location.
They might need to recable it, so the service might go down for a
few minutes today, but
Board of Directors
Officers, Directors
(NASDAQ:NOVL)
With all due respect, what are you thinking allowing this to happen? MONO is
arguably (one of) NOVLs Holy Grail(s), as are the Ximian technologists,
crown jewels.
Sincerely and respectfully,
/s/esecurites.com formerly wallstreetradio.com
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:
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
21 matches
Mail list logo
