title: Entity Framework - WCF - Enums?
body: <p>I was wondering how people are handling the lack of Enum support in Entity Framework when dealing with WCF services?  </p>
  
  <p>Common practice seems to be to declare getter &amp; setter in the entity property to private and then create a partial class for the entity and declare the enum property in there.  </p>
  
  <p>This is all fine and dandy but poses an issue for WCF services. I need the Enum definition on the client side and want this to happen through the automatic proxy generation. To do so I have to add the DataMember attribute to the Enum Property in the shared class, so it will be included in the serialization process.<br>
  However, when I call a the WCF method now, it serializes both, the (int) and (Enum) property, thus carrying redundant data and increasing message size.
  What's the best way to deal with this and how are other people handling this scenario?</p>
  
  <p>Thanks,</p>
  
  <p>Tom</p>