Mark
7/15/2004 11:23:00 PM
Ok, the problem was an assembly used by the SAO object, even though it is only used internally in the method, dllhost was trying to resolve it and couldn't.
interface IService{
byte[] Method(string param, enum param, string param);
}
SAO object: IService
byte[] Method (string param, enum param, string param)
....do some stuff
use DataEngine to get data via IDataEngine...
create byte[]
return byte[]
client class{
Iservice s = Activator.GetObject(typeof(IService), url);
The IDataEngine interface and implementation class (DataEngine) are in separate assemblies that are referenced by the SAO object, but not by the IService assembly. What I don't understand is that it being a SAO, singlecall object, why would the remoting client try to load the DataEngine assembly? In this circumstance the host is COM+ so I see logs of dllhost unable to resolve DataEngine. Since the remoting client only gets the IService interface, what is causing it to try to resolve the DataEngine, but not the SAO assembly? The sequence of events appears to be;
COMInterop creates remoting SAO
remoting SAO object calls to DataEngine
remoting SAO completes successfully returning a byte[]
COMInterop throws an exception trying to load DataEngine assembly