I'm stuck with a bit of an annoying problem right now. I've got a Silverlight 4 application (which runs OOB by default). It uses WCF with net.tcp as means of communicating with the server. The client uses a central instance of the wcf client proxy. As long as everything keeps running on the server side, everything's fine.

If i kill the server in the middle of everything, i drown in an avalanche of exceptions on the client side (connection lost, channel faulted etc etc).

Now i'm looking for a way to handle this in a clean and centralized way (if centralized is possible).

The SL app has one central client object sitting in App.cs (public static MyClient Client { get;set;}), which gets initialized on application start.

Any idea how to properly handle any connectivity problems on the client object?