Has anyone encountered a problem where creating a simple example with the UpdatePanel always results in a full refresh of the page after the postback?

 I created a page where I have a label outside the UpdatePanel and a label inside the UpdatePanel along with the button to cause the postback. Both labels showed the date and time (set during the PageLoad event handler). After clicking on the push button, the full page is refreshed instead of just one of the labels. I know that the full page was refreshed as I also added a script code to display an alert(). If everything was working correctly, the alert would only be displayed once when the page is loaded for the very first time. But, it is displayed after each postback.

 The example was created using the AJAX web site template in VS Team Suite. This is being tested on XP SP2 fully patched.

Either you keep button and label inside UpdatePanel or

Keep button outside UpdatePanel and write code in Following maneer for UpdatePanel ......

<Triggers>
<asp:AysyncTrigger ContriolID="Button1" EventName="Click">
</asp:AysyncTrigger>
</Triggers>

Try setting the EnablePartialRendering="true" in the ScriptManager. 

 <asp:ScriptManager ID="ScriptManager1" runat="server" EnablePartialRendering="true">
</asp:ScriptManager>

You might want to try posting your web.config. Also, if you see this in web.config try removing it and see if that fixes the problem. I had a similar issue when I began trying to modify existing apps to support ajax.

<xhtmlConformance mode="Legacy"/>

eh4316:

You might want to try posting your web.config. Also, if you see this in web.config try removing it and see if that fixes the problem. I had a similar issue when I began trying to modify existing apps to support ajax.

<xhtmlConformance mode="Legacy"/>

Excellent catch, thanks for this.

eh4316:

You might want to try posting your web.config. Also, if you see this in web.config try removing it and see if that fixes the problem. I had a similar issue when I began trying to modify existing apps to support ajax.

<xhtmlConformance mode="Legacy"/>

LEGEND! I had same problem as OP and this fixed it!

I wonder what that line of code did anyway.....

Swell:

 

eh4316:

You might want to try posting your web.config. Also, if you see this in web.config try removing it and see if that fixes the problem. I had a similar issue when I began trying to modify existing apps to support ajax.

<xhtmlConformance mode="Legacy"/>

 

LEGEND! I had same problem as OP and this fixed it!

I wonder what that line of code did anyway.....

Scott Guthrie provides a great explanation of this in his blog... http://weblogs.asp.net/scottgu/archive/2006/12/10/gotcha-don-t-use-xhtmlconformance-mode-legacy-with-asp-net-ajax.aspx 

Swell:

 

eh4316:

You might want to try posting your web.config. Also, if you see this in web.config try removing it and see if that fixes the problem. I had a similar issue when I began trying to modify existing apps to support ajax.

<xhtmlConformance mode="Legacy"/>

 

LEGEND! I had same problem as OP and this fixed it!

I wonder what that line of code did anyway.....

Scott Guthrie provides a great explanation of this in his blog... http://weblogs.asp.net/scottgu/archive/2006/12/10/gotcha-don-t-use-xhtmlconformance-mode-legacy-with-asp-net-ajax.aspx