6: Building a Shopping Cart Application in .NET framework

Maker Code 39 in .NET framework 6: Building a Shopping Cart Application

<br /> <asp:Label ID= Label12 runat= server BorderStyle= None Text= Shipping: Width= 80px /> <asp:Label ID= lblShipping 20 runat= server /> <br /> <asp:Label ID= Label14 runat= server BorderStyle= None Text= Total: Width= 80px /> <asp:Label ID= lblTotal 21 runat= server /> <br /><br /> Click Submit Order to complete your order<br /> </asp:WizardStep> </WizardSteps> <SideBarStyle VerticalAlign= Top /> </asp:Wizard> </asp:Content>

This is a long listing because the Wizard control has three steps, each of which is like an entire Web page unto itself The following list describes each of the controls defined for this page:

In the Page directive, remember to change the Language attribute to VB and the AutoEventWireup attribute to false if you re working with Visual Basic The Wizard control defines the wizard displayed by the Check Out page The ActiveStepIndex attribute specifies the index of the step the wizard should start with when the page is first displayed, and the FinishCompleteButtonText attribute specifies the text displayed on the Finish button in the final step of the wizard Whenever you run the application from Visual Studio, this attribute is changed to match the step that is currently displayed in the design window As a result, you should always switch to the first Wizard step before running the application from Visual Studio If you re working in Visual Basic instead of C#, you should remove the OnFinishButtonClick attribute

The <WizardSteps> element defines the steps used by the wizard Each of these steps is then defined by an <asp:WizardStep> element This one defines the first step in the Wizard, titled Shipping The content for this step begins with the text Where do you want this order shipped Then items 4 through 11 define the controls that allow the user to enter the shipping information A label, text box, and required-field validator let the user enter his or her last name

5 6 7 8

A label, text box, and required-field validator let the user enter his or her first name A label, text box, and required-field validator let the user enter his or her address A label, text box, and required-field validator let the user enter the city A label and a drop-down list let the user select the state As you can see, 51 <ListItem> elements are used to populate the dropdown list with the names and abbreviations of the 50 states plus the District of Columbia A label, text box, and required-field validator let the user enter his or her Zip code A label, text box, and required-field validator let the user enter his or her phone number A label, text box, and required-field validator let the user enter his or her e-mail address This is the last set of controls for the first wizard step The second wizard step defines the controls that let the user enter his or her credit card information This step is titled Billing A label and a drop-down list let the user choose the credit card type <ListItem> elements are used to fill the drop-down list with three popular credit card types: Visa, MasterCard, and American Express If you want to accept additional credit card types, you can add additional <ListItem> elements A label, text box, and required-field validator let the user enter the credit card number For an actual application, you ll want to do more validation than a simple required-field validator provides In particular, you ll want to make sure that the number entered conforms to the requirements for each credit card type (The requirements vary depending on card type; I ll leave it to you to provide this validation) A label and drop-down list let the user select the credit card s expiration month Twelve <ListItem> elements fill the list with the months of the year A label, text box, and two validators let the user enter the year the credit card expires The required-field validator ensures that the user enters a value, and the range validator requires that the entry be an integer between 2005 and 2099 Note that this validation logic doesn t prevent the user from entering data based on a card that s already expired You may want to provide more extensive validation here to ensure that the year is greater than or equal to the current year and (if the year is equal to the current year) that the month is greater than or equal to the current month

9 10 11

12 13

14

15

16