Showing posts with label conflict. Show all posts
Showing posts with label conflict. Show all posts

Monday, March 26, 2012

Conflict when using Textbox Watermark Extender?

Good day,

I'm trying to find what could be the problem. I'm playing with Textbox watermark extender and it works great, but when I tried using other extenders to same targetcontrol that the watermark is pointing to, I'm getting this kind of error.

Assertion Failed: Duplicate use of ID on

Is it a conflict or but in watermark extender? I'm using the examples of atlas control toolkit as reference. I used the popup control extender and tried to add a watermark extender to one of the text boxes. Then the error appears.

Note: The reason I encountered a problem is because I'm trying to make a textbox with the AutoComplete extender. I thought that adding a watermark extender would make the textbox much more user friendly.

Thanks for any comments.Depending on how the extenders implement their functionality, they may conflict when pointed at the same control. If you post a simple sample, we should be able to identify the conflict if there is one.

Here is the sample code. It is basically a text box with a popup control extender. In the popup control extender you could type some text in the smaller text box and when you had click the Add button it would transfer the text to the larger text box on the top. I added the watermark textbox extender and it begins to show the error. The popup works when the watermark is not used and vice versa. I removed the styles.

Thanks for any help. :)

<%@. Page Language="C#" AutoEventWireup="true" CodeFile="Default2.aspx.cs" Inherits="Default2" %><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"><atlas:ScriptManager ID="ScriptManager1" EnablePartialRendering=true runat="server"></atlas:ScriptManager><html xmlns="http://www.w3.org/1999/xhtml" ><head runat="server"> <title>Untitled Page</title></head><body> <form id="form1" runat="server"> <div> <asp:TextBox ID="txtEmailTo" Width=500px runat="server"></asp:TextBox> <div style="width:100%;height:3px;"></div> <asp:Panel BorderColor=black BorderStyle=solid BorderWidth=1px ID="pnlEmailTo" runat="server" Width="504px"> <atlas:UpdatePanel ID="UpdatePanel12" runat="server"> <ContentTemplate> <atlasToolkit:PopupControlExtender ID="PopupControlEmailTo" runat="server"> <atlasToolkit:PopupControlProperties OffsetX=0 OffsetY=2 TargetControlID="txtEmailTo" PopupControlID="pnlEmailto" Position="Bottom" /> </atlasToolkit:PopupControlExtender> <asp:TextBox ID="txtSampleTo" runat="server" Width="300px"></asp:TextBox> <center>  <div style="width:100%;height:3px;"></div> <asp:Button ID="btnAddTo" UseSubmitBehavior=false runat="server" Width=120px Text="Add Text" OnClick="btnAddTo_Click" /> </center> </ContentTemplate> </atlas:UpdatePanel> </asp:Panel> <atlasToolkit:TextBoxWatermarkExtender ID="TextBoxWatermarkExtender1" runat="server"> <atlasToolkit:TextBoxWatermarkProperties TargetControlID="txtEmailTo" WatermarkText="I'm a watermark" /> </atlasToolkit:TextBoxWatermarkExtender> </div> </form></body></html>

CODE

using System;using System.Data;using System.Configuration;using System.Collections;using System.Web;using System.Web.Security;using System.Web.UI;using System.Web.UI.WebControls;using System.Web.UI.WebControls.WebParts;using System.Web.UI.HtmlControls;public partialclass Default2 : System.Web.UI.Page{protected void Page_Load(object sender, EventArgs e) { }protected void btnAddTo_Click(object sender, EventArgs e) {try {if (this.txtEmailTo.Text.Trim().Length <= 0) {this.PopupControlEmailTo.Commit(this.txtEmailTo,this.txtEmailTo.Text.Trim().ToString() +this.txtSampleTo.Text.ToString()); }else {this.PopupControlEmailTo.Commit(this.txtEmailTo,this.txtEmailTo.Text.Trim().ToString() +";" +this.txtSampleTo.Text.ToString()); } }catch { } }}

I've just opened work item 224 to track this issue. It says:

"PopupControl and TextBoxWatermark both override the ID property so they can return specifically decorated IDs. This is okay, but they override the set method with a NOOP. This is bad because it means the base class's implementation that actually stores the ID for later use doesn't get called and therefore when pointing two extenders at the same control there will be no way to avoid both extenders assigning themselves the same ID ("_TargetControlID"). The set method should really do something like "base.ID = value;".

