Not sure if anyone encountered this from the Learning Resources Sample for ConcurrencyConflicts.
We found Concurrency Conflicts are not handled from the following issue steps:
0. Use sample code @..\IdeaBlade DevForce\Learning Resources\040_BusObjPersistence\ConcurrencyConflicts\Samples\300WNF_WinForms\CodeCS\UI\ConcurrencyHandler.cs
1. Call ResolveMyConflicts(...) to resolve conflicts
2. Modify a field (e.g. employee-> firstname) in app1, save, "Save Succeeded".
3. Update the same field in app2, save, a messagebox of the detailed conflicts will be shown, choose to save own copy, "Save Succeeded"
4. Then update the same field again in app1. No warning about conflicts, end up with "Save Succeeded" again.
Cause of problem: concurrency column(RowVersion) won't be updated by user2's SaveChanges()@step3. Which means @step4, app1 thinks its copy is the latest because of the RowVersion == the latest RowVersion in DB.
Is the above as designed?