blocks|key|316317|text|即使不需要更新值，WCFSerializer也会使用设置器来反序列化对象(并重新设置值)。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|316318|这就是你想要的：WCF+DataContracts|offset|length|316319|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/questions/172681/wcf-datacontracts^0|0|8|H|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|O|8|@]|9|@$D|P|E|Q|1|R]]|A|$]]|$1|F|3|-4|5|6|7|S|8|@]|9|@]|A|$]]]|G|$H|$5|I|J|K|A|$L|M]]]]

Even if you dont need to update the value, the setter is used by the WCFSerializer to deserialize the object (and re-set the value).

This SO is what you are after:
<a href="https://stackoverflow.com/questions/172681/wcf-datacontracts">WCF DataContracts</a>

blocks|key|313232|text|为Message提供一个公共的getter和受保护的setter，这样只有子类(和DataContractSerializer，因为它欺骗:)可以修改这个值。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|313233|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Give Message a public getter but protected setter, so that only subclasses (and the DataContractSerializer, because it cheats :) may modify the value.

blocks|key|3273071|text|你就不能有个“什么都不做”的二传手吗？|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3273072|[DataContract]
public+class+ErrorBase
{
++[DataMember]
++public+virtual+string+Message+
++{
++++++get+{+return+"";+}+
++++++set+{+}
++}
}|code-block|syntax|javascript|3273073|或者DataContract序列化程序也会对此感到厌恶？？|3273074|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|L|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|M|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

Couldn't you just have a "do-nothing" setter??

<pre><code>[DataContract]
public class ErrorBase
{
 [DataMember]
 public virtual string Message 
 {
 get { return ""; } 
 set { }
 }
}
</code></pre>

Or does the DataContract serializer barf at that, too??

blocks|key|315456|text|具有DataMember属性的属性始终需要设置。您应该在客户端应用程序上重写类似的对象，因为DataContract成员总是可以被赋值的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|315457|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Properties with DataMember attribute always requires set. You should re write simmilar object on the client application since DataContract members can always be assigned values.

blocks|key|3059788|text|我在JSON中遇到了这个问题，我想使用DataContractSerializer以便能够控制ASP.NET输出中项目的名称。最后，我将序列化程序切换到了JSON.NET，它通过[JsonProperty(PropertyName+=+"myName")]支持不带设置器的属性(+DataContractSerializer不支持)和属性名称控制(+ASP.NET+MVC中内置的JSON序列化程序不支持)。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|3059789|entityMap^0|2H|13|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|K|8|@]|D|@]|E|$]]]|G|$]]

I had this problem with ASP.NET MVC and me wanting to use DataContractSerializer in order to be able to control the names on the items in the JSON output. Eventually I switched serializer to JSON.NET, which supports properties without setters (which DataContractSerializer doesn't) and property name control (which the built-in JSON serializer in ASP.NET MVC doesn't) via <code>[JsonProperty(PropertyName = "myName")]</code>.

blocks|key|3273136|text|如果这是一个可行的选择，那么将其定义如下，而不是将ErrorBase作为基类：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|3273137|++++public+interface+IError
++++{
++++++++string+Message
++++++++{
++++++++++++[OperationContract]
++++++++++++get;

++++++++++++//+leave+unattributed
++++++++++++set;
++++++++}
++++}|code-block|syntax|javascript|3273138|现在，即使存在setter，客户端也无法通过WCF通道访问它，因此它就像是私有的一样。|3273139|entityMap^0|P|9|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@$9|P|A|Q|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|R|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|S|8|@]|D|@]|E|$]]|$1|M|3|-4|5|6|7|T|8|@]|D|@]|E|$]]]|N|$]]

If it's a viable option, then instead of having <code>ErrorBase</code> as the base class, define it as follows:

<pre><code> public interface IError
 {
 string Message
 {
 [OperationContract]
 get;

 // leave unattributed
 set;
 }
 }
</code></pre>

Now, even though a setter exists, it's inaccessible to the client via WCF channel, so it's as if it were private.

blocks|key|3273146|text|[DataMember(Name+=+"PropertyName")]
public+string+PropertyName
{
++++get
++++{
++++++++return+"";
++++}
++++private+set
++++{+}
}|type|code-block|depth|inlineStyleRanges|entityRanges|data|syntax|javascript|3273147|unstyled|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|G|8|@]|9|@]|A|$B|C]]|$1|D|3|-4|5|E|7|H|8|@]|9|@]|A|$]]]|F|$]]

<pre><code>[DataMember(Name = "PropertyName")]
public string PropertyName
{
 get
 {
 return "";
 }
 private set
 { }
}
</code></pre>

