I suppose you could build a "cover" for the proxy, and have the cover handle an exception in BeginOperation. But that wouldn't really be a solution, as the other app could (theoretically) disappear at any point; whether you'd eventually get a WCF-generated "there's no one at the other end any more!" exception if that happened, I don't know.
If you're responsible for application B, I'd suggest trying to make it more robust, rather than trying to handle a subset of the possible failure modes that could potentially be detected in the caller. At 04:09 AM 7/19/2006, Ragnvald Barth wrote >How do I know when the other application is aborted? > >Application A performs asynchronous WCF calls to application B: >Just before A calls B, B disappears. >If A now calls proxy.BeginOperation(), an exception is thrown! > >An exception from BeginOperation indicates that the exception is thrown >before the operation is started. So it should be possible to detect that >the operation cant be started. > >But how? J. Merrill / Analytical Software Corp =================================== This list is hosted by DevelopMentor® http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com
