On 24.04.2011 02:09, nmccready wrote:
Also what do I have to do to get MonoDevelop to look for new install?
Use the script at http://www.mono-project.com/Parallel_Mono_Environments
to setup the environment for using an alternate installation location.
Best Regards, David
--
dasz.at OG
While working on an interface between VirtualBox and C# on Linux, I ran
into a problem, which I think may be a bug in the mono code.
The System.Runtime.InteropServices.Marshal.GetObjectForIUnknown function
releases (using Marshal.Release) the given COM pointer. Microsoft's
documentation does
Ivo,
Both RCWs and CCWs should be working in mono. Please post more details of
the issues you are hitting. I am using both RCWs and CCWs extensively in my
applications.
The InterfaceType attribute is interesting. I believe interfaces are dual by
default (IDispatch based with a vtable), so if
I was under the impression that XPCOM is broken due to a GC bug. Is this
still the case?
Thanks,
Joe
___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list
Joe,
I can't find the bug # right now, but I'm assuming you are talking about
Release being called on the finalizer thread instead of the correct
creating/apartment of the COM object? I understand how it
can especially cause problems with UI controls requiring access on only the
UI thread. This
Hello,
In my FreeBSD Box, mono trunk build failed.
The following is build log.
$ gmake
gmake all-recursive
gmake[1]: Entering directory `/export/home/ksmakoto/Mono/BUILD'
(snip)
gmake[2]: Leaving directory `/export/home/ksmakoto/Mono/BUILD/libgc'
Making all in eglib
gmake[2]: Entering
