I haven't tried calling a static method except indirectly when I used
ExecuteAssembly (this invokes the static Main method in the executed
assembly). Invoking an instance method was no problem at all. From your
sample code it appears that you are still not invoking the method in the
context of the remote appdomain. You should define a class, derived from
MBRO, that implements the functionality you are using directly from the
default appdomain. The code you show here...
Assembly[] assemblies = appDomain.GetAssemblies();
Type type = assemblies[1].GetType("SampleNamespace.SampleClass", true,
false);
type.InvokeMember("Initialize"
,BindingFlags.Public | BindingFlags.InvokeMethod | BindingFlags.Static
,null
,null
,new Object[] {});
....I assume you are executing from the default appdomain. By loading a type
into the default appdomain you are loading up all the assemblies as well
into the default appdomain, and it will try to execute the method in the
default appdomain. Create a method in convertedClass and move this code
into it so that when it call the method the code is executing remotely, and
call the method via the unwrapped object handle.
This wont necessarily solve the apparent problem of not calling the static
method. What error do you get? Are any exceptions thrown?
You can also try to use AppDomian.DoCallback(). This should invoke the
method in the context of the other appdomain. Again, I haven't used it with
static methods.
Chris Mouton said:
Hi David,
Thank you for the link and although I've been through, I reread it to see
if I missed anything the first time. What you describing is completely
correct and it is exactly what I've done. Over the weekend I've written a
small application and dlls to simulate the situation. I tried to incorporate
all the suggestions that everybody has given me (thanks all!) but I can't
seem to be able to call the static method in the other domain. First I
thought it was a name clash, ie both AppDomain (current and loaded) has the
same signature and the static method in the current AppDomain is callled
only, but I found that I couldn't even call the static method in the loaded
AppDomain under a new name.
If anybody has any further suggestions on how to call a static method in
another (dynamicly loaded) AppDomain, please let me know. Pretty please....
Thank you
Chris Mouton
----- David Levine wrote: -----
The problem is that even though you are creating a new appdomain you are
still calling it from the context of the default appdomain. You need to
create an object derived from MarshalByRefObj, create an instance of it in
the new appdomain and then via remoting into the new appdomain call a method
in it that will create the object and then call its method. This link does a
good job of describing things, and you can google up a bunch of sample code
pretty easily.
http://www.gotdotnet.com/team/clr/AppdomainFAQ.aspx
Here is
the sample code of the DLL that I am loading and the method that I'm
calling:
AppDomainSetup setup = new AppDomainSetup();
setup.ApplicationBase = someDirectory;
AppDomain appDomain = AppDomain.CreateDomain("SampleDomain", null, setup);
Common.SampleInterface convertedClass = (Common.SampleInterface) appDomain.CreateInstanceAndUnwrap(
"SampleDLL",
"SampleDLL.SampleDLLClass");
Assembly[] assemblies = appDomain.GetAssemblies();
Type type = assemblies[1].GetType("SampleNamespace.SampleClass",
true,
false);
type.InvokeMember("Initialize"
,BindingFlags.Public | BindingFlags.InvokeMethod | BindingFlags.Static
,null
,null
,new Object[] {});
When this code is executed, the Initialize on my SampleClass from
staticly
linked DLL is called. I know this because I can have check code in the
SampleClass that says that it has not been initialized and if I look at the
Output window when in debugging mode, I can view that the wrong assemblies
are being loaded.
namespaces, one
which is your library's, and the other is your programs, then reference your
built in static method like this dynamically load
a DLL(s) into. In this newly loaded DLL I want to call a
static
method on a
class. The problem arise is that I have the same class/static method
definition statictly linked to my EXE and when I call InvokeMember(...),
even though I got the Type from the new AppDomain, it calls
the
static
method that I am staticly linked to and not the static method in the
dynamicly loaded DLL. another
AppDomain if there is duplicate definition clashes across domains?