Container Controls and Naming Containers: Unlike some of the other container controls covered in this book, the Panel and MultiView controls are not naming containers. This is an important concept in ASP.NET. Container controls generate a special ID-based namespace for their child controls; this control namespace is called a naming container. This naming container guarantees that the ID of each of its children is unique within the page. When child controls are created at runtime (for instance, with the Wizard control in this chapter or the data controls covered in Chapter 10) the naming container of the parent is combined with the child control’s Id to create the control’s UniqueId property. The fact that the MultiView is not a naming container means that the Id of every control contained within all the View controls must be unique. That is, you cannot have a control named btnNext in view1 and view2. This also means that controls in each view are always available for programmatic manipulation. However, the flipside to this functionality is that the view state for all controls in a MultiView, regardless of whether they are visible or not, is posted back and forth for every request that uses that MultiView - Study24x7
Social learning Network
12 Apr 2019 03:39 PM study24x7 study24x7

Container Controls and Naming Containers: Unlike some of the other container controls covered in this book, the Panel and MultiView controls are not naming containers. This is an important concept in ASP.NET. Container controls generate a special ID-based namespace for their chil...

See more

study24x7
Write a comment
Related Questions
500+   more Questions to answer
Most Related Articles