.NET news » Search results

A remote task is a piece of code that executes on the server in response to a client event. There are three possible ways for an ASP.NET AJAX client page to trigger a remote task: by causing a postback managed by an UpdatePanel control, by invoking a method directly on the application’s back end exposed through a local Web service, and by using a page method. Soon there will be a fourth method: a Windows Communication Foundation (WCF) service..

Lattice.DataMapper is a tool that maps .NET objects to and from an underlying relational database using external XML configuration and mapping files. Features included object pre-fetch (one-to-one, one-to-many, and many-to-many), objects cache, batch job, distributed transaction.

ASP.NET 2.0 offers you several ways to set a dependency between a cached item and a file(s), another cached item(s) or SQL Server database table. No doubt they satisfy most of the real world needs. However, at times the features offered by these dependencies are not sufficient. In such cases you can create your own dependency and use it instead of inbuilt ones. In this article you learn how this can be accomplished.

Implementing geolocation using REST, AJAX and Yahoo! for use with Google Maps.

One of the excellent features of ASP.net Ajax Extension 1.0 is the UpdatePanel control. The UpdatePanel control enable partial-page rendering in an ASP.NET Web page asynchronously. The contents of UpdatePanel control will automatically update when a postback event invoked. This control does work same as MagicAjax.net panel control. The UpdateProgress control is very useful when working with UpdatePanel control. With an UpdateProgress control, you can show the status during the partial-page rendering of an UpdatePanel.

An ASP.Net/AJAX interface for utorrent

How to do AJAX without writing any JavaScript.

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

When users of any computer application start a potentially lengthy operation, best practices dictate that the user interface should be updated to indicate that work is in progress and that results may not be available for a while. This is easy to accomplish in a desktop application, but it can be rather difficult in a Web scenario. In Web applications, displaying text such as "Please wait" just before an operation begins is easy, but if you want to provide some useful feedback, such as the estimated time to completion or the percentage of work finished, it’s a bit more difficult to accomplish. This is because most lengthy tasks in Web apps execute on the server, and there are no built-in mechanisms for pushing state information to the client.

In this month’s column, I build a server and client ASP.NET AJAX infrastructure to start and control a potentially lengthy server-side task.