You are implementing an N-tier application that will include WCF services. Services will transmit EF entities between tiers and the object context will not be available on the tier that modifies the entities. You need to ensure that service code can easily detect changes made to submitted entities when not attached to the object context.
What should you do?

An object context is responsible for tracking changes in the entities in an object graph. However, in N-tier scenarios, the object context might not be available on the tier that modifies the entities.

The ADO.NET Self-Tracking Entity Generator Template generates the entity types and a helper class that contains the change-tracking logic that is used by self-tracking entities and the extension methods that allow setting state on self-tracking entities.