- •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
COMPONENTS OF C# |
Chapter 3 |
51 |
|
|
|
The Finalize() method does not return any value. In addition, you cannot pass parameters to the Finalize() method and directly override it.
Before C# calls the Finalize() method, it waits for some time after the object instance is no longer used by any program code.This unnecessarily blocks memory and destroys resources in longer time duration. To tackle this problem, C# provides you with the Dispose() and Close() methods.
Dispose() and Close() Methods
In C#, you can explicitly call the Dispose() and Close() methods to destroy the resources immediately after the class instance is deleted. These methods are not implicitly invoked. Therefore, if you forget to call the Dispose() or Close() methods, the resources remain in memory until the garbage collection system cleans the memory. To solve this problem, you can use the Dispose() and Close() methods with the Finalize() method. If the Dispose() or Close() method is not explicitly called, the Finalize() method will clean the memory before the garbage collection system is invoked.
Having learned about the Finalize(), Dispose(), and Close() methods, you can take a look at the methods used with classes in detail.
Methods
A method is a logical section of code that can be used to perform a specific operation. An object or a class can call a method to implement the functionality of the method. A method has a return type or can be of the type void.
Declaring a Method
The syntax of method declaration is as shown here:
< modifier> <return type> <method name> (parameter1, parameter2, ........)
{
statements
}
Here, modifier is the access modifier and return type specifies the data type of the value that is returned by the method. The list of parameters that the method takes is specified in the parentheses following the method name.
52 |
Part II |
HANDLING DATA |
|
|
|
Calling a Method
After a method is declared, you can call the method to be used by any class or an object. To call a method, you use the following syntax:
object1.method1 (parameter1, parameter2,...);
Here, object1 is the instance of the class that calls the method, method1 is the name of the method, and the parameter list is specified within parentheses.
Passing Parameters to Methods
While calling a method, you can pass a list of parameters to the method. The types of parameters that can be passed to a method are:
Value parameters
Reference parameters
Output parameter
Parameter arrays
The parameters that are passed by value to a method are called value parameters. When a variable is passed by value, the method changes the value of the variable in a copy. However, the actual value remains unchanged. Therefore, the value parameters are not affected by the changes that are made to the variables in the method. By default, all variables are passed as value parameters.
The value of variables that are passed by reference, known as reference parameters, changes when you modify the variable in a method. When a variable is passed by reference, the variable passes only a reference to the method and not the actual value. Therefore, changes made by the method are made to the original variable and not to its copy. C# overwrites the changes to the original value of the variable. The ref keyword is used to pass a variable to a method by reference.
The syntax of a method to which you pass a parameter by reference is:
object1.method1 (parameter1, ref parameter2,...);
Here, parameter1 is passed by value. However, parameter2 is passed by reference. Therefore, the value of parameter1 will not be affected by the changes made to it during method execution. However, if changes are made to parameter2 in the method body, the changes will get reflected to its original value.
COMPONENTS OF C# |
Chapter 3 |
53 |
|
|
|
TIP
In contrast to variables, strings do not change even when passed by reference. When you make a change to the value of a string, C# creates a new string.
In general, methods return a single value. In C#, you can write methods that return multiple values. To do so, you pass a parameter to the method as an output parameter. An output parameter is passed to a method by using the out keyword.
object1.method1 (out parameter1);
Here, parameter1 is passed to method1 as an output parameter.
In C#, it is essential that you initialize a variable before using it.Therefore, when you pass an output parameter, it already has some value. C# overwrites this value with the value returned by the method. This is a waste and can be avoided by using the out keyword. A variable prefixed with the out keyword is an exception, as you can pass it to a method without initializing it.The output parameter is initialized by the value returned by the method. A variable can store an output value only if you pass the variable to the method by reference.
In addition to variables, you can pass arrays as a parameter to a method. However, only a one-dimensional array can be passed to a method. You use the params keyword to specify a parameter array.
The syntax of passing a parameter array is:
object1.method1 (parameter1, params data type[] parameter2);
In the previous syntax, parameter2 is a one-dimensional array, and its type is specified by the data type.
When you declare a parameter array along with other parameters, you must include the parameter array as the last element in the list. In addition, you cannot include a parameter array with a reference or an output parameter. Therefore, the following code will generate an error:
object1.method1 (params data type[] parameter1, ref parameter2);
54 |
Part II |
HANDLING DATA |
|
|
|
Method Modifiers
Similar to classes, methods in C# also have modifiers. Following are some of the commonly used method modifiers.
static. A static method cannot be called by any particular instance of a class. To call a static method, you need to specify the name of the container class.
new. A new method in C# is used to suppress the compiler’s warning when you try to hide a method of a base class with the same name as the derived class method.
public. Similar to the public modifier of a class, if you declare a method as public, it can be accessed from any location.The method can also be called from outside the class that declares it.
private. A method declared as private is private to the class that declares it. This implies that a private method cannot be called from outside the class that contains the method.
protected. A protected method modifier is similar to a protected class modifier. A method declared as protected can be called from the derived classes of the class that contains the method, in addition to the class that declares the method.
internal. An internal method can be called from anywhere in the assembly.
extern. An extern method in C# has an unlimited scope. You can use a method declared as extern even in a different language.
virtual. A derived class of a class that contains a method can override a virtual method. You can also implement a virtual method dynamically. However, the method that will get invoked will be decided at run time.
A virtual modifier cannot be used with static, override, and abstract modifiers.
abstract. An abstract method is a special type of a virtual method. An abstract method can define a method. However, you cannot implement an abstract method. You can only declare an abstract method in an
abstract class.
override. The override method is used to override an inherited abstract or virtual method.