Lets say the machine application B is running on is powered off. It would then be impossible to make application B robust enough to keep running... So, the problem must be solved in application A, but thanks anyway.
Normally a failing asynchronous operation would cause an exception to be thrown from EndOperation, not from BeginOperation as the case is here. I am aware that I could create a workaround by catching and storing the exception when BeginOperation is called, and wrap and throw from EndOperation. But that would require me to create an implementation of IAsyncResult so it is a quite extensive workaround. I have discovered a solution that works if the contract implementation object is created as a callback contract by WCF: The OperationContext.Current.Channel provides Closing, Closed and Faulted events! I cant find any good solution when the contract is created by application A. The same events should be accessible in the API somewhere. =================================== This list is hosted by DevelopMentor® http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com
