开发者

DataMember vs DataMemberAttribute

开发者 https://www.devze.com 2023-03-06 11:54 出处:网络
[DataContract] public class SearchResults { [DataMember] public List<SearchDetail> PList { get; set; }
[DataContract]
public class SearchResults
{
    [DataMember]
    public List<SearchDetail> PList { get; set; }
    [DataMemberAttribute]
    public int Co开发者_如何学Gount { get; set; }
}

The metadata for DataMember and DataMemberAttribute are same.

Is 'DataMember' just an alias of the other? Which one should we be using? (If possible please provide a link)


By convention, all attribute names end with Attribute. However, several languages that target the runtime, such as Visual Basic and C#, do not require you to specify the full name of an attribute. For example, if you want to initialize System.ObsoleteAttribute, you only need to reference it as Obsolete.

Source - https://learn.microsoft.com/en-us/dotnet/standard/attributes/applying-attributes

It is same and for all the attribute in .Net Framework it is applicable. Ex. Serializable


Yes, the 'Attribute' on the attribute name is optional. Use whatever makes you happy.

Attributes on MSDN (See the Note 2/3rd's down)

Note

By convention, all attribute names end with the word "Attribute" to distinguish them from other items in the .NET Framework. However, you do not need to specify the attribute suffix when using attributes in code. For example, [DllImport] is equivalent to [DllImportAttribute], but DllImportAttribute is the attribute's actual name in the .NET Framework.


You can use any attribute with the ending -Attribute in .NET, i.e. to use the full name of the attribute type. Just to keep it simple, the ending is allowed to be omitted.

0

精彩评论

暂无评论...
验证码 换一张
取 消