Manuel Abadia's ASP.NET stuff - February, 2006

This is the last part in the ObjectDataSource tutorial. It explains the importance of setting AffectedRows, optimistic concurrency, parameter merging in detail, caching and design time attributes.

There's an example where most of the ObjectDataSource capabilities are used.

I was "playing" with the ObjectDataSource's example from Part 2 when I realized I didn't enabled client callbacks for paging and sorting. I set GridView's EnableSortingAndPagingCallbacks to true and tried it. To my surprise, it didn't work! I was confused because I had tried it that in the past and it worked without any problems so it made no sense that it wasn't working now.

Of course the first thing that comes to my head in those situations is: "There's a bug in GridView's implementation". The reality is that 95% of the time it's my own fault but one never finds himself guilty until proven wrong!

This article continues exploring the ObjectDataSource. The topics covered are paging, sorting, filtering, parameters and events.

ObjectDataSource lets you integrate your own objects in the ASP.NET data binding framework without much work. In order to do so, you have to understand the data binding infrastructure (see my previous posts if you need more info about it) and what ObjectDataSource does for you.

Another year and another Grammy that Steve Vai lost.

This is the last post in the series about data source controls and the new data binding infrastructure.

Now I’m going to explain what does the framework internally to support two way data binding.

A data binding expression is contained withing <%# and %> delimiters. Inside those delimiters you can place code that return a value, an Eval expression or a Bind expression. You have two way data binding only if you use a Bind expression.