I didn't see where this had been discussed before, so please forgive me if this is a duplicate.
I would like to be able to elegantly handle exceptions across the HttpInvoker remoting interface. After an exhaustive search, I decided to wrap the exceptions that occur on the server side up in a serializable object and make this wrapper object the universal return value for all of my service methods. On the client side, I've created proxies that unwrap the object and either re-throw the appropriate exception or return the value that would have normally been expected. The problem is that this just feels very clunky and it's not very elegant for creating lots of services.
Has anyone else found a good way to handle this problem?