LLB v2.6
2.6.10.809 (SD.LLBLGen.Pro.LinqSupportClasses.NET35.dll)
2.6.10.930 (SD.LLBLGen.Pro.ORMSupportClasses.NET20.dll)
2.6.10.917 (SD.LLBLGen.Pro.DQE.SqlServer.NET20.dll)
DotNet 4.0 vs2010 project
I have a DevExpress ASPxGridView working well with an LLB DS. It is all automatic with LivePersistence = false and the PerformSelect handler getting the EntityCollection and the PerformWork handler commiting the Uow. All I need to do in the grid is allow the user to click the UpdateEdit button. Great.
As this view will have hundreds of controls to update, I want to eliminate the UpdateEdit button and replace it with OnChange handlers for each editable control for a smoother user experience. This is easy with the clientside event aspxGVUpdateEdit('grid').
When UpdateEdit() is executed, it updates the data source then returns the user interface to data mode, closing the EditForm. This is a pain as I have several controls for the user to update in the EditForm. So by eliminating a single button click, I have now added a click to reopen the EditForm after every control is changed. Not so hot.
I can bypass the UpdateEdit() method altogether, and in a callback handler tell the LLB DS to update using event parameters. But then I lose the nice abstracted e.Uow.Commit(adapter,true) statement that means I don't care what has been changed as LLB DS has managed it for me. Reason to buy LLB
So, if I don't use the DevExpress UpdateEdit() method as it annoyingly does two things (updates then changes the user's viewing mode) is it possible for me in some handler to update the LLB DS without having to work out what fields were changed. I have searched the Intellisense but can't spot a way to do this yet. I wondered about doing a fake update and see if that creates the Uow object and fires the PerformWork event, but I suspect that won't include the changes the user made unless I do them manually.
Any advice on this is gratefully received. (I have also asked the DevExpress support center)