1. ASP.NET Introduction 2. Comp of .Net Framework 3.5 3. Sys.Req for VS 2008 4. ASP.NET Envrmnt Setup 5. VS2010 Ultimate Sys.Req 6. Installing VS 2010 7. VS 2012 Sys.Req 8. Installing VS Exp 2012 9. Start the VS 2008 10. Application Life Cycle 11. Page Life Cycle 12. Page Life Cycle Events 13. ASP.NET Example 14. Event Handling 15. Default Events 16. Server Side 17. Request Object 18. Response Object 19. Server Controls 20. Server Controls Properties 21. Server Controls Methods 22. HTML Server Controls 23. Client Side 24. ASP.NET Basic Controls 25. TextBox Control 26. CheckBox Controls 27. RadioButton Controls 28. ListBox Control 29. HyperLink Control 30. Image Control 31. BulletedList Control 32. ASP.NET Directives 33. Implements Directive 34. Master Type Directive 35. Page Directive 36. PreviousPage Type 37. Managing State 38. Control State 39. Cookies 40. Query Strings 41. Server-Side State 42. Session State 43. Validation Controls 44. Required FieldValidator 45. Range Validator 46. Compare Validator 47. RegularExpressionValidator 48. Custom Validator 49. Validation Summary 50. Data Source Control 51. AdRotator Control 52. Calendar Control 53. Calendar Control Example 54. Panel Control 55. Panel Control Example 56. Multi Views Control 57. MultiView & View controls 58. MultiView Control Example 59. FileUpload Control 60. FileUpload Control Eg 61. AJAX Control 62. UpdatePanel control 63. UpdateProgress Control 64. Custom Controls 65. Custom Control Eg 66. Personalization 67. Create Simple Profile 68. ADO.NET 69. ADO.NET Objects 70. DataTable 71. DataRow 72. DataColumn 73. Object Example 74. Error Handling 75. Tracing Errors 76. Debugger 77. Security 78. Authentication 79. Authorization 80. LINQ 81. LINQ Query Operators 82. LINQ Example 83. Caching 84. Data Caching 85. Output Caching 86. Object Caching 87. Web Services 88. Create Web Services Eg 89. Web & Machine.config 90. Settings Schema 91. ASP.NET Deployment 92. XCopy Deployment 93. Web Setup Project 94. ASP Interview Part 1 95. ASP Interview Part 2 96. ASP Interview Part 3 97. ASP Interview Part 4 98. ASP Interview Part 5 99. ASP Interview Part 6
Pr.Pg border                                              Next Pg

ASP.NET AJAX Control tutorials

  • AJAX stands for Asynchronous JavaScript and XML.

  • The ASP.NET AJAX controls enable you to create rich client behavior with little or no client script, such as partial-page updating (refreshing selected parts of the page instead of refreshing the whole page with a postback) and displaying update progress during asynchronous postbacks. Asynchronous partial-page updates avoid the overhead of full-page postbacks.

  • You can find the AJAX control in the visual Studio IDE, in the toolbox called the AJAX Extensions.


Reasons to Use AJAX

  • AJAX produces a richer experience for the user. Because ASP.NET sup­port for AJAX is nearly seamless, the added complexities are well mitigated. When building a Web site, there are a few reasons you might choose to enable your ASP.NET site for AJAX:

  • AJAX improves the overall efficiency of your site by performing, when appropriate, parts of a Web page’s processing in the browser. Instead of waiting for the entire HTTP protocol to get a response from the browser, you can push certain parts of the page processing to the client to help the client to react much more quickly.

  • ASP.NET AJAX introduces to a Web site UI elements usually found in desktop applica­tions, such as rectangle rounding, callouts, progress indicators, and pop-up windows that work for a wide range of browsers.

  • AJAX introduces partial-page updates. By refreshing only the parts of the Web page that have been updated, the user’s wait time is reduced significantly. This brings Web-based applications much closer to desktop applications with regard to perceived UI performance.

  • AJAX is supported by most popular browsers—not just Internet Explorer. It works for Mozilla Firefox and Apple Safari, too. Although it still requires some effort to strike a balance between UI richness and the ability to reach a wider audience, the fact that AJAX depends on features available in most modern browsers makes this balance much easier to achieve.

  • AJAX introduces a huge number of new capabilities. Whereas the standard ASP.NET control and page-rendering model provides great flexibility and extensibility for pro­gramming Web sites, AJAX brings in a new concept—the extender control. Extender controls attach to existing server-side controls (such as the TextBox, ListBox, and DropDownList) at run time and add new client-side appearances and behaviors to the controls. Sometimes extender controls can even call a predefined Web service to get data to populate list boxes and such (for example, the AutoComplete extender).

  • AJAX improves on ASP.NET Forms Authentication and profiles and personalization ser­vices.ASP.NET support for authentication and personalization provides a great boon to Web developers—and AJAX just sweetens the offerings.


The ScriptManager Control

  • The ScriptManager control manages script resources for the page. The ScriptManager con­trol’s primary action is to register the AJAX Library script with the page so that the client script can use type system extensions.

  • The ScriptManager also makes possible partial-page rendering and supports localization as well as custom user scripts. The ScriptManager assists with out-of-band calls back to the server.

  • Any ASP.NET site wishing to use AJAX must include an instance of the ScriptManager control on any page using AJAX functionality.



The syntax of ScriptManager Control is.

<asp:ScriptManager ID="ScriptManager_name" runat="server">



ScriptManagerProxy Control

  • Scripts on a Web page often require a bit of special handling in terms of how the server renders them. Typically, the page uses a ScriptManager control to organize the scripts at the page level. Nested components such as content pages and user controls require the ScriptManagerProxy to manage script and service references to pages that already have a ScriptManager control.

  • This is most notable in the case of master pages. The master page typically uses the ScriptManager control. However, ASP.NET throws an exception if a second instance of ScriptManager is found in a given page. So, what would content pages do if they needed to access the ScriptManager control that the master page contains? The answer is that the content page should use the ScriptManagerProxy control and work with the true ScriptManager control through the proxy. Of course, as mentioned, this also applies to user controls as well.


Timer Control

  • The Timer control issues postbacks at defined intervals. Although the Timer control will perform a typical postback (posting the whole page), it is especially useful when coordinated with the UpdatePanel control to perform periodic partial-page updates.

  • You can include more than one Timer control on a Web page if different UpdatePanel controls must be updated at different intervals. Alternatively, a single instance of the Timer control can be the trigger for more than one UpdatePanel control in a Web page. Setting a Timer control inside an UpdatePanel control

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

<asp:UpdatePanel runat="server" id="UpdatePanel1"



<asp:Timer id="Timer1" runat="server" Interval="60000" OnTick="Timer1_Tick">





Pr.Pg border                                              Next Pg