Why do I have to implement set-method on properties?

Question

I noticed that the following code:

public Stringification { get { ":)"; } }

doesn't expose the property when creating an auto-generated client for WCF communication. However, if I explicitly add the set method as follows:

public Stringification { get { return SomeProperty + "!"; } set { } }

it works dandy. Is it a limitation of WCF? Is it documented anywhere? I couldn't find any info on that...

http://stackoverflow.com/a/2323289/1714342, here's explained — Kamil Budziewski, Jul 08 '13 at 09:46
Someone please answer to get the reputation, or I'll assume that the question should be closed/deleted. :) — Konrad Viltersten, Jul 08 '13 at 09:54
http://stackoverflow.com/questions/172681/wcf-datacontracts Already answered — Ehsan, Jul 08 '13 at 09:59

score 1 · Accepted Answer · answered Jul 08 '13 at 09:58

1

This is a limitation of WCF. It needs the set for the deserialization hence the set should be implemented for the get to work.

answered Jul 08 '13 at 09:58

ranieuwe

1 Answers1