I have a form inside of a masterpage content area that is using the postbackurl to submit to another page.  On the other page is a listview with an objectdatasource.  When that 2nd page is loaded, the listview gets loaded twice (as watched through debug -- the objectdatasource onselecting fires twice, listview databound fires twice, etc...).

If I place the same form on the masterpage itself (ie. not in a content area) and submit to that other page, the listview only loads once.

Any suggestions to this problem?

Thanks,

Lee

Not usre if I get this right; you have the master page with the form element inside a ContentPlaceHolder control? Is the form a server side control (runat="server")? Is the second page a content page or a stndard Web Form?

No - the form element is outside the contentplaceholder and yes, it's a server side control.  The second page is a content page.  I added a simple layout below - see if that helps.

Sorry for the confusion.

============================

Master:
...
<form...>
<asp:contentplaceholder id="content"...>
</form>
...

Page 1:
...
<asp:Content ...>
<asp:TextBox...>
<asp:ImageButton PostBackURL="~/page2.asp"...>
</asp:Content>

Page 2:
...
<asp:Content ...>
<asp:ListView...>
<asp:ObjectDataSource...>
</asp:Content>

Okay, I think we're on the same page now, pun intented. ;-)

The loading of a page and databound controls may have to do with one or more incorrectly defined HTML elements on the offending page. This can cause your browser to request the page more than once. Have you checked the markup in page 2 compared to what you have in page 1?

I'll be happy to go over your markup, if you want?

The pages are not publically accesible else I'd love for you to take a look...  What should I be looking for?  What page should I consider the offending page (master, page1 or page2)?

In watching debug, I noticed that Page_Load only gets fired once. So the sequence is something like:
Page_Load
ObjectDataSource_Selecting
ListView_ItemDataBound
(immediatly back to)
ObjectDataSource_Selecting
ListView_ItemDataBound

I don't know helps at all...

Well, if your problem is with page 2 only, or rather a combination of the master page and content page 2, then your beef should be with page 2. In any case, I think you might want to check properties that are set or not set, missing closing tags and stuff like that. Potentially start with the ImageButton and then all of the markup on page 2.

Do you DataBind from code? Or do you let ASP do it all for you?

superguppie:

Do you DataBind from code? Or do you let ASP do it all for you?

ASP.net does it all - there is no databind in codebehind.

It's probably related to this bug in the ListView control when bound to a data-source control. If you manually call DataBind on the ListView or any parent control, or if the ListView is nested within another data-bound control, the select method of the data source control will be called twice.

The bug has been marked as "fixed", so hopefully .NET 4 will not have this problem. Until then, the workaround is to wrap the ListView in a container which will prevent the parent DataBind method from affecting the ListView.

Hmmmm, now I am really curious about the masterpage and subpage. I have a webapplication using masterpages and even nested masterpages a lot. Haven't noticed any performance issues. But if there is repeated binding, I want to know about it. I'll have a look at that on monday. (when at work again)

So, you're not working over the weekend? Alright for some, eh?

Yeah. Lucky me.

And rethinking my last post. I don't think we use ListView. GridView is the one if I remember correctly.
That will be another "Lucku me". :D