.NET news » Search results

Microsoft's ASP.NET AJAX Framework helps page developers design more interactive web pages by streamlining the postback mechanism. In traditional web pages, a full postback involves the browser re-requesting the page, which is then re-rendered. This re-rendered page markup is returned, in its entirety, to the browser for display. Ajax techniques improve the user's experience in two primary ways through the use of partial postbacks: first, a partial postback is asynchronous, meaning that the user can still interact with the page while waiting for the partial postback to complete; second, and more importantly, because a partial page postback updates only a particular region (or regions) of a page, less data needs to be shuttled between the client and the server, resulting in a quicker and smoother experience..

Anyone who has spent time developing URL rewriters will know that these do not always play nicely with AJAX components. This is because the HtmlForm element written out by .NET uses the actual URL for post-backs, and not the page's virtual URL that you are trying to preserve. This article discusses how this can be resolved cleanly, and also shows how control adapters may be set programmatically using Reflection. This is useful for creating plug & play components such as URL rewriters in order to minimise the amount of configuration required.

How to achieve search engine optimization in AJAX site

Today's websites commonly exchange information between the browser and the web server using Ajax techniques. In a nutshell, the browser executes JavaScript code typically in response to the page loading or some user action. This JavaScript makes an asynchronous HTTP request to the server. The server processes this request and, perhaps, returns data that the browser can then seamlessly integrate into the web page. Typically, the information exchanged between the browser and server is serialized into JSON, an open, text-based serialization format that is both human-readable and platform independent.

Adding such targeted, lightweight Ajax capabilities to your ASP.NET website requires two steps: first, you must create some mechanism on the server that accepts requests from client-side script and returns a JSON payload in response; second, you need to write JavaScript in your ASP.NET page to make an HTTP request to this service you created and to work with the returned results. This article series examines a variety of techniques for implementing such scenarios. In Part 1 we used an ASP.NET page and the JavaScriptSerializer class to create a server-side service. This service was called from the browser using the free, open-source jQuery JavaScript library.

This article continues our examination of techniques for implementing lightweight Ajax scenarios in an ASP.NET website. Specifically, it examines how to create ASP.NET Ajax Web Services on the server-side and how to use both the ASP.NET Ajax Library and jQuery to consume them from the client-side.

An ASP.Net/AJAX interface for utorrent

Creating AJAX based CRUD tables using ASP.NET MVC 3 and the jTable jQuery plug-in.

A chapter excerpt from ASP.NET MVC 4 in Action

An introduction with AJAX, jQuery, JSON, MvcContrib and NUnit

UltimateSpell is an ASP.NET control to spell check editable content on your web pages. * AJAX Enabled - Spell check very long text without compromising on speed. Sends small blocks of text to server using AJAX techniques without refreshing the page. * Auto Find - Drag-and-drop the control onto your page, and you're done. It automatically finds and spell checks all editable controls. * Cache Dictionary - Automatically caches dictionaries for fast interaction and data retrieval. * Lots of Dictionaries - Currently 34 dictionaries available on our website. If not enough you can use your own dictionary as well. * Show Options - Change the spelling options either on the server-side, or on the client-side inside the spell check dialog box at runtime.

A base class for adding a rich asynchronous progress animation to any Form