TopDog74 wrote:
What are the common ways to approach change tracking with this kind of setup?
Ideally I'd like to keep the WCF service with the simple DTO's but also ensure that when i 'Update' an Entity that only the changed properties get saved.
AFAIK, when a DTO is sent to your web method, you should fetch the entity then set all the fields from the DTO to the entity, then save the entity, that way, only the updated fields are sent to the DB, this is also a good place to know whether the entity is new or not.
TopDog74 wrote:
I think in NHibernate you can map the contract back to an entity and 'Merge' it into a data context. Does something like this exist in LLBLGen?
What do you mean by 'context' and How does it NH?
This scenario is similar to MVC, where the view doesn't know about changes, it only render fields, and send them back to the controller, and at that point the controller doesn't know the entity state, it only know the fields that the view sent, you need an extra step (fetch) to recover the entity state.