We really do want to follow up on this. It's high on our agenda for the coming months. Just have to roll up the sleeves ...

 

Perhaps you could give us another episode where you finish the error handling examples and move the persistent code to the model from the view model.  In the error handling why not also write out a custom error to your log, just so we can see how it is done.

 

I also would like to see how you could do all the same stuff you are doing with the form, but instead with a datagrid, two datagrids in fact, for both the parent and child.

 

And finally when you have the parent/child relationship how would you manage add/delete/change to both the parent and child on the same screen.  In my case, modify customer or shipto, or add or delete a ship to, why not?

 

The customer and ship to tables are my simple test of two interalated tables, to see how your product can be used in real life.