I'm trying to understand the concept of LivePersistence="False". In this situation, all data handling needs to be done in one of the event handlers. What do I gain by using the LLBLGenDatasource in this situation as opposed to simply writing normal code (for example, to bind a grid)?

As far as I can see, there are no examples in the documentation that show LivePersistence="False"

Hi,

I guess you know about binding a grid so you're not really looking after the events you'll have to handle with LivePersistence="False". Just like the grid events right.

Now the difference it makes is that your datasource provides a much richer link between your UI and you Collection by taking many arguments such as native llblgen boundable filter and sorter (which you'd have to make with your grid), it deals with viewstate persistence (which you'd have to painfully handle otherwise), and exposes a handful of properties, many of them design time to set up the plumbings to the LLBLGen world easily.

Now it also maintains a UOW over postbacks which you can use to easily queue modifications before you validate them.

For all those different things I think you can find bits of code a bit everywhere.

To add to that with a short: 2-way databinding. It's not possible with asp.net 1.x databinding, it is with a datasourcecontrol (and a control which supports it of course. A textbox doesn't, a formview/grid does)