Wrox Programmer Forums
Go Back   Wrox Programmer Forums > ASP.NET and ASP > ASP.NET 2.0 > ASP.NET 2.0 Professional
ASP.NET 2.0 Professional If you are an experienced ASP.NET programmer, this is the forum for your 2.0 questions. Please also see the Visual Web Developer 2005 forum.
Welcome to the p2p.wrox.com Forums.

You are currently viewing the ASP.NET 2.0 Professional section of the Wrox Programmer to Programmer discussions. This is a community of software programmers and website developers including Wrox book authors and readers. New member registration was closed in 2019. New posts were shut off and the site was archived into this static format as of October 1, 2020. If you require technical support for a Wrox book please contact http://hub.wiley.com
Old April 5th, 2006, 04:43 PM
Authorized User
Join Date: Jan 2006
Posts: 91
Thanks: 0
Thanked 0 Times in 0 Posts
Default Performance Penalty for Custom Code Gridview Row B

I've got a Gridview in which I am displaying several different row formats, based on row content.

I'm considering three different options for the itemtemplate design.

1) Pre-build multiple custom panels, one for each major type of row format, with the fields all positioned and formatted, and show and hide them, based on a set of rules. This would also involve the use of in-line <%# procedure calls to get certain formatted values.

2) Pre-build one panel with all the fields in it, and in, _rowdatabound, show, position, and format the fields individually, based on a set of rules (using CSS to minimize the format and position attribution, where possible.)

3) Start with an empty panel and, in _rowdatabound, add to it just the fields needed that particular row (and format and position the fields), based on a set of rules (again using CSS where it helps to do so.)

The application will involve row sets counting typically less that 100 items (could go much higher, but that would be down the road a ways in the product lifecycle).

I my view, options 2 and 3 would be easiest to work with from a coding standpoint.

My question is: would there be significant (i.e. externally noticible) performance differences among these three options?

At one level, it would seem that the page generator has to go through all the steps in any case. However, I wonder if ASP.NET has high performance internal routines that, in option 1, and to a lesser extent in option 2, would beat the pants off my custom compiled VB. (Or would that make any significant difference at the row volumes I'm contemplating?)

Any guidance on how this would be appreciated.


Similar Threads
Thread Thread Starter Forum Replies Last Post
Gridview with only one row mallikalapati ASP.NET 2.0 Professional 5 March 5th, 2008 09:27 AM
Gridview with only one row mallikalapati ASP.NET 2.0 Professional 0 February 25th, 2008 06:46 AM
GridView Performance ramuis78 ASP.NET 2.0 Basics 6 August 30th, 2007 09:51 AM
Custom GridView bmains ASP.NET 2.0 Basics 0 August 8th, 2005 03:06 PM
Custom GridView (maybe?) bmains ASP.NET 2.0 Basics 0 April 18th, 2005 09:48 AM

Powered by vBulletin®
Copyright ©2000 - 2020, Jelsoft Enterprises Ltd.
Copyright (c) 2020 John Wiley & Sons, Inc.