c# - What is the purpose of self tracking entities? -


i've been reading self-tracking entities in .net , how can generated *.edmx file. thing i'm struggling understand generating these entities gives on basic ef entities? also, people have mentioned self tracking entities , silverlight, why use these rather client side or shared classes generated ria services?

what point of self-tracking entities , why use them?

self tracking entities (ste) implementation of change set (previous .net implementation of change set dataset). difference between ste , other entity types (poco, entityobject) common entity types can track changes when connected living objectcontext. once common entity detached loose change tracking ability. ste solves. ste able track changes if detach objectcontext.

the common usage of ste in disconnected scenarios .net .net communication on web services. first request web service create , return ste (entity detached when serialized , objectcontext lives serve single call). client make changes in ste , pass in web service call. service able process changes because have ste internal change tracking available.

handling scenario without change tracking possible more complex when work whole object graph instead of single entity - must manually merge changes received client current state in database.

be aware stes not interoperable solutions because functionality based on sharing ste code between server , client.


Comments

Popular posts from this blog

linux - Mailx and Gmail nss config dir -

c# - Is it possible to remove an existing registration from Autofac container builder? -

php - Mysql PK and FK char(36) vs int(10) -