Part 17 Unhandled exceptions in WCF HD

Link for code samples used in the demo http://csharp-video-tutorials.blogspot.com/2013/12/part-17-unhandled-exceptions-in-wcf_20.html Link for all dot net and sql server video tutorial playlists http://www.youtube.com/user/kudvenkat/playlists An unhandled exception in the WCF service, will cause the communication channel to fault and the session will be lost. Once the communication channel is in faulted state, we cannot use the same instance of the proxy class anymore. We will have to create a new instance of the proxy class. BasicHttpBinding does not have sessions. So when there is an unhandled exception, it only faults the server channel. The client proxy is still OK, because with BasicHttpBinding the channel is not maintaining sessions, and when the client calls again it is not expecting the channel to maintain any session. wsHttpBinding have secure sessions. So when there is an unhandled exception, it faults the server channel. At this point the existing client proxy is useless as it is also faulted, because with wsHttpBinding the channel is maintaining a secure session, and when the client calls again it expects the channel to maintain the same session. The same session does not exist at the server channel anymore, as the undhandled exception has already torn down the channel and the session along with it.