OK, I guess only he/she knows.

But it's strange ... I got an answer to this question yesterday and it was a perfectly fine answer. And it was the only answer I had. Decided to wait a day before accepting it (per this discussion). So I log back in today and it's gone.

I've seen answers deleted before if a "better" one has appeared or if there's a problem with the answer. However in this case ... no reason I can see to dump the answer.

  • 5
    Looks like the answer was technically incorrect. If the answerer realises this, the correct thing to do is delete the answer (or correct it, of course). – nb69307 Feb 5 '10 at 11:50
  • Now if only we can figure out why people answer in comments... :-) You got your upvote anyway. – tvanfosson Feb 5 '10 at 11:52
  • I made it a comment because I wasn't sure that this was the reason - I'm not an expert in the area of the original SO question. – nb69307 Feb 5 '10 at 11:59
  • @Neil -- I see, but it's still an answer -- and it's correct. I did add a smiley. – tvanfosson Feb 5 '10 at 12:09
  • @neil but now you know it's correct ... – Unsliced Feb 5 '10 at 12:10
  • You shouldn't have waited... meta.stackexchange.com/questions/38090/… – juan Feb 5 '10 at 13:26

For those who can't see the original answer, it indicated that the NonSerialized attribute couldn't be applied to fields because it was meant for binary serialization, which is only partly true and it looks like the answer was deleted after someone commented that it was incorrect. I've added what, I think, is the correct answer -- XmlIgnore is only processed by an XmlSerializer and if doing binary or SOAP serialization, you need to use NonSerialized.

  • thanks for both answers – hawbsl Feb 5 '10 at 19:26

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .