Gridview rowupdating event handler
The Grid View does know the events that should be used to implement them, so the exceptions shown above are thrown when you try to perform one of these operations, but you have implemented the appropriate event handler.
The example shown here is for a Grid View, but the same types of event handlers must be implemented in roughly the same way for other data controls including the Form View, Details View, and List View. This is the final Grid View markup, so you can see the event handlers we’re going to implement.
We’ll get to how these properties are populated shortly, but first we need to go back to the Bind Data method.
The original method shown above did not implement any sorting, but now that we have a place to store the Sort Expression and Sort Direction we need to change that.
If we were using a Template Field instead, the compiler translates the markup in the templates to the appropriate types of controls in the same way as the page markup in parsed.
For this example, the Item Template would be transformed into a Literal control, and the Edit Item Template would be transformed into a Literal control, a Text Box, and a Literal control (the literal controls would include the spacing between the Edit Item Template tags and the Text Box tags).
When the Bound Field is in Edit mode, things are a little different.
Once we have a reference to the Text Box, we set the new first name.We also want it to be something persistent, so that, for example, if you sort, then page, the sort is maintained.The way we’ll accomplish this is to create two properties that store those values in View State.We also need force databinding to occur when then page is loaded, which we’ll handle in Page_Load.The required actions for paging to work are setting the new page index, setting the Data Source, and calling Data Bind (the last two through the Bind Data method).