Why do we need WizardStep objects like ...?

This is probably a stupid question, but still ..


A Wizard control consists of a set of WizardStep objects, which are individual steps in a wizard. But why is this WizardStep object exposed as controls (thus they require the runat = Server attribute)? Couldn't they be handled similarly to ListItem objects that don't require a runat attribute but are instead available through the Parent_Control.Item property?


thank

+1


source to share


1 answer


WizardStep controls can be containers for other controls, making them non-trivial. Whereas ListItems are just objects consisting of a string and an ID and nothing more.



+1


source







All Articles