I'm wondering if SharePoint Out-of-the-box components use any client side redirect. Or the standard web parts (e.g. ListViewWebPart) only use server side redirect (Response.redirect)?
View Complete Post
AJAX is meant to go beyond mere partial page rendering. Find out where Dino Esposito thinks dynamic pages are headed in the future with ASP.NET AJAX.
MSDN Magazine June 2008
Microsoft AJAX Library and the ASP.NET 2.0 AJAX Extensions provide a number of compelling features ranging from client-side data binding, to DHTML animations and behaviors. Learn all about them here.
MSDN Magazine January 2007
This month Dino Esposito dissects the client-side source code generated by ASP.NET pages.
MSDN Magazine December 2006
MSDN Magazine February 2004
MSDN Magazine January 2004
In the September and October 2000 issues of MSDNÃÂ® Magazine I discussed how to build a client-side environment for ASP applications; that is, a serverless environment to run ASP pages (see Cutting Edge: A Client-side Environment for ASP Pages and Cutting Edge: A Client-side Environment for ASP Pages-Part 2).
MSDN Magazine January 2003
In the past, Web developers often used ActiveX controls if they wanted customized client-side functionality incorporated into their Web applications. Now, they can build objects supported by the Microsoft .NET Framework which are more compact, lightweight, secure, and seamlessly integrated. By hosting .NET Windows Forms controls in Internet Explorer, developers can realize many of their client-side Web development goals. This article adapts ActiveX concepts for use with Windows Forms, and builds a multifile upload application that demonstrates these techniques.
MSDN Magazine January 2002
MSDN Magazine December 2000
MSDN Magazine October 2000
MSDN Magazine September 2000
I've seen this question posted on all corners of the web... "How do I disable "AutoPostBack" on the ASP.NET 2.0 TreeView control?!" Unfortunately, most of the answers either don't work, miss the point (don't work right), or boil down to "You can't do it." I happen to know that this behavior worked perfectly in the IEWebControls TreeView that Microsoft released as an add-on prior to ASP.NET 2.0, however. So I set out to find a solution for the ASP.NET 2.0 TreeView issue.
In a nutshell, the behavior that I and others are looking for is to have a TreeView rendered in a page that allows the user to expand, contract, and select nodes within the TreeView without causing a PostBack to the server. This implies two things: (1) the most recently-selected node should be recorded as the currently-selected node [i.e., at PostBack time, the most-recently selected node is actually represented as the SelectedNode]; and (2) the selected node should exhibit the SelectedNodeStyle as specified in the TreeView declaration.
It appears that the TreeView engineers saw only two possible outcomes from selecting a leaf node in a tree: (1) immediately posting back to the server, or (2) immediately navigating to another web page. They apparently did not consider option (3) just allowing selection in-place on the client, while waiting for a click on so
I have a web page that displays a listing of links. A treeview control displays a hierarchy of tags with checkboxes that act as filters... when checked, the list is 'filtered'. This all works fine but what I really need is for this page to be lightning fast. Right now, checking a box fires an event and a postback, etc. I'm wondering if there is a way to do all of this on the client side. For example, could you start out with a complete listing (dataset) of all possible hyperlinks, and then apply filters to that list all on the client side so as to eliminate any lag/postback?