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 Next Pg

Control State tutorials

  • The ASP.NET page framework provides the ControlState property as way to store custom control data between server trips.

  • For example, if you have written a custom control that has different tabs showing different information, in order for that control to work as expected, the control needs to know which tab is selected between round trips. View state can be used for this purpose, but developers can turn view state off at the page level, effectively breaking your control. Unlike view state, control state cannot be turned off, so it provides a more reliable way to store control-state data.

  • Advantages of using control state are:

    1. No server resources are required: By default, control state is stored in hidden fields on the page.

    2. Reliability: Because control state cannot be turned off like view state, control state is a more reliable method for managing the state of controls.

    3. Versatility: Custom adapters can be written to control how and where control-state data is stored.

  • Disadvantages of using control state are:

    1. Some programming is required: While the ASP.NET page framework provides a foundation for control state, control state is a custom state-persistence mechanism. To fully utilize control state, you must write code to save and load control state.


Hidden Fields

  • Hidden field is a control provided by ASP.NET which is used to store small amounts of data on the client.

  • It store one value for the variable and it is a preferable way when a variable's value is changed frequently.

  • Hidden field control is not rendered to the client (browser) and it is invisible on the browser. A hidden field travels with every request like a standard controlís value.

  • Advantages of using hidden fields are:

    1. No server resources are required: The hidden field is stored and read from the page.

    2. Widespread support: Almost all browsers and client devices support forms with hidden fields.

    3. Simple implementation: Hidden fields are standard HTML controls that require no complex programming logic.

  • Disadvantages of using hidden fields are:

    1. Potential security risks: The hidden field can be tampered with. The information in the hidden field can be seen if the page output source is viewed directly, creating a potential security issue.

    2. Simple Storage architecture:  The hidden field does not support rich data types. Hidden fields offer a single string value field in which to place information.

    3. Performance Considerations: Because hidden fields are stored in the page itself, storing large values can cause the page to slow down when users display it and when they post it.

    4. Storage limitations: If the amount of data in a hidden field becomes very large, some proxies and firewalls will prevent access to the page that contains them. Because the maximum amount can vary with different firewall and proxy implementations, large hidden fields can be sporadically problematic.


Pr.Pg border                                              Next Pg