Exposing Enums In WCF To Client Application

This article explains how to expose enums used in WCF Service to the clients who consume our Service.

Create a WCF Service and create an enum inside it.

[DataContract]
    public enum Status
    {
        [EnumMember]
        Open,
        [EnumMember]
        InProgress,
        [EnumMember]
        Done,
        [EnumMember]
        Close
    }

We need to decorate enum with [DataContract] attribute and each member with [EnumMember] attribute, if we want them to be visible on the client end. These attributes can be found in System.Runtime.Serialization namespace.

 

We just need to make sure that we use that enum in our WCF Service, otherwise you will not find it on the client side. Below we have defined GetDataStatus as an operation contract, which takes our Status enum as a parameter. 

[ServiceContract]
    public interface IService1
    {
        [OperationContract]
        string GetDataStatus(Status state);

    }

Following is the implementation of GetDataStatus method in class, which implements IService1 interface. 

public class Service1 : IService1
    {
        public string GetDataStatus(Status state)
        {
            if (state == Status.Open)
            {
                return "Status Open";
            }
            if (state == Status.Done)
            {
                return "Status Done";
            }
            return string.Empty;
        }
    }

Now, we are done with our WCF Service. We need an application which consumes WCF Service. For this, I have created a console application and added reference of our WCF Service in it and written the code given below in it. 

class Program
    {
        static void Main(string[] args)
        {
            ServiceReference1.Service1Client sc = new ServiceReference1.Service1Client();
            Console.WriteLine(sc.GetDataStatus(ServiceReference1.Status.Open));
            Console.ReadKey();
        }
    }

You will find that we will be able to access our Status enum on line number 06 above.

Thanks for reading and you can find the source code attached, which is used in this article.