Once that's in place, it's possible to avoid the same-naming problem by assigning an ID to either or both of the relevant extender's property lists so that their generated IDs will be non-conflicting ("AssignedID_TargetControlID")."

Making that change and adding an ID to one of your two extenders pointing at the same control seems to fix the problem for me. The resulting behavior's still a little weird since they both key off of focus, etc., but at least it works and will allow non-conflicting extenders to point to the same control.

Thanks for bringing this up!


Ah I see...

Much thanks for the reply, I'd try it later today to see if it is really that weird. :)

Regards,

Conflict of TextboxWatermarkExtender and validators

I downloaded the latest version of Atlas and built a test page to see if TexboxWatermarkExtender would work with a validator. The code is below. When I click on the submit button for the first time (with no data in the textbox), I see correct behavior: validation fails, I see the error message, and the page is not posted back. If I make no changes and click on the submit button again, for a split-second I see a javascript error in the IE ("Sys.Application.findObject(...) is null or not an object"), and then the page is posted back. Needless to say, no validation occurs.

I am new to Atlas, so forgive me if I am making a rookie mistake somewhere:

<%@dotnet.itags.org. Page Language="C#" AutoEventWireup="true" CodeFile="TestPage.aspx.cs" Inherits="TestPage" %><%@dotnet.itags.org. Register assembly="AtlasControlToolkit" namespace="AtlasControlToolkit" tagprefix="cc1" %><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head runat="server"> <title>Untitled Page</title></head><body> <form id="form1" runat="server"> <div> <atlas:ScriptManager runat="server" EnablePartialRendering="true" ID="scriptManager" /> <cc1:TextBoxWatermarkExtender ID="TextBoxWatermarkExtender1" runat="server" EnableViewState="true"> <cc1:TextBoxWatermarkProperties WatermarkText="mm/dd/yyyy" TargetControlID="txtDate" /> </cc1:TextBoxWatermarkExtender> <asp:TextBox ID="txtDate" runat="server" ToolTip="mm/dd/yyyy"></asp:TextBox> <asp:RegularExpressionValidator ID="regexDate" runat="server" ControlToValidate="txtDate" CssClass="evError" ErrorMessage="Enter the date in format MM/DD/YYYY" Display="Dynamic" ValidationExpression="(0[1-9]|1[012])[- /.](0[1-9]|[12][0-9]|3[01])[- /.](19|20)\d\d" /> <asp:Button ID="Button1" runat="server" Text="Button" /></div> </form></body></html>

Check out this thread for more info about TBW+validators:http://forums.asp.net/thread/1273626.aspx

We'll be adding this to the FAQ, too. Thanks!


Thanks a lot, will do. I missed your reply until now, sorry.
In case anyone is curious, this code only started working when I added an UpdatePanel

Conflict between UpdatePanel and Client-side Callback?

I posted this issue in the ASP.Net Ajax UI forum originally but never got a definitive answer:http://forums.asp.net/t/1184085.aspx

Basically, I have a Timer control outside an UpdatePanel that Ticks every second and triggers the UpdatePanel to display the current date & time. I also have an HTML button that initiates a client-side callback, which simply counts the number of client-side callbacks executed so far, and displays the count on the page. And finally I have a TextBox control placed outside the UpdatePanel. The TextBox isn't used for anything, but it needs to be there for the error to be generated.

The problem is that when I repeatedly click the HTML button to initiate client-side callbacks while the Timer is ticking, I will eventually get the "The state informationis invalidfor this page and might be corrupted"error. To get the error to be thrown I usually have to vary thefrequency of my clicking, but I can reproduce it without too muchtrouble (i.e. between 2 and 30 clicks). I am able to reproduce theerror in both IE and Firefox, though it is much easier to get Firefox to throw the error (to get IE to throw the error, I had to add more server controls to the page).

A poster on the other thread said it sounded like there was a conflict between the UpdatePanel and Client-side callbacks, but couldn't provide any further information. Is this a known issue/limitation? Anyone know what's going on here?

Thecode is below.

<%@dotnet.itags.org. Page Language="C#" AutoEventWireup="true" CodeFile="Default.aspx.cs" Inherits="_Default" %>

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"
<html xmlns="http://www.w3.org/1999/xhtml" >
<head id="Head1" runat="server">
<title>Testing</title>
<script type="text/javascript">
function initiateCallBack(){
doCallBack(document.getElementById("spanCallBackCount").innerHTML);
}

