https://bugs.winehq.org/show_bug.cgi?id=47669
--- Comment #24 from Zebediah Figura z.figura12@gmail.com --- (In reply to ryan from comment #19)
(In reply to Zebediah Figura from comment #18)
I think there's Mono problems here, but I'm not sure and I can't get the wine-mono debugging channels to work correctly for some reason.
Maybe a different approach is possible. I take it that this is the mono that's taking over for .net... maybe it can be disabled and .net used instead?
Trying native .NET would probably be worthwhile, yeah. Not sure which version though.
I suspect it's a mono problem partly because there are definitely CIL binaries involved, and partly because half the time I get STATUS_ILLEGAL_INSTRUCTION which can maybe suggest a wrongly marshalled vtbl (though that is an awfully specific guess).
I'm bothered by the fact that using WINE_MONO_TRACE doesn't seem to work properly. I can get exception messages that don't show up otherwise, but I don't get any relay messages for some reason. That makes debugging significantly harder...