versioning - approaches to WCF service version control -

we implementing numerous services in our company , running versioning issues data contracts. 1 of problems have our data contract used model of actual application behind service. wondering approach others have taken in kind of situation or service versioning in general. aware of microsoft best practices guide wanted see if has other ideas on how version.

the first rule of services, business object != message object. basicly, never expose business objects data contracts. or say, can't fax cat. can send facsimile of cat, can't send cat on wire. here's great picture remind you: http://www.humorhound.com/2009/04/demotivational-poster-youre-doing-it-wrong/

in more modern terms, mvvm pattern. view of model domain layer uses not built client, have create separate model , view other layers. yes seems lot more work, in end easier , better way build service oriented applications. versioning 1 of ways makes life easier. other important thing tend build models geared around how going used, , wind more explict code (less crazy branching).