Download as a PDF

method that transfers control to another page. Assume the
page being called is named MyDNCRegister.aspx. The
supporting VB.NET “code-behind” subroutine is as follows:
Private Sub btnRegisterNow_Click(...) Handles
btnRegisterNow.Click
Server.Transfer("myDNCRegister.aspx")
End Sub
The service routine for the other buttons in Figure 5 is
similar to the above fragment. The only difference is the
actual name of the Web Form being called.
4.1.2.1 Step One: Registration – Data Collection: A
rendition of the registration page appears in Figure 6. The
interior frame identifies the page as “Step One” of the
process and provides brief instructions for the consumer as
well as text boxes to collect input data. Up to three phone
numbers (including area code) could be entered on the page.
The consumer – for verification purposes - must enter his/her
email address twice. Local (client-side) validation could be
done. As an option, simple facts could be locally checked,
using the ASP.NET Validator controls (Required Field,
Range, and Regular Expression Validators). For instance;
area code must be present and it should be a number less
than 999, phone numbers are made of exactly seven digits
each (range 0000000-9999999), email addresses have a
format defined by the pattern [email protected], etc.
4.1.2.2 Step Two: Temporary Registration: Once the
consumer has finished the entering and editing of data,
he/she could click on the Submit button. The page is sent to
the web server where another page (call it
MyDNCCheckErrors.aspx) may perform further validation
of the supplied data. In addition to syntactical verification,
some logical problems could be addressed, such as: is the
area code a legitimate value, is the phone number already
registered, and so on. Figure 7 shows a verification page that
reflects the data entered in the previous step (Figure 6).
Figure 5. Homepage of MyDNC Registry