You searched for the word(s): userid:653162

More Search Options

RSS Available

• When is tagMapping applied?

  In the ASP.NET AJAX sample web.config there is a section to map the System.Web.UI.WebControls Validators to replacements in System.Web.UI.Compatibility. Obviously this is done to make them compatible with the UpdatePanel client-side code hooks. My question is when is that mapping applied, and by whom? Does the mapping only happen in the Designer? What if I manually want to dynamically create a Validator control? Will the system somehow just know what to do? Or do I (like we have to for the ClientScript

  Posted to ASP.NET AJAX Discussion and Suggestions (Forum) by IDisposable on 12/14/2006
  Filed under: Validator tagMapping

• Re: CompositeDataBoundControlAdapter "Invisible" rows fix

  I'm a moron... Visible is the guy that prevents rendering... my mistake.

  Posted to CSS Friendly Control Adapters (Forum) by IDisposable on 12/14/2006

• Re: Bug in DataList - No PostBack in Footer

  Shouldn't you do the same things for the heade right after it's DataBind call?

  Posted to CSS Friendly Control Adapters (Forum) by IDisposable on 12/14/2006

• Re: CompositeDataBoundControlAdapter "Invisible" rows fix

  Please DON'T include this fix...it is the wrong approach. Visible is not the same as Enabled. Things that are not Visible should still be rendered to the client, with a style of display:none. If you don't emit the elements then it is not possible for client-side code to display the element without a round-trip to the server (or things like hovers working). So, the right thing to change is for all the places that render rows that could be set to Visible = false to emit the correct style on the tag

  Posted to CSS Friendly Control Adapters (Forum) by IDisposable on 12/14/2006

• [Beta 3] FIX: TreeView doesn't handle expanded state for second and subsequent TreeView instances on same page

  If you have a page with multiple TreeView instances, only the first one will have it's expanded/collapsed state correctly set when the page loads/reloads. This is due to a tiny error in the TreeViewAdapter.cs SaveAdapterViewState method. Replace this line: Page.ClientScript.RegisterOnSubmitStatement(GetType(), GetType().ToString(), script); With this: Page.ClientScript.RegisterOnSubmitStatement( typeof (TreeViewAdapter), _viewState.ClientID, script);

  Posted to CSS Friendly Control Adapters (Forum) by IDisposable on 11/1/2006
  Filed under: BETA3 TreeView FIX postback expanded

• Re: What's up with UpdatePanels and how come nothing works? Or: A brief explanation of how UpdatePanel works by the guy who wrote the feature. (Long!)

  Excellent summary! I also suggest reading this message for information about being agile in the presence/absence of the AJAX being installed. http://forums.asp.net/thread/1445844.aspx

  Posted to ASP.NET AJAX UI (Forum) by IDisposable on 10/31/2006

• Re: AJAX FIX: UpdatePanel

  Now comes the tedious part. You need to find every other call to WriteBeginDiv that is in the kit. And you need to add an extra argument, final argument, an empty string. The files you need to touch are: You don't have to do all this tedious work if you simply ADD the second overloaded method WriteBeginDiv instead of modifying the existing one.

  Posted to CSS Friendly Control Adapters (Forum) by IDisposable on 10/29/2006

• RSS Feeds of Forums return a 304 even when new messages exist...

  RSS feeds for the forum are returning a 304 Not Changed HTTP status code even if there are new messages on the forum. See this blog post... http://musingmarc.blogspot.com/2006/07/fixing-forumsaspnet-rss-feed-issues.html

  Posted to Feedback on this website (Forum) by IDisposable on 7/28/2006

• Re: Tip for those who put ScriptManager on the Master page

  This is cool, thanks!

  Posted to ASP.NET AJAX Discussion and Suggestions (Forum) by IDisposable on 7/13/2006

• Code review of differences since April..

  You've got a bug in the processing of batched request responses... check out Atlas.js line# 4858: if (statusCode < 200 || statusCode >= 300) { for (var i=0; i<requests.length; i++) requests[0].completed.invoke(response, null); } In the final line, the requests[ 0 ] should be requests[ i ] . As it stands, you're processing the response callback against only the first request, but doing it requests.length times.

  Posted to ASP.NET AJAX Discussion and Suggestions (Forum) by IDisposable on 7/13/2006