Immediate Help needed - hyperlink vs Button

[=?Utf-8?B?ZGlub28=?=]

I am having a ASP.Net screen that displays around 10000 records on a page. At
present I have "Edit" button next to each record.

Does any one have idea that instead of using a ASP Button if I use ASP link
to edit the record, would gain me any performance?
I do get some but not able to undetstand why?

I checked the GDI objects created by ASP Button control as oppose to Link,
but there is no much difference.

Any one has any idea whats going on here.

[Mark Rae [MVP]]

Re: Immediate Help needed - hyperlink vs Button

"dinoo" <dinoo@discussi ons.microsoft.c omwrote in message
news:BF008B12-9B68-4D19-BCCE-2C1207BC6F7D@mi crosoft.com...

I am having a ASP.Net screen that displays around 10000 records on a page.

10,000 records on a single page? Surely not...! How long does the browser
take to render that amount of markup...?


--
Mark Rae
ASP.NET MVP

http://www.markrae.net

[Ben Amada]

Re: Immediate Help needed - hyperlink vs Button

dinoo wrote:

>I am having a ASP.Net screen that displays around 10000 records on a page.
>At
present I have "Edit" button next to each record.
>
Does any one have idea that instead of using a ASP Button if I use ASP
link
to edit the record, would gain me any performance?
I do get some but not able to undetstand why?
>
I checked the GDI objects created by ASP Button control as oppose to Link,
but there is no much difference.
>
Any one has any idea whats going on here.

If possible, I would try to reduce the number of records you're showing at a
single time. Maybe add paging or some way for the user to better filter the
amount of data shown on each page.

If you have viewstate enabled and the Edit button performs a post to the
server, the viewstate that is posted to the server is probably really large.
Most people don't have very fast upload speeds. This poor performance can
be improved by either not having viewstate turned on for the data you're
outputting, or using a hyperlink pointing back to the same page with the ID
of the record to be edited. This would perform a GET and avoid the large
viewstate post data back to the server.