CreateUserWizardStep Class
Contains basic functionality for creating a user in a step that can be templated. This class cannot be inherited.
Assembly: System.Web (in System.Web.dll)
[BrowsableAttribute(false)] [AspNetHostingPermissionAttribute(SecurityAction::InheritanceDemand, Level = AspNetHostingPermissionLevel::Minimal)] [AspNetHostingPermissionAttribute(SecurityAction::LinkDemand, Level = AspNetHostingPermissionLevel::Minimal)] public ref class CreateUserWizardStep sealed : public TemplatedWizardStep
<asp:CreateUserWizardStep />
The CreateUserWizard control creates new user accounts in a Web site's user data store. The CreateUserWizardStep is, by default, the first step within the CreateUserWizard control. The CreateUserWizardStep step is a required step within the CreateUserWizard control.
The CreateUserWizardStep class is derived from the TemplatedWizardStep class. The CreateUserWizardStep is displayed in the CreateUserWizard control before the CompleteWizardStep step.
Note: |
|---|
Although the CreateUserWizardStep step is the first step in the wizard by default, it is possible to provide a different first step. Doing so, however, can affect whether the Previous button is displayed. For example, if the CreateUserWizardStep step does not have a custom navigation template, and is preceded by another step that is rendered before CreateUserWizardStep, then the Previous button is displayed on the CreateUserWizardStep step at run time. If the CreateUserWizardStep step is rendered before the alternate "first" step, then the Previous button is not displayed. Furthermore, the Previous button is never rendered at design time. If you want the Previous button to be rendered at design time, you must add it to the custom navigation template of the CreateUserWizardStep step. |
You can modify the CreateUserWizardStep step to contain additional fields, or change the display order of the fields included in the CreateUserWizardStep step, by editing the template associated with the control.
The new Web site user account is created in the data store when the user clicks the Next button on the CreateUserWizardStep step. By default, the AllowReturn property is set to false to keep the user from returning to the CreateUserWizardStep step and accidentally attempting to create another user account with the same credentials. If you set the AllowReturn property to true, you must include logic in your application to remove the user account that was originally created before the user returned to this step, or to allow the user to edit information he or she originally entered.
| Topic | Location |
|---|---|
| How to: Customize the ASP.NET CreateUserWizard Control | Building ASP .NET Web Applications |
| How to: Customize the ASP.NET CreateUserWizard Control | Building ASP .NET Web Applications |
The first code example uses the short-form declarative syntax of the CreateUserWizardStep class to add an additional control to a CreateUserWizard control. The code example requires the following entries in the Web.config file.
<configuration>
<system.web>
<profile>
<properties>
<add name="lastName" />
<add name="firstName" />
</properties>
</profile>
</system.web>
</configuration>
Security Note: |
|---|
This example has a text box that accepts user input, which is a potential security threat. By default, ASP.NET Web pages validate that user input does not include script or HTML elements. For more information, see Script Exploits Overview. |
Security Note: |
|---|
This control has a text box that accepts user input, which is a potential security threat. User input in a Web page can potentially contain malicious client script. By default, ASP.NET Web pages validate user input to ensure that the input does not contain HTML elements or script. As long as this validation is enabled, you do not need to explicitly check for script or HTML elements in user input. For more information, see Script Exploits Overview. |
The second code example lists the complete CreateUserWizardStep control.
Security Note: |
|---|
This control has a text box that accepts user input, which is a potential security threat. User input in a Web page can potentially contain malicious client script. By default, ASP.NET Web pages validate user input to ensure that the input does not contain HTML elements or script. As long as this validation is enabled, you do not need to explicitly check for script or HTML elements in user input. For more information, see Script Exploits Overview. |
- AspNetHostingPermission
for operating in a hosted environment. Demand value: LinkDemand. Permission value: Minimal.
- AspNetHostingPermission
for operating in a hosted environment. Demand value: InheritanceDemand. Permission value: Minimal.
System.Web.UI::Control
System.Web.UI.WebControls::View
System.Web.UI.WebControls::WizardStepBase
System.Web.UI.WebControls::TemplatedWizardStep
System.Web.UI.WebControls::CreateUserWizardStep
Windows 7, Windows Vista, Windows XP SP2, Windows XP Media Center Edition, Windows XP Professional x64 Edition, Windows XP Starter Edition, Windows Server 2008 R2, Windows Server 2008, Windows Server 2003, Windows Server 2000 SP4, Windows Millennium Edition, Windows 98
The .NET Framework and .NET Compact Framework do not support all versions of every platform. For a list of the supported versions, see .NET Framework System Requirements.
Note:
Security Note: