We are using binary .Net remoting over http for a client-server application. At the server, we have implemented custom error handling which results in the Service Interface (the facade layer) to throw a decent exception, with lots of information. The problem we encounter now is that most of the time the client displays these exceptions as BinaryFormatter exceptions, in stead of the ApplicationException or the normal Exception we throw serverside.

Does anyone have experience with this? How do we keep our rich exception when we travel to our client? Please drop me a line in the comments.