HighTechTalks DotNet Forums  

How to get the Appdomain Object from AppDomain ID

Dotnet Framework (CLR) microsoft.public.dotnet.framework.clr


Discuss How to get the Appdomain Object from AppDomain ID in the Dotnet Framework (CLR) forum.



Reply
 
Thread Tools Search this Thread Display Modes
  #11  
Old   
John
 
Posts: n/a

Default Re: How to get the Appdomain Object from AppDomain ID - 09-13-2006 , 03:38 PM






no, not , I am not using COM, when I talk about COM GIT, I am talking
about I want to using the feature similiar to COM GIT, what I want to
do has nothing to do with COM.
I still beleive that if somehow I could get the AppDomain Object from
an AppDomain ID, it will be much easier than the remoting, because all
I need to do is the following

1) AppDomain app=GetAppDomainFromAppDomainID();
2) IMyInterface imf =(IMyInterface )app.GetData();
3) imf.method1();



Jon Shemitz wrote:
Quote:
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.


Reply With Quote
  #12  
Old   
Willy Denoyette [MVP]
 
Posts: n/a

Default Re: How to get the Appdomain Object from AppDomain ID - 09-14-2006 , 04:21 PM







"John" <johnxhc (AT) yahoo (DOT) com> wrote

Quote:
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.




Reply With Quote
  #13  
Old   
John
 
Posts: n/a

Default Re: How to get the Appdomain Object from AppDomain ID - 09-14-2006 , 07:00 PM



The remoting proxy is automatically created for you when you get the
object reference from another domain.

(I just need to get the AppDomainObject from AppDomainID from another
process.)

I already got it work if the AppDomain is is in the same process , the
following code is working:

Interface Project

using System;
using System.Collections.Generic;
using System.Text;

namespace Ginterface
{
public interface ITest
{
string GetName();

}
}



Object Project
using System;
using System.Runtime.Remoting;
using System.Collections.Generic;
using System.Text;

namespace plugin
{
public class test : System.MarshalByRefObject ,Ginterface.ITest
{
public string GetName()
{

return "John";
}
public test()
{
AppDomain.CurrentDomain.SetData("Name", this);
}

}
}
Client Project

static void Main(string[] args)
{

AppDomainSetup setup = new AppDomainSetup();
setup.ApplicationName = "TestApp";
setup.ApplicationBase =
setup.PrivateBinPath =
AppDomain.CurrentDomain.BaseDirectory;//@"C:\Project\testAppDomainCsharp\plugin\bin\Debug" ;
AppDomain app=AppDomain.CreateDomain("Test",null,setup);

ObjectHandle
oh=app.CreateInstanceFrom(@"C:\Project\testAppDoma inCsharp\plugin\bin\Debug\plugin.dll",
"plugin.test");
Ginterface.ITest ttx=( Ginterface.ITest )app.GetData("Name");
string x2 = ttx.GetName();



}
Willy Denoyette [MVP] wrote:
Quote:
"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.


Reply With Quote
Reply




Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.4
Copyright ©2000 - 2008, Jelsoft Enterprises Ltd.