blocks|key|3273207|text|如果你只有一个getter，为什么你需要序列化这个属性呢？似乎您可以删除只读属性的DataMember属性，而序列化程序只会忽略该属性。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3273208|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

If you only have a getter, why do you need to serialize the property at all. It seems like you could remove the DataMember attribute for the read-only property, and the serializer would just ignore the property.

blocks|key|3273255|text|如果序列化程序的类型为DataContractJsonSerializer+(或任何DataContractSerializer)，则还可以在构造函数中使用DataContractSerializerSettings，并将SerializeReadOnlyTypes属性设置为true。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|3273256|entityMap|0|LINK|mutability|MUTABLE|url|https://docs.microsoft.com/en-us/dotnet/api/system.runtime.serialization.json.datacontractjsonserializer?view=netframework-4.6.2|1|https://docs.microsoft.com/en-us/dotnet/api/system.runtime.serialization.datacontractserializer.-ctor?view=netframework-4.6.2#System_Runtime_Serialization_DataContractSerializer__ctor_System_Type_System_Runtime_Serialization_DataContractSerializerSettings_|2|https://docs.microsoft.com/en-us/dotnet/api/system.runtime.serialization.datacontractserializersettings?view=netframework-4.6.2|3|https://docs.microsoft.com/en-us/dotnet/api/system.runtime.serialization.datacontractserializersettings.serializereadonlytypes?view=netframework-4.6.2#System_Runtime_Serialization_DataContractSerializerSettings_SerializeReadOnlyTypes^0|B|Q|16|M|26|U|33|M|B|Q|0|16|M|1|26|U|2|33|M|3|0^^$0|@$1|2|3|4|5|6|7|T|8|@$9|U|A|V|B|C]|$9|W|A|X|B|C]|$9|Y|A|Z|B|C]|$9|10|A|11|B|C]]|D|@$9|12|A|13|1|14]|$9|15|A|16|1|17]|$9|18|A|19|1|1A]|$9|1B|A|1C|1|1D]]|E|$]]|$1|F|3|-4|5|6|7|1E|8|@]|D|@]|E|$]]]|G|$H|$5|I|J|K|E|$L|M]]|N|$5|I|J|K|E|$L|O]]|P|$5|I|J|K|E|$L|Q]]|R|$5|I|J|K|E|$L|S]]]]

If your serializer is of type <a href="https://docs.microsoft.com/en-us/dotnet/api/system.runtime.serialization.json.datacontractjsonserializer?view=netframework-4.6.2" rel="nofollow noreferrer"><code>DataContractJsonSerializer</code></a> (or any <a href="https://docs.microsoft.com/en-us/dotnet/api/system.runtime.serialization.datacontractserializer.-ctor?view=netframework-4.6.2#System_Runtime_Serialization_DataContractSerializer__ctor_System_Type_System_Runtime_Serialization_DataContractSerializerSettings_" rel="nofollow noreferrer"><code>DataContractSerializer</code></a>) you can also use <a href="https://docs.microsoft.com/en-us/dotnet/api/system.runtime.serialization.datacontractserializersettings?view=netframework-4.6.2" rel="nofollow noreferrer"><code>DataContractSerializerSettings</code></a> in the constructor, with the <a href="https://docs.microsoft.com/en-us/dotnet/api/system.runtime.serialization.datacontractserializersettings.serializereadonlytypes?view=netframework-4.6.2#System_Runtime_Serialization_DataContractSerializerSettings_SerializeReadOnlyTypes" rel="nofollow noreferrer"><code>SerializeReadOnlyTypes</code></a> property set to true.

I have some class that I'm passing as a result of a service method, and that class has a get-only property:

<pre><code>[DataContract]
public class ErrorBase
{
 [DataMember]
 public virtual string Message { get { return ""; } }
}
</code></pre>

I'm getting an exception on service side:

<blockquote>
 System.Runtime.Serialization.InvalidDataContractException: No set
 method for property 'Message' in type 'MyNamespace.ErrorBase'.
</blockquote>

I have to have this property as only getter, I can't allow users to assign it a value. Any workaround I could use? Or am I missing some additional attribute?

WCF chokes on properties with no "set ". Any workaround?

JSON

我有一些作为服务方法的结果传递的类，这个类有一个get-only属性：[DataContract]public class ErrorBase{  [DataMember]  public virtual string Message { get { return ""; } }}我在服务端得到了一个异常：“MyNam...

问WCF在没有"set“的属性上阻塞。有什么解决方法吗？
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问WCF在没有"set“的属性上阻塞。有什么解决方法吗？EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问WCF在没有"set“的属性上阻塞。有什么解决方法吗？
EN