faulted

After reading information about task and exepcion management, I am using this code to manage an exception thrown in a Task: Task<Object> myTask = Task.Factory.StartNew<Object>(doTask, CancellationToken.None, TaskCreationOptions.None, TaskScheduler.Default); myTask .ContinueWith(task => afterTask(task), TaskScheduler.FromCurrentSynchronizationContext()); Where doTask and AfterTask are: private <Object> doTask() { throw new Exception("BOOM"); } private afterTask(Task<Object> aTask) { if (aTask.IsFaulted) { MessageBox.Show(aTask.Exception.InnerException.Message); } else //whatever } When

In my WCF client class I'm handling the Faulted() event so that if the remote service throws an exception and faults the channel I can still at least shut it down gracefully. Here's my code: protected void RemoteDataRetriever_Faulted(object sender, EventArgs e) { (sender as ICommunicationObject).Abort(); this.Dispose(); throw new ChannelTerminatedException("The remote service threw an unhandled exception and as a result the channel has been closed."); } So what I would expect is that the client can handle the ChannelTerminatedException that I've thrown manually and send a message to the user,

I have encountered a very interesting behavior of reliable session. I am using netTcp binding + duplex channel + reliable session. When I am trying to listen on channel.faulted , if there is security mode is set to transport , faulted event would fire immediately when client disconnects. However when I set binding's security mode to None or Message, faulted event no longer fires in the same situation. They will eventually get faulted half of ReciveTimeout on server side which I understands as reliable session would send a heart beat message at that time. The question is: Why the wcf binding

When a single ClientBase<T> instance is used for multiple WCF service calls, it can get a channel into a faulted state (ie. when the service is down). I would like to heal the channel automatically when the service comes up again. The only way I found is to call the following code before each method call: if (clientBase.InnerChannel.State == CommunicationState.Faulted) { clientBase.Abort(); ((IDisposable)clientBase).Dispose(); clientBase = new SampleServiceClientBase(); } I got the feeling that this isn't the right way to do it. Anyone got a better idea? Aaronaught You can't. Once a channel is