contracts

I have a new question for WCF gurus. So, I have a class User which is close to the 'User' representation from the DB which I use for database operations. Now, I would like to have 2 different service contracts that use this class as data contract, but each in their own way... I mean, public class DBLayer { void InsertUsers(List<User> userList) { // both 'PropertyVisibleForService1' and 'PropertyVisibleForService2' // are used HERE to be inserted into their columns } } [DataContract] public class User { [DataMember] public string PropertyVisibleOnlyForService1{...} [DataMember] public string

I have started using Code Contracts and have found that it makes it difficult to immediately spot the 'guts' of a method. Take this (very simple) example: public static void UserAddNew(string domain, string username, string displayName) { Contract.Assert(!string.IsNullOrWhiteSpace(domain)); Contract.Assert(!string.IsNullOrWhiteSpace(username)); Contract.Assert(!string.IsNullOrWhiteSpace(displayName)); LinqDal.User.UserAddNew(domain, username, displayName); } Now I'm tempted to put the contracts in a region, so that they can be hidden away, but then I'm concerned that I'm losing a nice

If I need to go from this service contract: [ServiceContract(Namespace="http://api.x.com/Svc1")] public interface IService1 { [OperationContract(Name = "AddCustomer")] bool AddCustomer(DTOCustomer1 customer); } to this: [ServiceContract(Namespace="http://api.x.com/Svc1")] public interface IService1 { [OperationContract(Name = "AddCustomer")] bool AddCustomer(DTOCustomer2 customer); } and according to this good article: Versioning WCF I understand that when data contract is changed there is a need of defining a new vs of data contract in new namespace followed by defining a new vs of service