DataPager double binds when paging using QueryStringField - by ryanrr

Status : 

  Fixed<br /><br />
		This item has been fixed in the current or upcoming version of this product.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.


12
0
Sign in
to vote
ID 355348 Comments
Status Closed Workarounds
Type Bug Repros 5
Opened 7/8/2008 4:32:35 AM
Access Restriction Public

Description

When you use the QueryStringField with a DataPager it causes the ListView to bind twice; once as if it was on the first page, and a second time for whatever page is passed via the QueryString (even if it is also the first page). Naturally, this is very bad for performance and completely unnecessary. 
Sign in to post a comment.
Posted by EnderII on 12/15/2009 at 3:30 PM
Can this fix not be added to a .Net 3.5 Service Pack?
Posted by ljwagerfield on 7/24/2009 at 1:47 AM
I have written my own lightweight DataPager. It only support QueryStrings, but that's what you're after, right?

Download the Crucible .NET Project, and compile it (VS 2008)...
http://www.crucible.org.uk/ (Download it from the Crucible NET SVN, there's a link on the homepage).

The web control you're after is:
Crucible.NET.Web.UI.WebControls.QsDataPager

Behaves in the same way as DataPager... you can have it either inside your ListView, or outside with the PagedControlID property pointing to the ListView.
Posted by Microsoft on 7/1/2009 at 9:53 AM
We have fixed this issue in the next release of the .NET Framework. You can preview the fix in Beta 1 of .NET 4.
Posted by ljwagerfield on 6/19/2009 at 2:32 AM
Has this been fixed?! What is the work-around / fix? Please tell!!!
Posted by Philwith on 10/20/2008 at 4:13 AM
Has this been resolved then? If so how?
Posted by Daze on 7/29/2008 at 9:03 AM
I'd really like to see this fixed a.s.a.p.
Posted by Microsoft on 7/9/2008 at 4:25 AM
Thanks for your feedback. We are escalating this bug to the product unit who works on that specific feature area. The team will review this issue and make a decision on whether they will fix it or not for the next release.

Thank you,
Visual Studio Product Team