Home/ Questions/Q 201913
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-11T17:14:27+00:00

I was reading Microsoft’s Best Practices: Data Contract Versioning , and they state: Do

  • 0

I was reading Microsoft’s Best Practices: Data Contract Versioning, and they state:

Do not remove data members in later versions, even if the IsRequired property was left at its default property of false in prior versions.

Can anyone suggest any reason for this? They don’t elaborate. Since they say it’s fine to add data members in a later version, it seems that removing would be fine too — effectively, the older version would see it as an add.

The difference, I suppose, is that you’re supposed to add new members at the end (using the Order property on the DataMemberAttribute), whereas the property getting removed would probably not be at the end. But they also say that missing members will be left at their default value during loading, so it’s clear that missing members are OK.

What am I missing? What version-interop problems would I cause (both forward-compatibility and backward-compatibility) if I obsoleted a feature of my product and removed the [DataMember] property that goes with it?

Also, if I decided that I wasn’t interested in forward-compatibility (i.e., if I wasn’t concerned about older versions opening newer files), would any such problems still apply?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Simply because outside service consumers may provide/use that data (they were created before you removed some members). In case you’ve changed service method signature, DataContractSerializer won’t be able to recognize DataContract anymore, because of unknown data members.

    So if your service consumers are all known, you can easily manipulate data members at your own will as long as you:

    • don’t break consumers or
    • properly inform them of the change
    • 0