Timeline for wcf deserialize enum as string
Current License: CC BY-SA 2.5
15 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 17, 2014 at 14:52 | comment | added | Alex | I don't even remember, this was over four years ago. | |
| Jul 17, 2014 at 13:02 | comment | added | nawfal | @Alex are you using DataContractSerializer or DataContractJsonSerializer ? | |
| Jul 17, 2014 at 12:56 | comment | added | nawfal | @Alex the accepted policy of SO is that you can close the older q with the newer one if latter has-received-more attention/is-better-worded etc. That said I retract my close vote because this is about DataContractSerializer in WCF context while the other is about JavascriptSerializer in ASP.NET. I should be more careful! :) | |
| Jul 17, 2014 at 12:45 | comment | added | Alex | @nawfal If you pay attention, you'll see that this question was asked two months before the one you're referring to. If anything, that one is a possible duplicate of this one. | |
| Jul 17, 2014 at 8:44 | review | Close votes | |||
| Jul 17, 2014 at 13:01 | |||||
| Jul 21, 2013 at 9:01 | comment | added | Michael Freidgeim | Try to avoid expose enums in wcf data contracts because they create subtle backwards compatible problems. See stackoverflow.com/questions/326339/… | |
| Jul 1, 2011 at 7:54 | answer | added | MHALottering | timeline score: 1 | |
| Jan 28, 2010 at 7:21 | history | edited | Alex | CC BY-SA 2.5 | Added comment about the impossibility of what I want to do to the end of the question |
| Jan 28, 2010 at 7:15 | vote | accept | Alex | ||
| Jan 27, 2010 at 21:46 | answer | added | Simon Gill | timeline score: 8 | |
| Jan 27, 2010 at 12:55 | comment | added | GaussZ | Yes 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. | |
| Jan 27, 2010 at 12:00 | comment | added | Alex | The 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. | |
| Jan 27, 2010 at 9:53 | comment | added | GaussZ | Have 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? | |
| Jan 23, 2010 at 1:36 | answer | added | user220583 | timeline score: 0 | |
| Jan 22, 2010 at 22:29 | history | asked | Alex | CC BY-SA 2.5 |