[Mono-dev] Version-specific binding - resolved, but real bugs found

Brian Crowell mono-devel at fluggo.com
Wed Jun 14 17:29:55 EDT 2006

Brian Crowell wrote:
> mono-devel-list is taking a bizarre amount of time to show my message. 
> Regardless, here's one potential solution.

Unfortunately, this solution has splash damage.

Once this bug is fixed, other bad assumptions come into light. For example, a 
CrossAppDomainDelegate does not fire properly in the new domain because the 
assembly associated with its target is not loaded into the new domain before an 
attempt is made to call the target.

I believe the problem can be traced to a combination of the 
CrossAppDomainSink.SyncProcessMessage method (in 
/class/corlib/System.Runtime.Remoting.Channels/CrossAppDomainChannel.cs) and 
AppDomain.InvokeInDomainByID (in /class/corlib/System/AppDomain.cs). It seems to 
be because the cross-appdomain call bypasses the normal remoting channels, and 
therefore bypasses the part that ensures deserialized references can be used in 
the new domain.

I'll keep looking into this.


More information about the Mono-devel-list mailing list