I have base library in c++ and client application is in C#. There is c++/cli interface to access c++ api's from C#. Every thing works fine until more than one app domain not come into play like NUnit or WCF hosting i.e. with one app domain.
I have stored managed object in gcroot in cli for callback. I have read that this is the root cause of app domain issue ("Cannot pass a GCHandle across AppDomains") because they don't have app domain info (http://lambert.geek.nz/2007/05/29/unmanaged-appdomain-callback/). someone suggested to use delegates but my underlying c++ layer is expecting object not function pointer(http://www.lenholgate.com/blog/2009/07/error-cannot-pass-a-gchandle-across-appdomains.html). I have also tried IntPtr but in this case i am not able to cast it to my managed object during callbacks.
UPDATE
Let me elaborate my problem a bit more.
I have "Receiver" class in C# and this is passed as input parameter to one of the api. This receiver object is used for callback. In C++/CLI I have created a Native /unmanaged class "ObjectBinder" which is same replica (has same methods) of managed Receiver class. It holds reference of managed receiver object in gcroot. When we call that api from C# it comes to CLI layer and app domain is "client exe". we store the parameter "managed receiver object" in ObjectBinder in gcroot and pass reference of native ObjectBinder object to C++. Now the backend code (c++ and c) send an asyn callback (new thread) to c++ layer which use ObjectBinder object to send back call to CLI. Now we are in CLI layer in ObjectBinder object. BUT App domain has been changed (in case of WCF or NUNIT or any other service that creates it's own App domain which is not known at compile time) . Now i want to access managed Receiver object which is stored in gcroot to send back callback to C# but it gave APP DOMAIN error.
I have also tried IntPtr and IUnknown * instead of gcroot with Marshal::GetIUnknownForObject and Marshal::GetObjectForIUnknown but getting same error.
One possible workaround for this problem without delegates is to call a CrossAppDomainSingleton from your ObjectBinder class. The CrossAppDomainSingleton can hold the reference to your Receiver instance. This solution will dispatch your call to a dedicated app domain.
If you have multiple Receiver instances this could still work with a mapping logic in the singleton and passing some kind of id in the callback.
You can find an implementation here.
You cannot marshal a managed object between .NET application domains simply with
GCHandle.ToIntPtr
/GCHandle.FromIntPtr
, even if you derive fromMarshalByRefObject
orContextBoundObject
.One option to do that is to use COM and Global Interface Table (GIT). The COM Marshaller and .NET runtime will marshal the calls together, but you'd need to stick with a COM interface implemented by the managed object. This will work for calls across different domians and different COM apartment threads.
Another option is to create a COM-callable wrapper (CCW) with
Marshal.GetIUnknownForObject
, then useMarshal.GetObjectForIUnknown
from another domain. You'll get back a managed proxy object if you derived fromMarshalByRefObject
, or an unmanaged RCW proxy otherwise. This will work if you call your managed object on the same thread (albeit, from another app domain).Here is an example which illustrates the original problem (as I understood it) and these two possible solutions. I use a late-bound
InterfaceIsIDispatch
interface here to avoid having to register the type library (no need to do RegAsm, in case you also want to marshal cross-apartments, in addition to cross-domains).