- •About the Authors
- •Contents at a Glance
- •Contents
- •Introduction
- •Goal of the Book
- •How to Use this Book
- •Introduction to the .NET Framework
- •Common Language Runtime (CLR)
- •Class Library
- •Assembly
- •Versioning
- •Exceptions
- •Threads
- •Delegates
- •Summary
- •Introduction to C#
- •Variables
- •Initializing Variables
- •Variable Modifiers
- •Variable Data Types
- •Types of Variables
- •Variable Scope
- •Types of Data Type Casting
- •Arrays
- •Strings
- •Initializing Strings
- •Working with Strings
- •Statements and Expressions
- •Types of Statements
- •Expressions
- •Summary
- •Classes
- •Declaring Classes
- •Inheritance
- •Constructors
- •Destructors
- •Methods
- •Declaring a Method
- •Calling a Method
- •Passing Parameters to Methods
- •Method Modifiers
- •Overloading a Method
- •Namespaces
- •Declaring Namespaces
- •Aliases
- •Structs
- •Enumerations
- •Interfaces
- •Writing, Compiling, and Executing
- •Writing a C# Program
- •Compiling a C# Program
- •Executing a C# Program
- •Summary
- •Arrays
- •Single-Dimensional Arrays
- •Multidimensional Arrays
- •Methods in Arrays
- •Collections
- •Creating Collections
- •Working with Collections
- •Indexers
- •Boxing and Unboxing
- •Preprocessor Directives
- •Summary
- •Attributes
- •Declaring Attributes
- •Attribute Class
- •Attribute Parameters
- •Default Attributes
- •Properties
- •Declaring Properties
- •Accessors
- •Types of Properties
- •Summary
- •Introduction to Threads
- •Creating Threads
- •Aborting Threads
- •Joining Threads
- •Suspending Threads
- •Making Threads Sleep
- •Thread States
- •Thread Priorities
- •Synchronization
- •Summary
- •Case Study
- •Project Life Cycle
- •Analyzing Requirements
- •High-Level Design
- •Primary and Foreign Keys
- •Referential Integrity
- •Normalization
- •Designing a Database
- •Low-Level Design
- •Construction
- •Integration and Testing
- •User Acceptance Testing
- •Implementation
- •Operations and Maintenance
- •Summary
- •Creating a New Project
- •Console Application
- •Windows Applications
- •Creating a Windows Application for the Customer Maintenance Project
- •Creating an Interface for Form1
- •Creating an Interface for WorkerForm
- •Creating an Interface for CustomerForm
- •Creating an Interface for ReportsForm
- •Creating an Interface for JobDetailsForm
- •Summary
- •Performing Validations
- •Identifying the Validation Mechanism
- •Using the ErrorProvider Control
- •Handling Exceptions
- •Using the try and catch Statements
- •Using the Debug and Trace Classes
- •Using the Debugging Features of Visual Studio .NET
- •Using the Task List
- •Summary
- •Creating Form1
- •Connecting WorkerForm to the Workers Table
- •Connecting CustomerForm to the tblCustomer Table
- •Connecting the JobDetails Form
- •to the tblJobDetails Table
- •Summary
- •Introduction to the Crystal Reports Designer Tool
- •Creating the Reports Form
- •Creating Crystal Reports
- •Creating the Windows Forms Viewer Control
- •Creating the Monthly Worker Report
- •Summary
- •Introduction to Deploying a Windows Application
- •Deployment Projects Available in Visual Studio .NET
- •Deployment Project Editors
- •Summary
- •Case Study
- •Project Life Cycle
- •Analyzing Requirements
- •High-Level Design
- •Low-Level Design
- •Summary
- •Populating the TreeView Control
- •Displaying Employee Codes in the TreeView Control
- •Event Handling
- •Displaying Employee Details in the ListView Control
- •Summary
- •Case Study
- •Project Life Cycle
- •Analyzing Requirements
- •High-Level Design
- •Low-Level Design
- •Summary
- •Adding the Programming Logic to the Application
- •Adding Code to the Form Load() Method
- •Adding Code to the OK Button
- •Adding Code to the Exit Button
- •Summary
- •The Created Event
- •Adding Code to the Created Event
- •Overview of XML
- •The XmlReader Class
- •The XmlWriter Class
- •Displaying Data in an XML Document
- •Displaying an Error Message in the Event Log
- •Displaying Event Entries from Event Viewer
- •Displaying Data from the Summary.xml Document in a Message Box
- •Summary
- •Airline Profile
- •Role of a Business Manager
- •Role of a Network Administrator
- •Role of a Line-of-Business Executive
- •Project Requirements
- •Creation and Deletion of User Accounts
- •Addition of Flight Details
- •Reservations
- •Cancellations
- •Query of Status
- •Confirmation of Tickets
- •Creation of Reports
- •Launch of Frequent Flier Programs
- •Summarizing the Tasks
- •Project Design
- •Database Design
- •Web Forms Design
- •Enabling Security with the Directory Structure
- •Summary
- •Getting Started with ASP.NET
- •Prerequisites for ASP.NET Applications
- •New Features in ASP.NET
- •Types of ASP.NET Applications
- •Exploring ASP.NET Web Applications
- •Introducing Web Forms
- •Web Form Server Controls
- •Configuring ASP.NET Applications
- •Configuring Security for ASP.NET Applications
- •Deploying ASP.NET Applications
- •Creating a Sample ASP.NET Application
- •Creating a New Project
- •Adding Controls to the Project
- •Coding the Application
- •Summary
- •Creating the Database Schema
- •Creating Database Tables
- •Managing Primary Keys and Relationships
- •Viewing the Database Schema
- •Designing Application Forms
- •Standardizing the Interface of the Application
- •Common Forms in the Application
- •Forms for Network Administrators
- •Forms for Business Managers
- •Forms for Line-of-Business Executives
- •Summary
- •The Default.aspx Form
- •The Logoff.aspx Form
- •The ManageUsers.aspx Form
- •The ManageDatabases.aspx Form
- •The ChangePassword.aspx Form
- •Restricting Access to Web Forms
- •The AddFl.aspx Form
- •The RequestID.aspx Form
- •The Reports.aspx Form
- •The FreqFl.aspx Form
- •Coding the Forms for LOB Executives
- •The CreateRes.aspx Form
- •The CancelRes.aspx Form
- •The QueryStat.aspx Form
- •The ConfirmRes.aspx Form
- •Summary
- •Designing the Form
- •The View New Flights Option
- •The View Ticket Status Option
- •The View Flight Status Option
- •The Confirm Reservation Option
- •Testing the Application
- •Summary
- •Locating Errors in Programs
- •Watch Window
- •Locals Window
- •Call Stack Window
- •Autos Window
- •Command Window
- •Testing the Application
- •Summary
- •Managing the Databases
- •Backing Up the SkyShark Airlines Databases
- •Exporting Data from Databases
- •Examining Database Logs
- •Scheduling Database Maintenance Tasks
- •Managing Internet Information Server
- •Configuring IIS Error Pages
- •Managing Web Server Log Files
- •Summary
- •Authentication Mechanisms
- •Securing a Web Site with IIS and ASP.NET
- •Configuring IIS Authentication
- •Configuring Authentication in ASP.NET
- •Securing SQL Server
- •Summary
- •Deployment Scenarios
- •Deployment Editors
- •Creating a Deployment Project
- •Adding the Output of SkySharkDeploy to the Deployment Project
- •Deploying the Project to a Web Server on Another Computer
- •Summary
- •Organization Profile
- •Project Requirements
- •Querying for Information about All Books
- •Querying for Information about Books Based on Criteria
- •Ordering a Book on the Web Site
- •Project Design
- •Database Design
- •Database Schema
- •Web Forms Design
- •Flowcharts for the Web Forms Modules
- •Summary
- •Introduction to ASP.NET Web Services
- •Web Service Architecture
- •Working of a Web Service
- •Technologies Used in Web Services
- •XML in a Web Service
- •WSDL in a Web Service
- •SOAP in a Web Service
- •UDDI in a Web Service
- •Web Services in the .NET Framework
- •The Default Code Generated for a Web Service
- •Testing the SampleWebService Web Service
- •Summary
- •Creating the SearchAll() Web Method
- •Creating the SrchISBN() Web Method
- •Creating the AcceptDetails() Web Method
- •Creating the GenerateOrder() Web Method
- •Testing the Web Service
- •Securing a Web Service
- •Summary
- •Creating the Web Forms for the Bookers Paradise Web Site
- •Adding Code to the Web Forms
- •Summary
- •Case Study
- •Project Life Cycle
- •Analyzing Requirements
- •High-Level Design
- •Low-Level Design
- •Summary
- •Overview of Mobile Applications
- •The Microsoft Mobile Internet Toolkit
- •Overview of WAP
- •The WAP Architecture
- •Overview of WML
- •The Mobile Web Form
- •The Design of the MobileTimeRetriever Application
- •Creating the Interface for the Mobile Web Forms
- •Adding Code to the MobileTimeRetriever Application
- •Summary
- •Creating the Forms Required for the MobileCallStatus Application
- •Creating the frmLogon Form
- •Creating the frmSelectOption Form
- •Creating the frmPending Form
- •Creating the frmUnattended Form
- •Adding Code to the Submit Button in the frmLogon Form
- •Adding Code to the Query Button in the frmSelectOption Form
- •Adding Code to the Mark checked as complete Button in the frmPending Form
- •Adding Code to the Back Button in the frmPending Form
- •Adding Code to the Accept checked call(s) Button in the frmUnattended Form
- •Adding Code to the Back Button in the frmUnattended Form
- •Summary
- •What Is COM?
- •Windows DNA
- •Microsoft Transaction Server (MTS)
- •.NET Interoperability
- •COM Interoperability
- •Messaging
- •Benefits of Message Queues
- •Limitations
- •Key Messaging Terms
- •Summary
- •Pointers
- •Declaring Pointers
- •Types of Code
- •Implementing Pointers
- •Using Pointers with Managed Code
- •Working with Pointers
- •Compiling Unsafe Code
- •Summary
- •Introduction to the Languages of Visual Studio .NET
- •Visual C# .NET
- •Visual Basic .NET
- •Visual C++ .NET
- •Overview of Visual Basic .NET
- •Abstraction
- •Encapsulation
- •Inheritance
- •Polymorphism
- •Components of Visual Basic .NET
- •Variables
- •Constants
- •Operators
- •Arrays
- •Collections
- •Procedures
- •Arguments
- •Functions
- •Adding Code to the Submit Button
- •Adding Code to the Exit Button
- •Summary
- •Introduction to Visual Studio .NET IDE
- •Menu Bar
- •Toolbars
- •Visual Studio .NET IDE Windows
- •Toolbox
- •The Task List Window
- •Managing Windows
- •Customizing Visual Studio .NET IDE
- •The Options Dialog Box
- •The Customize Dialog Box
- •Summary
- •Index
DESIGNING THE APPLICATION |
Chapter 20 |
465 |
|
|
|
|
|
Designing Application Forms
The application provides different forms for users in different roles. For example, business managers are provided with four forms: AddFl.aspx, RequestID.aspx, Reports.aspx, and FreqFl.aspx. All forms pertaining to different roles were discussed in Chapter 18.
In this section, I explain the controls that you need to add to each Web form and the properties of Web forms that you need to configure. After this section, all Web forms for the application will be ready.
Standardizing the Interface of the Application
All Web forms for the SkyShark Airlines application have a standard interface, which is derived by adding a banner to a header.htm file and including the file on each Web page. Next, I have added a menu bar, which resembles a tab control, on top of each Web form. To do this, I created four similar images with different tabs selected and showing the images at the same position on each Web form. A collage of these images is shown in Figure 20-4.
FIGURE 20-4 Creating a menu bar for the application
Now, when a user selects different screens, distinct images are displayed but give the impression that the same screen contains several tabs.
Common Forms in the Application
There are a number of common forms used by employees at all positions in SkyShark Airlines. In this section, I will explain the design of these forms.
466 Project 4 CREATING AN AIRLINE RESERVATION PORTAL
Default.aspx
The default.aspx form is the first form displayed when a user visits a Web site. The default.aspx form is the logon form for the Web application. When users visit the Web application, they need to log on by specifying their logon credentials in the default.aspx form. Subsequently, depending upon the position of the user, the user is redirected to other forms of the Web application.
You can change the form WebForm1.aspx, added to the Web application by default, to make the form the default.aspx page. To do so, follow these steps:
1.Right-click on WebForm1.aspx in Solution Explorer and select Rename.
2.Type the name of the form as default.aspx.
3.Double-click on default.aspx to open the code-behind file in the Code Editor window.
4.Change the name of the class to WebLogonForm.
5.Return to the design view of the default.aspx form.
6.In the design view of the form, in the @ Page directive in the first line, change the name of the class to WebLogonForm. The new @ Page directive is given as follows:
<%@ Page language=”c#” Codebehind=”default.aspx.cs” AutoEventWireup=”false”
Inherits=”SkyShark.WebLogonForm” %>
NOTE
By performing these steps, you have changed the name and the default class associated with the Web form.These steps need to be carried out for all Web forms that you will add to the project. However, I will not repeat these steps separately for each Web form.
To design the default.aspx form, add controls to it and change their properties as shown in Table 20-2.
|
DESIGNING THE APPLICATION |
Chapter 20 |
467 |
|||
Table 20-2 Controls in the Default.aspx Form |
|
|
|
|
|
|
|
|
|
|
|
||
|
|
|
|
|
|
|
Control Type |
ID |
Properties Changed |
|
|
|
|
|
|
|
|
|
|
|
TextBox |
txtUserName |
None |
|
|
|
|
TextBox |
txtPassword |
TextMode=Password |
|
|
|
|
Button |
btnSubmit |
Text=Submit |
|
|
|
|
Label |
lblMessage |
ForeColor=Red |
|
|
|
|
|
|
Text="" |
|
|
|
|
|
|
Font:Bold=True |
|
|
|
|
RequiredFieldValidator |
RequiredFieldValidator |
ControlToValidate=txtUserName |
|
|||
|
|
ErrorMessage=Please specify a valid |
|
|||
|
|
user name. |
|
|
|
|
RequiredFieldValidator |
RequiredFieldValidator2 |
ControlToValidate=txtPassword |
|
|||
|
|
ErrorMessage=Please specify a valid |
|
|||
|
|
password. |
|
|
|
|
|
|
|
|
|
|
|
In the preceding table, I have not included the details of the User Name and Password labels. You need to add these controls to the form as well. The completed default.aspx form is shown in Figure 20-5.
FIGURE 20-5 The default.aspx page
468 Project 4 CREATING AN AIRLINE RESERVATION PORTAL
Logoff.aspx
The Logoff.aspx form is used to display the logoff page when a user logs off from the Web site.The controls I have added to the Logoff.aspx form are summarized in Table 20-3.
Table 20-3 Controls in the Logoff.aspx Form
|
Control Type |
ID |
|
|
Y |
|
|
|
|
|
|
Properties Changed |
|
||
|
TextArea |
None |
|
L |
|
||
|
Hyperlink |
|
F |
NavigateUrl=default.aspx |
|
||
|
HyperLink1 |
|
|
|
|||
|
|
|
M |
|
Text=Click here to logon. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
A |
|
|
|
|
|
|
TIP |
E |
|
|
|
|
|
|
TextArea is an H |
T |
|
|
|
|
|
|
ML control. herefore, you need not specify any values for the |
|
|||||
control.
The Logoff.aspx page is shown in Figure 20-6.
FIGURE 20-6 The Logoff.aspx page
Team-Fly®
DESIGNING THE APPLICATION |
Chapter 20 |
469 |
|
|
|
|
|
ChangePassword.aspx
The ChangePassword.aspx form is used by authenticated users to change their passwords. The controls you need to add to the ChangePassword.aspx form are given in Table 20-4.
Table 20-4 Controls in the ChangePassword.aspx Form
Control Type |
ID |
Properties Changed |
Label |
txtUser |
Text=Changing Password for: |
TextBox |
txtPassword |
TextMode=Password |
TextBox |
txtConfPassword |
TextMode=Password |
Button |
btnSubmit |
Text=Submit |
RequiredFieldValidator |
RequiredFieldValidator1 |
ErrorMessage=Please specify a valid |
|
|
password. |
|
|
ControlToValidate=txtPassword |
RequiredFieldValidator |
RequiredFieldValidator2 |
ErrorMessage=Please specify a valid |
|
|
password. |
|
|
ControlToValidate=txtConfPassword |
CompareValidator |
CompareValidator1 |
ErrorMessage=The passwords |
|
|
specified by you do not match. |
|
|
Please try again. |
|
|
ControlToValidate=txtConfPassword |
|
|
ControlToCompare=txtPassword |
|
|
|
In the ChangePassword.aspx form,the txtUser control is used to display the logon name of the user who is currently logged on.This control is common to all forms in the application. The CompareValidator1 control is used to ensure that the user specifies identical values in the txtPassword and txtConfPassword controls. The completed ChangePassword.aspx form is shown in Figure 20-7.