- •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
846 |
Part X |
APPENDIXES |
|
|
|
extensions.Therefore, using managed extensions, the existing code can be reused, saving both time and effort. You can also use managed extensions to merge both unmanaged and managed C++ code in an application.
Attributes that enable you to extend the functionality of a language and simplify the creation of COM components are supported by Visual C++ .NET. You can also apply classes, data members, or member functions to attributes.
Overview of Visual Basic .NET
The complete framework of Visual Basic .NET is based on the .NET Framework. Visual Basic .NET inherits the various features of the .NET Framework along with features of the earlier versions of Visual Basic. In this section, you will learn about the features of Visual Basic .NET as compared to the features in the earlier versions of Visual Basic.
As discussed earlier, Visual Basic .NET supports implementation inheritance as compared to the earlier versions of Visual Basic that supported interface inheritance. In other words, you can implement only interfaces with the earlier versions of Visual Basic. All the methods of the interface need to be implemented when you implement an interface in Visual Basic 6.0. In addition, the code has to be rewritten each time you implement the interface.
Visual Basic .NET, on the other hand, supports implementation inheritance.This implies that while applications are created in Visual Basic .NET, a class can also be derived from another class, which is known as the base class. The methods and properties of the base class are inherited by the derived class. In the derived class, you can either use or override the code that already exists in the base class.Therefore, code can be reused with the help of implementation inheritance. Although multiple interfaces can be implemented in a class in Visual Basic .NET, the class can inherit from only one class.
Visual Basic .NET also provides constructors and procedures, where constructors are used to initialize objects. The Sub New procedure replaces the Class_Initialize event in Visual Basic .NET. The Sub New procedure is executed when an object of the class is created, unlike the Class_Initialize event that is available in the earlier versions of Visual Basic.The first procedure to be executed in a class is the Sub New procedure. Instead of the Class_Terminate event, the Sub Finalize procedure is available in Visual Basic .NET. When an object is destroyed, the Sub
INTRODUCTION TO VISUAL BASIC .NET Appendix B 847
Finalize procedure is automatically called to complete the tasks that remain incomplete. In addition, the Sub Finalize procedure can only be called from the class to which it belongs or from the classes from which it is derived.
Visual Basic .NET has another additional feature known as garbage collection. Allocated resources such as objects and variables are monitored by the .NET Framework. In addition, the destroying objects, which are no longer in use, automatically release memory for reusing the objects in the .NET Framework. When an object is set to Nothing, in Visual Basic 6.0, it is destroyed automatically, whereas in Visual Basic .NET, it continues to occupy space even when it is set to Nothing. In Visual Basic .NET, the garbage collector checks the objects that are not currently used by the applications.The garbage collector releases the memory occupied by the object when any object is found marked for garbage collection.
The GC class, the Sub Finalize procedure, and the IDisposable interface are used to perform garbage selection operations in the .NET Framework. The System namespace contains the GC class that provides various methods that enable you to control the system garbage collector. In the .NET Framework, a member of the Object class, the Sub Finalize procedure, acts as a destructor. You can also override this procedure in your applications. However, the Sub Finalize procedure is not executed when the application is executed. The Sub Finalize procedure is called by the GC class to release the memory that is occupied by a destroyed object. However, an explicit way of managing resources in the form of the IDisposable interface is provided by the .NET Framework.The Dispose() method is included in the IDisposable interface. After the IDisposable interface is implemented, the Dispose() method can be overridden in the applications. You can release resources and database connections in the Dispose() method.
Overloading is a feature that enables you to define several procedures with the same name, where each procedure has a different set of arguments. Visual Basic
.NET supports this feature of overloading as compared to the earlier versions of Visual Basic. You can use overloading for constructors and properties in a class along with the procedures. The Overloads keyword is used for overloading procedures.
Consider a scenario in which a procedure needs to be created to display the address of an employee. The address of the employee should be viewed based on either the employee name or the employee code, which can be done by using the overload feature. You need to create two procedures with the same name but
848 |
Part X |
APPENDIXES |
|
|
|
different arguments. The employee name is accepted as the argument by the first procedure, and the employee code is accepted as the argument by the second.
The .NET Framework class library is organized into namespaces. A namespace is referred to as a collection of classes. You can logically group classes within an assembly by using namespaces. In addition to Visual Basic .NET, these namespaces are available in all the .NET languages.
In Visual Basic .NET, you use the Imports statement to access the classes in namespaces. Consider an example: To use a button control as defined in the System.Windows.Forms namespace, you include the statement mentioned here in the
beginning of the program. |
|
Y |
||
|
|
|
||
Imports System.Windows.Forms |
L |
|||
F |
||||
|
|
|||
After the Imports statement has been added, a new button can be created using |
||||
the following code: |
|
M |
|
|
|
|
|
||
Dim button1 as Button |
A |
|
||
|
|
|||
If you do not include theEImports statement in the program, the full reference path |
||||
T |
|
|
of the class to create a button needs to be used. If the Imports statement is not used, then the following code can be used for creating a button:
Dim button1 as System.Windows.Forms.Button
TIP
In addition to using the namespaces already available in Visual Basic .NET, you can create your own namespaces. In the next appendix, you will learn how to create a namespace.
As already discussed, Visual Basic .NET also supports multithreading. A multithreaded application can simultaneously handle multiple tasks. Multithreading can also be used to decrease the time taken by an application to respond to user interaction. You need to ensure that a separate thread in the application handles user interaction so that the time taken by an application to respond to user interaction is decreased.
Team-Fly®
INTRODUCTION TO VISUAL BASIC .NET Appendix B 849
Visual Basic .NET enables you to detect and remove errors at run time by supporting structured exception handling. In Visual Basic .NET, you can use Try…Catch…Finally statements to create exception handlers. By using Try…Catch…Finally statements, you can create strong and efficient exception handlers to improve the performance of the application.
You have considered the new and added features of Visual Basic .NET. The following sections discuss the features of an object-oriented programming language.
Features of an Object-Oriented
Programming Language
In an object-oriented programming language, objects serve as the building blocks of a programming language, displaying a unique identity and behavior. A chair, a table, and a book are examples of objects that are used every day. An object in a programming language is defined as an instance of a class. Applications created in an object-oriented programming language are made up of objects.
An object is qualified as an object-oriented programming language if the following features are supported:
Abstraction
Encapsulation
Inheritance
Polymorphism
The next sections will consider each of the features mentioned here in detail.
Abstraction
Before you buy a television set, you consider its size, durability, and features. As a buyer, you may not be interested in knowing about the machinery of the television set.The main features of the television set are more likely to be your primary concern. This is known as abstraction. In a programming language, abstraction helps you focus mainly on the essential aspects of an object. The nonessential aspects are normally overlooked.