The following simple code example illustrates the scenario in question. I have a Person entity, which is simply mapped to the Person table in the DB. I am using the default Enti
Have you tried using composition instead of inheritance?
public class PersonViewModel {
public Person Person { get; }
public int? MyViewProperty { get; set; }
// ...
}
Unless there's a really good reason I would never transfer that object to your service however. To me that looks like a client side object only. What's the point of having GUI properties transmitted to the server when they're not stored in the database anyway? Isn't it enough to just get the Person and send that to the server for update?