Message, DataContracts: versioning use of order property

Topics: Service Factory Modeling Edition Forum
Jan 23, 2007 at 8:22 AM
The Order property of the MessageBodyMember and the DataMember attributes should be configurable to set the version number to apply when adding new contract members. Now the Order starts at zero and increments by one for each member. This is not according to the Microsoft recommended "best practices" usage of the Order property wrt versioning.
Jan 23, 2007 at 8:27 AM
Hi KjellSJ,
I would like to add this behaviour in our customFactory, could you please give me some hint of where to find more information on this versioning best practice ?

Jan 23, 2007 at 10:02 AM
Data contract versioning best practice (item 8.3 is about 'Order'):

Message best practice:

Feb 7, 2007 at 6:11 PM
In the WSSF code there is the complete opposite implementation, there are also unit tests that checks if data contract members have same order and fails consequently. So what is the "best" way to follow ?