Comments on: WCF Data Contracts and "k__BackingField" Property Naming

By: Nathan

Nathan — Wed, 23 Feb 2011 17:35:05 +0000

@TheDude
@Code Njnja

You bet! Thanks!

HAH! I just watched “The Big Lebowski” the other night for the first time since it came out.. Hilarious.

By: TheDude

TheDude — Wed, 23 Feb 2011 17:25:45 +0000

I dont normally post replies to stuff like this – but this saved me a lot of time. Thank you.

By: Code Njnja

Code Njnja — Fri, 11 Feb 2011 19:21:40 +0000

Thanks Nathan!!

By: Mickey

Mickey — Thu, 10 Feb 2011 11:39:30 +0000

Great explanation.

One point though, – you’d mentioned that the reason for the k_backingfield append is because it uses System.RunTime.Serialization instead of System.Xml.Serialization. On the svcutil tool, you can specify the type of serialization, and I tried it with System.Xml.Serialization and that too generates properties with the _kbacking field, so looks like it may not be down to the type of serialization after all.

By: Whats Cooking

Whats Cooking — Fri, 17 Sep 2010 00:01:33 +0000

thanks for this tip, [DataMember] was just the simple solution i was looking for.

By: Hector

Hector — Mon, 24 Aug 2009 15:44:13 +0000

Great!

By: nathan

nathan — Fri, 29 May 2009 03:24:21 +0000

@The Wolf Cool thanks. Yeah that makes sense. I thought it seemed a bit redundant.

By: The Wolf

The Wolf — Thu, 28 May 2009 21:12:34 +0000

I don’t think you need the [Serializable] attribute with DataContracts. Because of the potential for cyclical references in Entities (which serialize does not handle if i remember correctly), I always try and use DataContracts over the SerializableAttribute.