- •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 |
481 |
|
|
|
|
|
FIGURE 20-14 The QueryStat.aspx form
ConfirmRes.aspx
The ConfirmRes.aspx form is used to confirm reservations before flight departure. Just as with the CancelRes.aspx form, the ConfirmRes.aspx form uses the ticket number to confirm a reservation.
Summary
This chapter discussed how to design an application for an airline portal.The first step to design the application is to create the database schema by using either SQL Server Enterprise Manager or Query Analyzer.
The next step is to design the Web forms of the application by using the list of controls specified against each form of the application. Then, you change the default name and classes associated with each Web form. Finally, you update the changed class name in the @ Page directive of the Web form so that the application can identify the classes associated with each Web form. The design of your application is now ready.
This page intentionally left blank
Chapter 21
Implementing the
Business Logic
484 Project 4 CREATING AN AIRLINE RESERVATION PORTAL
In the last chapter, you designed the forms for the SkyShark Airlines application. In this chapter, you will implement the business logic for running the application and fulfilling the business requirements of SkyShark Airlines that were dis-
cussed in Chapter 18, “Project Case Study and Design.”
Coding the Logon and Logoff
Functionality
The logon and logoff functionality of the Web application is implemented by the use of Session variables. To log on to the Web site, the user supplies the logon name and password on the default.aspx page. After the user has been successfully authenticated, the username and the role of the user are stored in session variables. These values are used for identifying the user on each page of the Web application. When the user decides to log off, the Session variables for the user are cleared and the user is no longer able to browse the Web site.
TIP
You can also authenticate users by using the ASP.NET authentication mechanism. This mechanism is discussed in Chapter 25, “Securing the Application.”
The next sections will implement the functionality described previously in the default.aspx and Logoff.aspx forms.
The Default.aspx Form
The default.aspx form uses the dtUsers table to authenticate users. Before you write the code for the default.aspx form, drag the dtUsers table from Server Explorer to the design view of the form. Visual Studio .NET automatically configures SqlDataAdapter and SqlConnection controls for the form. You can read a
IMPLEMENTING THE BUSINESS LOGIC |
Chapter 21 |
485 |
|
|
|
|
|
description of these controls in Chapter 19, “Basics of ASP.NET Web Applications,” in the section “Coding the Application.”
After you add SqlDataAdapter and SqlConnection controls to the form, you can generate a dataset for the form. To generate the dataset, follow these steps:
1.Click anywhere on the form.
2.Click on the Data menu and select Generate Dataset.The Generate Dataset dialog box will appear.
3.In the Generate Dataset dialog box, click on the New option and click on OK.
4.A new DataSet control is added to your project.
All the three data controls are visible in Component Designer in the Design view of the form, as you can see in Figure 21-1.
FIGURE 21-1 Data controls appear in Component Designer
A DataAdapter control has a default set of queries associated with it for selecting, inserting, updating, and deleting data from the SQL Ser ver table with which the DataAdapter control is associated.These queries are specified by the SelectCommand, InsertCommand, UpdateCommand, and DeleteCommand properties of the DataAdapter control.
486 Project 4 CREATING AN AIRLINE RESERVATION PORTAL
If required, you can change the default queries associated with the DataAdapter control. For example, the default SelectCommand associated with the sqlDataAdapter1 control, which you added to the form for the dtUsers table, is
SELECT Username, Password, Role, PasswordChanged FROM dtUsers. This quer y
returns all the records from the dtUsers table.
However, to validate a single user, you need not retrieve all the records from the dtUsers table. Therefore, you can modify the SelectCommand property to
SELECT Username, Password, Role, PasswordChanged FROM dtUsers WHERE
(UserName=@username). The modified query accepts the @username parameter at run time and retrieves the record from the table that has the same username as specified by the user.
After you add and configure data controls for the default.aspx form, double-click on Submit to write the code for the Click event of the form.
The code for the Click event of the Submit button is logically divided into three parts:
1.Retrieve data from the dtUsers table. The username and password specified by the user are used to retrieve the details of the user from the
dtUsers table. To retrieve data, you can use the Fill method of the sqlDataAdapter1 control.The Fill method runs the SELECT query associated with the control and updates data into the dataset that is passed to the method as a parameter. The code for retrieving data from the database is given as follows:
string username, password; int datarows;
username=txtUserName.Text.Trim(); password=txtPassword.Text.Trim(); sqlConnection1.Open();
sqlDataAdapter1.SelectCommand.Parameters[“@UserName”].Value=username; datarows=sqlDataAdapter1.Fill(dataSet11,”UserDetails”); sqlConnection1.Close();
2.Check username and password supplied by the user. If the username specified by the user matches with any record in the database, then the data inserted into the dataset will have at least one row in it. The number of records retrieved from the database can be ascertained by checking the return value of the Fill method described previously. If no rows have
IMPLEMENTING THE BUSINESS LOGIC |
Chapter 21 |
487 |
|
|
|
|
|
been returned by the SELECT query, then the username specified by the user is incorrect. However, if the SELECT query returns data but the password does not match, then the password specified by the user is incorrect. The code that uses the logic described above to check the username and password is given as follows:
if (datarows==0) lblMessage.Text=”Incorrect user name”;
else
{
if (dataSet11.Tables[“UserDetails”].Rows[0][1].ToString(). Trim()==password)
{
//The credentials supplied by the user are correct
}
else
lblMessage.Text=”Incorrect password”;
}
3.Store username and role in session variables and redirect the user.
When the user is successfully authenticated, the username and the role of the user are stored in Session variables and the user is redirected to the home page of one of the roles in the organization, depending upon the role of the user retrieved from the database. The code to implement this functionality is given as follows:
string Role; Role=dataSet11.Tables[“UserDetails”].Rows[0][2].ToString().Trim(); Session[“usrName”]=username;
Session[“usrRole”]=Role; if (Role==”Disabled”)
{
lblMessage.Text=”Your account has been disabled. Please contact the network administrator.”;
return;
}
FormsAuthentication.GetAuthCookie(username,false); switch(Role)
488 |
Project 4 |
CREATING AN AIRLINE RESERVATION PORTAL |
|||
|
|
{ |
|
|
|
|
|
|
|
|
|
|
|
case “Admin”: |
|
|
|
|
|
Response.Redirect(“.\\NA\\ManageUsers.aspx”); |
|||
|
|
break; |
|
|
|
|
|
case “BM”: |
|
|
|
|
|
Response.Redirect(“.\\BM\\AddFl.aspx”); |
|||
|
|
break; |
|
|
Y |
|
|
case “LOB”: |
|
|
|
|
|
|
|
|
|
|
|
Response.Redirect(“.\\LOB\\CreateRes.aspx”); |
|||
|
|
break; |
|
|
|
|
|
} |
|
M |
|
|
|
|
|
|
|
|
The complete code of the Click event ofLSubmit button, which incorporates the |
||||
|
functionality described previously, isFgiven as follows: |
||||
|
|
E |
|
||
|
private void btnSubmit_Click(object sender, System.EventArgs e) |
||||
{ |
T |
|
|
||
|
if (Page.IsValid==true) |
A |
|
{
string username, password; int datarows;
username=txtUserName.Text.Trim(); password=txtPassword.Text.Trim(); sqlConnection1.Open();
sqlDataAdapter1.SelectCommand.Parameters[“@UserName”].Value=username; datarows=sqlDataAdapter1.Fill(dataSet11,”UserDetails”); sqlConnection1.Close();
if (datarows==0) lblMessage.Text=”Incorrect user name”;
else
{
if (dataSet11.Tables[“UserDetails”].Rows[0][1].ToString().Trim()==password)
{
string Role; Role=dataSet11.Tables[“UserDetails”].Rows[0][2].ToString().Trim(); Session[“usrName”]=username;
Session[“usrRole”]=Role; if (Role==”Disabled”)
{
Team-Fly®