Clarification may be needed. You used these phrases: "I use LoadFrom", "I make a call to one of these remotable types from a remote client", and "ignored by the host."
Am I right that the computer that called LoadFrom is the host, and that another machine (not the one that called LoadFrom) is the remote client? What did you do to "register the remotable types [in the loaded assembly]" on the host? How did the remote client specify what type was to be accessed? (Which version of Activator.CreateInstance, or other API, is being called?) Were you trying to call a static method of a type, or did the remote client create an object of that type? I might not have the answer to your question, but I'm sure that this info might help someone figure out what might be going wrong. At 11:58 AM 1/12/2004, Andy Smith wrote >I use LoadFrom() to load an assembly and register the remotable types >included therein. I make a call to one of these remotable types from a >remote client and it fails UNLESS I put the assembly in the same directory >as the host (executable). It's as if the path that was provided for the >LoadFrom() is ignored by the host when it comes time to actually service a >remoting call. But this seems odd, doesn't the assembly stay loaded after >my LoadFrom() call? Why would it have to look for the DLL file, since I >already loaded it? I must be missing something... > >Thanks! > >Andy J. Merrill / Analytical Software Corp =================================== This list is hosted by DevelopMentor� http://www.develop.com Some .NET courses you may be interested in: NEW! Guerrilla ASP.NET, 26 Jan 2004, in Los Angeles http://www.develop.com/courses/gaspdotnetls View archives and manage your subscription(s) at http://discuss.develop.com
