If you know the module on the managed side, Module.ResolveMethod() can be used
to get a MethodInfo from a token.
Regards,
Jeroen
-Original Message-
From: mono-devel-list-boun...@lists.ximian.com [mailto:mono-devel-list-
boun...@lists.ximian.com] On Behalf Of Greg Young
Sent:
You could pass the manged MethodInfo* object directly into managed,
retrieving it in native code by calling: mono_method_get_object
Alternatively, you could pass a System.RuntimeMethodHandle struct into
managed code (with the MonoMethod* as the value in that structure) and
call
Let's say I have a MonoMethod in unmanaged code. I want to pass some
data out of that code back into managed code (using some identifiers
of the monomethod) so that the managed code can obtain a MethodInfo
via reflection.
At first I thought about passing the token(s). I cannot however find
anyway
Greetings!
I've stumbled upon what I believe to be a rather serious problem in mono's
WCF implementation.
When a client disconnects during a transmission from a WebServiceHost, an
exception is thrown:
Exception Write failure at System.Net.Sockets.NetworkStream.Write
(System.Byte[] buffer,
I have to pass by lookup values. My unmanaged is running in the context of
a profiler.
On Saturday, February 14, 2015, Jonathan Chambers jonc...@gmail.com wrote:
You could pass the manged MethodInfo* object directly into managed,
retrieving it in native code by calling: mono_method_get_object
That looks like a bad package.
XSP should not depend on a specific version of Mono, instead it should
require at least a specific version of Mono.
CCing Jo.
On Mon, Feb 9, 2015 at 11:46 AM, sean_houston sean.sta...@aesir-media.com
wrote:
apache2-mod_mono-3.12 is available in the CentOS