function callBackComplete(result){
document.getElementById("spanCallBackCount").innerHTML = result;
}
</script>
</head>
<body>
<form id="form1" runat="server">
<asp:ScriptManager ID="ScriptManager1" runat="server"></asp:ScriptManager
<br /><br />
<asp:UpdatePanel ID="UpdatePanel1" runat="server" UpdateMode="conditional">
<ContentTemplate>
Date & Time: <asp:Literal ID="ltrDateTime" runat="server"></asp:Literal>
</ContentTemplate>
<Triggers>
<asp:AsyncPostBackTrigger ControlID="Timer1" EventName="Tick" />
</Triggers>
</asp:UpdatePanel>
<asp:Timer ID="Timer1" runat="server" Interval="1000" OnTick="Timer1_Tick"></asp:Timer
<br /><br />
<asp:TextBox ID="txtTest" runat="server" Text="Testing"></asp:TextBox
<br /><br />
Call Back Count: <span id="spanCallBackCount">0</span>
<br /><br /
<input type="button" id="btnCallBack" name="btnCallBack" onclick="initiateCallBack();" value="Initiate Client-side Callback" /
</form>
</body>
</html

using System;
using System.Data;
using System.Configuration;
using System.Web;
using System.Web.Security;
using System.Web.UI;
using System.Web.UI.WebControls;
using System.Web.UI.WebControls.WebParts;
using System.Web.UI.HtmlControls;

public partialclass _Default : System.Web.UI.Page, System.Web.UI.ICallbackEventHandler
{
int callBackCount = 0;

protected void Page_Load(object sender, EventArgs e)
{
string callBackReference = Page.ClientScript.GetCallbackEventReference(this,"cnt","callBackComplete","context");
string callBackScript ="function doCallBack(cnt, context){" + callBackReference +"}";
Page.ClientScript.RegisterClientScriptBlock(this.GetType(),"doCallBack", callBackScript,true);
}

public void RaiseCallbackEvent(string cnt)
{
callBackCount = Convert.ToInt32(cnt);
callBackCount++;
}

public string GetCallbackResult()
{
return callBackCount.ToString();
}

 protected void Timer1_Tick(object sender, EventArgs e)
{
ltrDateTime.Text = DateTime.Now.ToString("MM/dd/yyyy hh:mm:ss tt");

UpdatePanel1.Update();
}

}

No one can help with this? Come on, one of you Microsoft gurus must be able to provide some input...


Hi,

I tried it but can't reproduce the issue.

It's caused by viewstate validation failure, you can disable it.

<%@. Page Language="C#" AutoEventWireup="true" CodeFile="Default2.aspx.cs" Inherits="Default2" EnableViewStateMac="false"%>


Thanks for the help. Did you test it with Firefox? It's much more difficult to get IE to throw the error. I do get the error with IE, but it's much less consistent (and usually requires me to add more controls to the page). Firefox throws it pretty easily though. I actually created a video of the behavior I'm seeing with Firefox which can be seen here:

http://www.youtube.com/watch?v=EBsMRxnOtpE

(There's no audio, but I'm just running the code that I posted above, so it's not a big deal. In it, I run it with Firefox, and get it to throw the error after 20 clicks).

Unfortunately I can't disable the ViewState as in my real scenario the UpdatePanel and timer are at the top of the page checking every 60 seconds to see if the user has any new messages (internal messages to our system), and a client-side callback is used to maintain the state of the side navigation menu which consists of a Ajax Accordion control inside a Collapsible Panel.

Since the collapsing of the Panel and the selecting of Accordion panes is all done via client-side javascript, there's no good way of maintaining the state of the menu when the user is redirected to another page (or clicks a link). To solve this, I added some additional javascript that is executed whenever the user manipulates the menu, that makes a callback which stores the state of the menu in a session variable (whether it's collapsed and what Accordion pane is selected). This way when the user is redirected, or clicks on a link to another page, I have the information necessary to make the side menu look the same as it did on the previous page.

And since, these two elements are shared among all the site's pages (via a MasterPage with a UserControl for each element)....I'm not sure what to do.

