I have two app domains in my application: domain A and domain B. When application starts an object in A (objA) instantiates an object in B (objB) and calls a few methods on it. While application is running there are no calls from objA to objB. When application shuts down objA calls a method on objB. If application runs for some time (I have not figured out yet exact numbers) a last call from objA to objB throws RemotingExeption: "Object 'blah-blah' has been disconnected or does not exist at the server." I overwrote InitializeLifetimeService to return null and now it seems to work with no exceptions. So my questions are:
1. After reading the article http://msdn.microsoft.com/msdnmag/issues/03/12/LeaseManager/ I was under impression that if app domains are in the same process you do not have to manage leases. Where am I wrong? 2. Is it correct to do the way I did (returning null from InitializeLifetimeService)? Wouldn't it prevent objects from being garbage collected? Thank you, Alex =================================== This list is hosted by DevelopMentor® http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com
