Configure ASP.NET AJAX Extensions ...

Create a New ASP.NET AJAX Web Site
Once you have installed the ASP.NET AJAX Extensions from http://ajax.asp.net, you will see a new template named "ASP.NET AJAX-Enabled Web Site" in Visual Studio .NET 2005 is New Web Site dialog (see Figure 1).

When you use the ASP.NET AJAX-Enabled Web Site template to create a new Web site, you add a specialized web.config file that contains various configuration entries for enabling ASP.NET AJAX functionality on the server side. The ASP.NET AJAX Extensions documentation breaks down each of the configuration tags added into web.config here.

The top portion of the web.config file contains several different section configuration tags. These tags define classes that perform the task of parsing configuration data defined in web.config at run time. For example, the scriptResourceHandler section tag specifies that the System.Web.Configuration.ScriptingScriptResourceHandlerSection class should be used to parse data defined in the scriptResourceHandler tag shown here:

<scriptResourceHandler  
  enableCompression="true"
  enableCaching="true" />

This tag provides configuration information used by the run-time engine to determine if script resources embedded in assemblies are compressed and/or cached. Both compression and caching are enabled by default, although the compression setting will not have an effect in browsers that don support compression.

Other configuration sections in web.config include the ASP.NET AJAX profile service, which is used to access personalization information, and the authentication service, which is used to log users in and out of an application. You can also use the JSON [JavaScript Object Notation] serialization configuration to limit JSON message sizes that will be processed, restricting the number of object levels that can be processed and integrating custom JSON serialization classes.

The authentication, profile and JSON serialization configuration tags are commented out by default, but you can easily enable them by removing the appropriate comment tags. (In a future column, I will discuss the profile and authentication services and show you how they can be used in AJAX applications.)

Prefixes, Handlers and Modules
In addition to defining custom configuration sections used by the ASP.NET AJAX Framework, web.config maps the standard "asp" server control prefix to the System.Web.Extensions assembly (see Listing 1).

This allows you to use AJAX server-side controls, such as the ScriptManager and UpdatePanel, as you would any other standard ASP.NET server control. Prefix the desired control with "asp" and it is ready to use:

<asp:ScriptManager id="sm"
  runat="server" />

Web.config also defines two HttpHandlers and one HttpModule. All three play key roles. Review the definitions for these sections in Listing 2.

The two HttpHandlers that are defined include ScriptHandlerFactory and ScriptResourceHandler. ScriptHandlerFactory performs a variety of tasks such as handling calls made to back-end services (Web Services, profiles and authentication services). ScriptResourceHandler handles requests made to scripts embedded in the ASP.NET AJAX Extensions assemblies.

An HttpModule called ScriptModule is also defined. It handles authentication as well as routing calls to Web services using REST [Representational State Transfer]. REST is internally used for ASP.NET AJAX Web service calls. You can find more information about REST here.

Using the new ASP.NET AJAX-Enabled Web Site template simplifies the process of configuring a Web site to use ASP.NET AJAX data, controls and HttpHandlers and HttpModules. In this column, you have learned about some of the configuration sections in web.config, and learned how handlers and modules fit into the overall picture. In the next column, I will introduce a few of the ASP.NET AJAX server controls that you can use to AJAX-enable a Web site.
source: 123aspx

 View Full Story.