(Other Format)
This Wrox Blox provides two solutions for dynamic control survivability, including using the ASP.NET Session object to hold the dynamic controls, and accessing the page's Form objects before they are destroyed. Using ASP.NET 2.0 with C# and VB.NET, you will explore both solutions and see the best situations in which to use them. Many ASP .NET programmers require the use of dynamic, page-generated controls to provide a flexible user experience. However, when creating controls on the fly within a web page, any postback to that page will destroy the original controls and the data they were holding.
How do you retain these controls and their data when performing an otherwise destructive postback? ASP.NET programmers usually find that a web search will provide little in the way of answers to this question. This Wrox Blox provides two solutions for this common problem. The solutions proposed include using the ASP.NET Session object to hold the dynamic controls, and accessing the page’s Form objects before they are destroyed. Both of these solutions have their advantages and drawbacks. Using ASP.NET 2.0 with C# and VB.NET, you will explore both solutions and see the best situations in which to use them.
More Reviews and RecommendationsJ.F. DiMarzio is an author and Senior Web Developer from central Florida. He has written five books on the subject of technology and computer science and offers a refreshing, peer-style tone that makes his books and articles easy to understand. Mr. DiMarzio has been active in the technology for more than 13 years and has been programming for more than 20 years.