Databases
StackOverflow2013
Postsdbo
POwcf deserialize enum as string
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POwcf deserialize enum as string
    primarykey
    data
    text
    <p>I'm trying to consume a RESTful web service using WCF. I have no control over the format of the web service, so I have to make a few workarounds here and there. One major problem I cannot seem to get around, however, is how to make WCF deserialize an enum as a string.</p> <p>This is my code (names changed, obviously):</p> <pre><code>[DataContract] public enum Foo { [EnumMember( Value = "bar" )] Bar, [EnumMember( Value = "baz" )] Baz } [DataContract] public class UNameIt { [DataMember( Name = "id" )] public long Id { get; private set; } [DataMember( Name = "name" )] public string Name { get; private set; } [DataMember( Name = "foo" )] public Foo Foo { get; private set; } } </code></pre> <p>And this is the returned data that fails deserialization:</p> <pre><code>{ "id":123456, "name":"John Doe", "foo":"bar" } </code></pre> <p>Finally, the exception thrown:</p> <blockquote> <p>There was an error deserializing the object of type Service.Foo. The value 'bar' cannot be parsed as the type 'Int64'.</p> </blockquote> <p>I do not want to switch to using the XmlSerializer, because, among its many other shortcomings, it won't let me have private setters on properties.</p> <p>How do I make WCF (or, well, the DataContractSerializer) treat my enum as string values?</p> <p><strong>EDIT</strong>: Doing this seems to be impossible, and the behavior is the way it is by design. Thank you Microsoft, for not giving us options, having to resort to hacks. Doing it the way somori suggests seems to be the only way to get string enums with JSON and WCF.</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USAlex
    1. USAlex
    plurals
    1. PL
      singulars
      1. LTLinked
    2. PL
      singulars
      1. LTLinked
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POwcf deserialize enum as string
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POwcf deserialize enum as string
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POwcf deserialize enum as string
      1. This table or related slice is empty.
      1. VTUpMod
    1. COHave you tried building a UNameIt object in code and using the DataContractSerializer to serialize (and then deserialize it) to see if maybe the serialization mismatches the message you receive?
      singulars
      1. POwcf deserialize enum as string
      1. USGaussZ
    2. COThe thing is, I'm not the one doing the serialization. This JSON comes from a third party. I can't control anything about it, the only thing I have control over is the deserialization, except I guess not, because I can't get WCF to deserialize an enum the way these guys set up enums. I wish the DataContractSerializer was more flexible.
      singulars
      1. POwcf deserialize enum as string
      1. USAlex
    3. COYes I understand that you have no control over it, it would maybe hint at the problem though if you could compare a self-serialized object with what you get from the third party to understand why the serializer does not like it.
      singulars
      1. POwcf deserialize enum as string
      1. USGaussZ
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload