Beginning Ajax With ASP.NET (2006).pdf

Chapter 8
Listing 8-3: (continued)
38. if(prototypeJs.Length > 0)
39. RegisterClientScriptBlock(page, Constant.AjaxID + “.prototype”,
40. “”);
41.
42. if(coreJs.Length > 0)
43. RegisterClientScriptBlock(page, Constant.AjaxID + “.core”,
44. “”);
45.
46. if(convertersJs.Length > 0)
47. RegisterClientScriptBlock(page, Constant.AjaxID + “.converters”,
48. “”);
49.
50.
51. if(Settings.TokenEnabled)
52. {
53. RegisterClientScriptBlock(page, Constant.AjaxID + “.token”,
54. “AjaxPro.token = \”” +
CurrentAjaxToken + “\”;”);
55. }
56. }
Being as flexible as possible, the library allows you to set these property values with additional
Web.Config entries. The only thing you’ve done so far in the Web.Config is to wire up the Ajax Pro
page handler. The library has defined a custom section that you can use in your Web.Config. This is
processed by the AjaxPro.AjaxSettingsSectionHandler, found in the /Configuration/
AjaxSettingsSectionHandler.cs file.
Try It Out
Adding Custom Sections to Your Web.Config File
Fortunately, ASP.NET has framework calls that make it really easy to add custom sections to your
Web.Config file. Listing 8-4 shows a sample entry in your Web.Config to override the several default
property and actions of the Ajax.NET Pro library. Listing 8-5 shows how the library reads those overridden
values.
Listing 8-4: Web.Config configSections Sample
...
01.
02.
03.
06.
07.
08.
186