Nov 07, 2007 - 03:23 AM
Hope you've been doing well...
The short answer is that the gridview has built-in control for sorting and paging where the datagrid required three poodles, a ring of fire and the sacrifice of a small child to get it to do those "routine" tasks.
For a more detailed accounting of the differences, take a look at http://msdn.microsoft.com/msdnmag/iss...
From personal experience, the gridview is more flexible, but it still carries a lot of "weight" as a trade-off for that flexibility. I've been doing a lot more with repeaters because they're smaller in overhead and still offer a good portion of the features a gridview has...unless I'm going to do sorting or paging. Then, mostly for the ease with the built-in features, I'm using the gridview.
Hope this helps!
Nov 08, 2007 - 07:39 AM
i somehow thought there was "more" to it, but then again, having sorting and paging integrated and better than the datagrid is a good deal also...
here's the points...
Feb 07, 2010 - 07:51 PM
2.Code requires to handle the PageIndexChanged.
3.Need extensive code for update operation on data.
4.When compared to gridview less events supported.
1.No code required.
2.No code required for PageIndexChanged.
3.Needs little code for update operation.
4.GridView supports events fired before and after database updates
Dec 28, 2010 - 08:37 PM
Dec 14, 2014 - 09:32 PM