![]() | |
![]() |
| | Thread Tools | Search this Thread | Display Modes |
#11
| |||
| |||
|
|
John wrote: Basically, I want to use it as COM Global Interface Table, one app Appdomain running in one process, setup some object it wants to expose using Appdomain.SetData, another app in another process can use IcorPublish to enumerate all the appDomain in the system and find out the particular domain it is interesting. Get the AppDomainID, from the AppDomainID, get the AppDomain Object, using AppDomain.GetData get the Object, casting the Object to an interface pointer and use it. Of course I know that I could achieve the same thing with .NET Remoting, but it seem to me that if I could somehow get the AppDomain Object from the AppDomainID, it will be much simpler than using Remoting. It doesn't sound simpler! Remoting is very easy to use at a Hello World level, and that is perfectly adequate for many applications. It also supports additional complexity (lease management, channel sinks, &c) for the apps that need it. It's documented and supported; there are users out there who've probably solved any problem you'll run into. Seems a lot simpler than building your own infrastructure and increasing your reliance on (ugh!) COM. -- .NET 2.0 for Delphi Programmers www.midnightbeach.com/.net Delphi skills make .NET easy to learn Great reviews & good sales. |
#12
| |||
| |||
|
|
Basically, I want to use it as COM Global Interface Table, one app Appdomain running in one process, setup some object it wants to expose using Appdomain.SetData, another app in another process can use IcorPublish to enumerate all the appDomain in the system and find out the particular domain it is interesting. Get the AppDomainID, from the AppDomainID, get the AppDomain Object, using AppDomain.GetData get the Object, casting the Object to an interface pointer and use it. |
#13
| |||
| |||
|
|
"John" <johnxhc (AT) yahoo (DOT) com> wrote in message news:1158160939.979310.289370 (AT) e63g2000cwd (DOT) googlegroups.com... | Basically, I want to use it as COM Global Interface Table, one app | Appdomain running in one process, setup some object it wants to expose | using Appdomain.SetData, another app in another process can use | IcorPublish to enumerate all the appDomain in the system and find out | the particular domain it is interesting. Get the AppDomainID, from the | AppDomainID, get the AppDomain Object, using AppDomain.GetData get the | Object, casting the Object to an interface pointer and use it. You can't use this ITF pointer in another domain, you need a remoting proxy. The pointer is only relevant for the Apllication Domain it's born in (even if in the same process). You need to use remoting, or create your own proxy, but what makes you thing it will be simpler than using Remoting. Willy. |
![]() |
| Thread Tools | Search this Thread |
| Display Modes | |
| |