That is totally acceptable.
Anyone with an idea where the Module identifier sits on monoclass?
On Sun, Feb 15, 2015 at 10:52 AM, Konrad Kruczynski
kkruczyn...@antmicro.com wrote:
Note however, that resolution via metadata token can only give you an open
type, that is information about bound
Note however, that resolution via metadata token can only give you an open
type, that is information about bound generic type is lost during
MethodInfo - MetadataToken - MethodInfo (since, naturally, only open
types are present in the assembly).
--
BR,
Konrad
2015-02-15 9:15 GMT+01:00 Greg
Hello, [ I am CCing Atsushi so he can eyeball the patch ]
Thanks for the background research and for pointing me to that
long-standing bug.
It seems like a pull request was created, but that the author closed the
pull request.
I have updated the patch, can you try this and report back?
Now to get module on the unmanaged side. I figured it might be in
MonoClass but have yet to find it there. Maybe I should be looking
under the referenced MonoImage (though that doesn't seem quite right)
On Sun, Feb 15, 2015 at 9:00 AM, Jeroen Frijters jer...@sumatra.nl wrote:
If you know the
As far as I can tell, that patch fixes the crash. I'll be doing some more
testing in the next few days.
I'd be grateful if you could also have a look at
https://bugzilla.xamarin.com/show_bug.cgi?id=20764
While it's not a crashing bug, it causes any OperationContract with a
return type of void to
Console output for debugging is done in very limited, IIRC in only one
or two [*1] locations and not supposed to be done everywhere. They
should be actually replaced by something like WCF logging feature that
can be enabled by some configuration. IIRC it partly works. Nothing will
be logged by
