Monday, January 26, 2009

Change Tracking and Conflict Management with ADO.NET Data Services

Today the msdn-solve portal released a new CodeClip of mine about Change Tracking and Conflict Management with ADO.NET Data Services.

In ADO.NET Data Services a data context needs to be notified about any changes applied to the tracked entities. It’s easy to do so when you have full control over the entity. But when the entities are bound to e.g. a DataGrid, things get more and more complicated.
View the CodeClip [German] or read the how-to-guide to learn how to use the PropertyChanged-Event to notify changes on entities.

In multi-user scenarios data is usually manipulated by many users simultaneously. How does your application know if there is new data available when trying to update the data source? Both, the clip and the guide demonstrate how eTags (timestamps) can be used to deal with conflicts using the “Optimistic Concurrency” princible.

CodeClip [German]: http://www.microsoft.com/germany/msdn/solve/codeclips/library.aspx?id=msdn_de_31212

How-To-Guide [German]: http://www.microsoft.com/germany/msdn/solve/knowhow/howto/sql/WieKannIchMitADONETDataServicesAenderungsverfolgungRealisierenUndDatenkonflikteLoesen.mspx

No comments:

Post a Comment