Error handling in WCF

There are 2 ways of handling errors in WCF.

1. Set the behavior property to enable client side to get the server error

you can add this XML delaration to your behavior.

1. <serviceDebug includeExceptionDetailInFaults="true"/>

Then you can throw your exception like this

1. throw new Exception("My Simple exception!");

At client side, you can capture the error using

1. try
2.             {
3.                 calling server operation....
5.             }
6.             catch (FaultException fe)
7.             {
8.                 MessageBox.Show(fe.Message);
9.             }

The wead point for this method to handle the error is that, any error will be throw to client side, it may include some key information of the server which is not safe. The better way of doing this is to encapsual the error to a SOAP error.

Now i will introduce the second way of handling error

 

1. Define your own error class.

 

1. [DataContract]
2.     public class FaultClass
3.     {
4.         private string info;
5.         public FaultClass(string message)
6.         {
7.             this.info = message;
8.         }
10.         [DataMember]
11.         public string msg
12.         {
13.             get { return info; }
14.             set { info = value; }
15.         }
16.     }

2. In your service operations, you have to register your error like this,

1.  [ServiceContract(SessionMode = SessionMode.Required)]
2.     public interface IServiceClass
3.     {
4.         [OperationContract]
5.         [FaultContract(typeof(FaultClass))]
6.         string GetText();
7.     }

3.After this, you can throw the exception in your service operation

1. throw new FaultException<FaultClass>(new FaultClass("My SOAP fault"));

4. Then at client side, you can catch the error:(Please add service reference firstly.)

1. try
2.             {
3.                 Calling service operation...
5.             }
6.             catch (FaultException<TCP.FaultClass> ex)
7.             {
8.                 MessageBox.Show(ex.Detail.msg);
9.             }