Also, the error still persists even after settingEnableViewStateMac="false"in the page directive....(not sure why this thread was marked resolved/answered, I know I didn't mark it that way...)


I tried it on both IE && FF like a hundred times, but still get no exception. May be I didn't click it quickly enough?

Based on my understanding, it may be caused by different requests and responses intersect.

Can you try to disable the button upon a click and enable it again after the callback returns to avoid this?


Thanks for the help, you do have to vary the frequency of your clicking to get it to throw the error. I know it sounds bizarre but I start with a few steady clicks, not even that fast, and then increase the frequency of clicks until the error is thrown. If it hasn't thrown the error after 50 clicks, I'll reload the page and try again (Here's a better YouTube video:http://www.youtube.com/watch?v=EBsMRxnOtpE).

Disabling the button after a click might work in the test scenario but my real world app initiates a callback whenever the user manipulates the navigation menu in some way. So, hindering their ability to quickly jump from one item in the menu to another may be problematic....though callback doesn't take long, sio it's something I'll look into more...

More importantly though, I'm not sure that solves the problem. In my real app the Timer for the UpdatePanel ticks every 60 seconds, while a callback is issued every time the navigation menu is manipulated. And, when I've seen the error thrown, it appears to be thrown by the ticking of the Timer, because I've received the error after I clicked on the menu a few times, and then did nothing, and the error would only popup when the Timer executed its next Tick event...

Conflict between OnError and OnAsyncPostBackError events

I am updating my application from ATLAS to Ajax RC.

All my pages are inherited from my own WebPage subclass page that implements an OnError event and I have included the Script Manager with the OnAsyncPostBackError property in the master pages of the application.

When an exception is thrown within an Update Panel the Onerror event captures the exception and I haven't found a way to setup the AsyncPostBackErrorMessage. An alert message appears with the text:


Sys.WebForms.PageRequestManagerServerException: An unknown error occurred while processing the request on the server. The status code returned from the server was: 500


Any suggestions...?


Thanks...Antonio

Try to capture asynchronous?post?back error as the follow.
?????ScriptManager.AsyncPostBackError += new EventHandler<AsyncPostBackErrorEventArgs>(ScriptManager_AsyncPostBackError);
Determine if it is asynchronous post back:
?????ScriptManager.IsInAsyncPostBack;
Get synchronous post back error message:
?????ScriptManager.AsyncPostBackErrorMessage;
Get asynchronous post back source:
?????ScriptManager.AsyncPostBackSourceElementID;
Wish the above can help you.

I am having the same issue... We have existing sites that uses a standard basepage the overrides the OnError to catch any page errors. It will log the error and then redirect to a nicely formatted error page to explain the error. This works fine, but when I am inside a AJAX call and I get an error, I also get the following error

Sys.WebForms.PageRequestManagerServerException: An unknown error occurred while processing the request on the server. The status code returned from the server was: 500

But if I remove my OnError Handler completely, then I will get the actual error in the javascript popup. How can I handle both the normal page errors and AJAX errors if just having the OnError seems to kill the AsyncPostBackError info?

Pat


changing UpdateMode from"Conditional" to "Always" solved my problem


I tried many ways to raise and catch the error with both OnError and OnAsyncPostBackError implemented. but no use. It always go to OnError handler.

Is someone suggests the complete code ... with master page, update panels on a page and onError and OnAsyncPostBackError events implemented?

Basically, I am looking to implement both handlers and distinguish to redirect Page request errors to OnError and Update panel requests errors to OnAsyncPostBackError;

Any help is appreciated in advance.


I found a way to do this ...

Put this snippet of code in your base Page codebehind ... this should capture every error that gets thrown.

1protected override void OnError(EventArgs e)2 {3 ScriptManager mgr = ScriptManager.GetCurrent(this);45 System.Exception ex =this.Server.GetLastError();67if (mgr.IsInAsyncPostBack)8 {9base.OnError(e);10 }11else12 {13this.Server.ClearError();1415base.OnError(e);1617 Response.Write(<html><head><title>Error</title></head><body>");18 Response.Write("<table class='Section'><tr class='SectionTitle'><td colspan='2'>Error Details</td></tr><tr><TD valign='top' class='FieldLabel' width='125px'>Error Message:</TD><td class='GenText'>");19 Response.Write(ex.Message);20 Response.Write("</TD></TR><TR><TD valign='top' class='FieldLabel'>Error Source:</TD><TD class='GenText'>");21 Response.Write(ex.Source);22 Response.Write("</TD></TR><TR><TD valign='top' class='FieldLabel'>Stack Trace:</TD><TD class='GenText'>");23 Response.Write(ex.StackTrace);24 Response.Write("</TD></TR><TR><TD colspan=\"2\"><a href=\"");25 Response.Write(Request.RawUrl);26 Response.Write("\">Return to previous page</a></td></tr></table></body></html>");27 Response.End();28 }29 }

Then in your master page (or whatever page) codebehind capture the AsyncPostBackError from the ScriptManager tag (making sure to hook the OnAsyncPostBackError in the aspx page to the ScriptManager1_AsyncPostBackError):

1protected void ScriptManager1_AsyncPostBackError(object sender, AsyncPostBackErrorEventArgs e)2 {3if (e.Exception.Data["ExtraInfo"] !=null)4 {5 ScriptManager1.AsyncPostBackErrorMessage =6 e.Exception.Message +7 e.Exception.Data["ExtraInfo"].ToString();8 }9else10 {11 ScriptManager1.AsyncPostBackErrorMessage ="The following error occurred: " + e.Exception.Message;13 }14 }


My updated code for handling OnError and OnAsyncPostBackError events ...

I took different approach like assigning event handlers early and then do accordingly. I have all my pages contain a Master Page and derived from Page Base ...MyAppPageBase

publicclassMyAppPageBase :Page
{
protectedoverridevoid OnInit(EventArgs e)
{
bool AttachPageErrorEventHandler =true;

// Determine if it is a page request, then only attach page error event handler
try
{
if (this.Page !=null &&
ScriptManager.GetCurrent(this.Page) !=null &&
ScriptManager.GetCurrent(this.Page).IsInAsyncPostBack)
{
// Note: We are not attaching any event handler for page error -->
this.Page.Error -=newEventHandler(MyAppPage_Error);
this.Page.Error +=newEventHandler(MyAppPage_UP_Error);
AttachPageErrorEventHandler =false;
}
}
catch { }

if (AttachPageErrorEventHandler)
{
this.Page.Error +=newEventHandler(MyAppPage_Error);
this.Page.Error -=newEventHandler(MyAppPage_UP_Error);
}
base.OnInit(e);
}

protectedvoid MyAppPage_Error(object sender,EventArgs e)
{
Exception exBase = Server.GetLastError().GetBaseException();

if (exBase.GetType().Name =="HttpRequestValidationException")
{
>>> Redirect to a page to show that you are using <script> tag as data; Malformed data
}
else// all other / generic exception
{

this.Context.AddError(exBase);
Server.ClearError();
Server.Transfer("~/Error.aspx");
Response.Flush();/*The line is added to cancel the event bubbleup */
Response.End();/*The line is added to cancel the event bubbleup */
}
}

protectedvoid TPPage_UP_Error(object sender,EventArgs e)
{
Exception exBase = Server.GetLastError().GetBaseException();
if (exBase.GetType().Name =="HttpRequestValidationException")
{
string str ="You have submitted the data with <script>tag or with malformed data";
Response.Write(string.Format("{0}|error|500|{1}|", str.Length, str ));
}
else// all other types of exception
{
Response.Write(string.Format("{0}|error|500|{1}|", exBase.Message.Length, exBase.Message));
}
}
}

so far it is working great!

Conflict between Microsoft ASP.NET 2.0 AJAX Extensions (Atlas) and ArcGIS Server 9.2 Contr

Helloo,

I was trying to use Microsoft ASP.NET 2.0 AJAX Extensions (Atlas) and ArcGIS Server 9.2 controls in the same web applications but there were conflict a between the Map control and UpdatePanel control as the error message appear with the message (“unknown error”);

Why this conflict occurs?

Is there’re any solution that enable be to use the UpdatePanel control in the same page with Map Control?

In the Atlas CTPs we had a lot of conflicts with 3rd part controls (and even some of our own controls) because we did a lot of automatic scanning for scripts and things like that. In Atlas 1.0 we don't do automatic stuff like that because it breaks too easily. Instead, 3rd party controls will have to be updated to be compatibleinside the UpdatePanel. If they're outside the UpdatePanel then they typically don't require any changes.

Thanks,

Eilon

Conflict between IE7 and AJAX update panel

I think I found a bug in Microsoft Explorer 7. When I launch a modal popupwindow or a java alert box (using ScriptManager.RegisterClientScriptBlock) from within an Update Panel, the whole screen is being pushed about 15 pixels downwards, if the page has a masterpage. It seems to work alright for pages without masterpages.

I have tested my application in IE6, IE7 and Mozilla Firefox. Internet Explorer 7 is the only browser having this issue. It doesn't matter if the update panel encapsulates just the button or everything in the content page, the problem is still there. It seems to me now that my only option is to detach all content pages with this issue from the master page by creating duplicate menus.

If anyone knows something please let me know.

Can you post some codes here??I'd?like?to?test?it?in?IF?7.0.

I discovered that the problem occurs even when a button is clicked.

Steps to replicate the error.

1. Go New Website, ASP.NET AJAX CTP enabled website/Visual Basic

2. Create MasterPage.master

3. Create Default2.aspx with MasterPage.master as masterpage

4. Copy the following block to Default.aspx(Source)

<%@. Page Language="VB" MasterPageFile="~/MasterPage.master" AutoEventWireup="false" CodeFile="Default2.aspx.vb" Inherits="Default2" title="Untitled Page" %><asp:Content ID="Content1" ContentPlaceHolderID="ContentPlaceHolder1" Runat="Server"> <asp:Panel ID="Panel1" runat="server" Height="50px" Width="125px"> <asp:UpdatePanel id="x" runat="server"> <ContentTemplate><asp:Button id="Button1" runat="server" Text="Button" ></asp:Button> </ContentTemplate> </asp:UpdatePanel> </asp:Panel></asp:Content>

5. Copy the following block to MasterPage.master(Source)

<%@. Master Language="VB" CodeFile="MasterPage.master.vb" Inherits="MasterPage" %><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head id="Head1" runat="server"> <title>Untitled Page</title> </head><body> <form id="form1" runat="server"> <asp:ScriptManager ID="ModalPopUpTestExScriptmanager" runat="server"> </asp:ScriptManager> <asp:UpdatePanel ID="UpdatePanel1" runat="server"> </asp:UpdatePanel> <asp:contentplaceholder id="ContentPlaceHolder1" runat="server"> </asp:contentplaceholder> </form></body></html>

6. Start the application and click the button. If you use IE7 as a browser the button will be relocated when you click it the first time. It works for me in Firefox and IE6.


Correction: Item no 4 should be: "4. Copy the following block to Default2.aspx(Source)" and nothing else


When I remove the update panel from the master page everything function normally. The problem seems to happen in IE7 especially when both the content page and master page have an update panel each. Personally, I don't need an update panel in my masterpage. The update panel in my masterpage was completely redundant and unnecessary. The reason I had it there at all is that I was experimenting some time ago with top menus in update panels and I must have forgotten to remove it. Thanks
I installed Visual Studio .NET 2005 with Ajax RC 1.0 and Futures Dec CTP in my PC and tested your codes in your?last?post. I?found?it?worked?fine?in?IE?7.0.
Try to add "<asp:ScriptManagerProxy runat="server"></asp:ScriptManagerProxy>" to the content page?as?the?following and check if it works.
<%@. Page Language="VB" MasterPageFile="~/MasterPage.master" AutoEventWireup="false" CodeFile="Default2.aspx.vb" Inherits="Default2" title="Untitled Page" %
<asp:Content ID="Content1" ContentPlaceHolderID="ContentPlaceHolder1" Runat="Server">
<asp:ScriptManagerProxy runat="server"></asp:ScriptManagerProxy>
<asp:Panel ID="Panel1" runat="server" Height="50px" Width="125px">
<asp:UpdatePanel id="x" runat="server">
<ContentTemplate>
<asp:Button id="Button1" runat="server" Text="Button" ></asp:Button>
</ContentTemplate>
</asp:UpdatePanel>
</asp:Panel>
</asp:Content>
Wish the above can help you.
I installed Visual Studio .NET 2005 with Ajax RC 1.0 and Futures Dec CTP in my PC and tested your codes in your?last?post. I?found?it?worked?fine?in?IE?7.0.
Try to add "<asp:ScriptManagerProxy runat="server"></asp:ScriptManagerProxy>" to the content page?as?the?following and check if it works.
<%@. Page Language="VB" MasterPageFile="~/MasterPage.master" AutoEventWireup="false" CodeFile="Default2.aspx.vb" Inherits="Default2" title="Untitled Page" %
<asp:Content ID="Content1" ContentPlaceHolderID="ContentPlaceHolder1" Runat="Server">
<asp:ScriptManagerProxy runat="server"></asp:ScriptManagerProxy>
<asp:Panel ID="Panel1" runat="server" Height="50px" Width="125px">
<asp:UpdatePanel id="x" runat="server">
<ContentTemplate>
<asp:Button id="Button1" runat="server" Text="Button" ></asp:Button>
</ContentTemplate>
</asp:UpdatePanel>
</asp:Panel>
</asp:Content>
Wish the above can help you.