tag:blogger.com,1999:blog-2556565917388324168.post6727498198519434087..comments2023-05-05T11:28:20.564-03:00Comments on Pampa Notes on Software Trends: How to use the Unplugged LINQ to SQL GeneratorJose Marcenarohttp://www.blogger.com/profile/05555839326427060802noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-2556565917388324168.post-28971719182029029412008-03-09T22:02:00.000-02:002008-03-09T22:02:00.000-02:00That's a big question we let unanswered (on purpos...That's a big question we let unanswered (on purpose :)), many people are creating different disconnected change tracking implementations in one of those ways:<BR/><BR/>- ClientContext (a disconnected serializable context with a portable change set) <BR/>- Entities with state (alla DataRow.RowState)<BR/><BR/>As you, We are taking the second approach (entities with state).<BR/>The reasons for this Benjamin Eidelmanhttps://www.blogger.com/profile/04340842860289810596noreply@blogger.comtag:blogger.com,1999:blog-2556565917388324168.post-22147077223937485732008-03-09T02:05:00.000-02:002008-03-09T02:05:00.000-02:00Good work guys, just wondering though in what way ...Good work guys, just wondering though in what way you were planning to do the change tracking on the client side?<BR/><BR/>I've got been working on some bits on pieces using a base class to control trange tracking + a little reflection.<BR/><BR/>My current method involves having each entity know it's state (new, modified, dirty, deleted) when disconnected, the it's a simple matter attaching them Matthew Hunterhttps://www.blogger.com/profile/15449365892205165530noreply@blogger.com