- •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
852 |
Part X |
APPENDIXES |
|
|
|
Polymorphism helps you to perform different functions by using the same methods. To elaborate, the implementation of a base class can be changed in the derived classes. Therefore, when two classes are derived from the same class, a method can be created with the same name in both the classes. Based on the task that needs to be performed, you can select the method.
You learned about the features of object-oriented programming language, such as abstraction, encapsulation, inheritance, and polymorphism. Now, have a look at the components of Visual Basic .NET.
Components of Visual Basic .NET
You have learned about the components of Visual C# .NET throughout this book.This appendix discusses the components of Visual Basic .NET. These components include variables, constants, operators, arrays, collections, procedures, arguments, and functions.
Variables
Applications deal mostly with different types of data, such as text or numeric. This data needs to be stored by an application for later use and for performing certain operations on the data. It also needs to be stored for performing certain operations, such as calculating totals. A programming language uses variables in order to store data. A temporary memory location is called a variable that has a name or a word to refer to and a data type to determine the kind of data it can hold.
Visual Basic .NET provides various data types that help in storing different kinds of data. In the following section, you will learn more about the data types.
Data Types
The kind of data that a variable can hold is referred to as a data type. Integer, Long, and Byte are some of the data types that are provided by Visual Basic .NET. Table B-1 lists the various data types of Visual Basic .NET.
|
INTRODUCTION TO VISUAL BASIC .NET |
Appendix B |
|
853 |
|
|
|
||||
Table B-1 Data Types in Visual Basic .NET |
|
|
|
|
|
|
|
|
|
||
|
|
|
|
|
|
Data Type |
Description |
|
|
|
|
|
|
|
|
|
|
Integer |
The numeric data is stored.This data type stores the Integer data as a 32-bit |
|
|
||
|
(4 bytes) number. |
|
|
|
|
Long |
The numeric data that can exceed the range supported by the Integer data type |
|
|
||
|
that is stored. It stores the value of Long as a 64-bit (8 bytes) number. |
|
|
||
Short |
The smaller range of numeric data (between –32,678 to 32,767) is stored.This |
|
|
||
|
data type stores the Short data as a 16-bit (2 bytes) number. |
|
|
|
|
Byte |
The binary data is stored.This data type can also store ASCII character values |
|
|
||
|
in the numeric form. |
|
|
|
|
Char |
A single character is stored.This data type stores the Char data as a 16-bit (2 |
|
|
||
|
bytes) unsigned number. |
|
|
|
|
DateTime |
The date and time data is stored.This data type stores the date and time data |
|
|
||
|
as IEEE 64-bit (8 bytes) long integers. |
|
|
|
|
String |
The alphanumeric data, which is data containing numbers and text,is stored. |
|
|
||
Object |
The data of any t ype, such as Integer, Boolean, String, or Long, is stored. |
|
|
||
Double |
The large floating-point numbers are stored.This data type stores the Double |
|
|
||
|
data as an IEEE 64-bit (8 bytes) floating-point number. |
|
|
|
|
Single |
The single precision floating-point values are stored.This data type stores the |
|
|
||
|
Single data as an IEEE 32-bit (4 bytes) floating-point number. |
|
|
|
|
Decimal |
The very large floating-point values are stored.This data type stores the |
|
|
||
|
Decimal data as a 128-bit (16 bytes) signed integer to the power of 10. |
|
|
||
Boolean |
The data that can have only two values is stored.This data type stores the True |
|
|
||
|
and False Boolean data as a 16-bit (2 bytes) number. |
|
|
|
|
|
|
|
|
|
|
As compared to the earlier versions of Visual Basic, some changes in data types of Visual Basic .NET are mentioned as follows.
The Variant data type is used to store any type of data in Visual Basic 6.0. This is similar to the Object data type in Visual Basic .NET.
The Double data type is used to store a date in Visual Basic 6.0. The DateTime data type stores data in the date and time format in Visual Basic .NET.
854 |
Part X |
APPENDIXES |
|
|
|
The Currency data type is not supported by Visual Basic .NET. Instead, the Decimal data type is used to store currency values.
After having a look at the various data types, you can now examine how variables are declared in Visual Basic .NET.
Variable Declarations
To provide information about a variable to a program in advance is known as declaring a variable. The Dim statement is used to declare a variable. To declare a variable, you can use the following syntax:
Dim VariableName As type
The As type clause in the Dim statement is optional, and it defines the object type or the data type of the variable that you are declaring. Now, consider the following statement:
Dim int1 as Integer
Dim str1 as String
An Integer variable known as int1 is declared by the first statement, and a String variable known as str1 is declared by the second variable.
Variables can also be declared using the identifier type characters. These characters also specify the data type of a variable. You can consider the following statement as an example:
Dim str1$
In the statement, the identifier type character for a String variable is specified by $. The various identifier type characters that can be used in Visual Basic .NET are listed in Table B-2.
|
INTRODUCTION TO VISUAL BASIC .NET Appendix B |
855 |
||
|
|
|
||
Table B-2 Identifier Type Characters in Visual Basic .NET |
||||
|
|
|
|
|
Data Type |
Identifier Type Character |
|||
|
|
|
|
|
Integer |
% |
|
|
|
Long |
& |
|
|
|
Decimal |
@ |
|
|
|
String |
$ |
|
|
|
Single |
! |
|
|
|
Double |
# |
|
|
|
|
|
|
|
|
You should consider some of the ground rules for naming a variable before discussing the various variable declarations that are possible in Visual Basic .NET. However, it is not necessary for you to follow these naming conventions. Following the naming convention makes the code easy to understand for anyone who wants to understand the code.
Some of the ground rules of naming a variable are:
A variable must begin with a letter.
A variable cannot contain a period or identifier type character.
A variable must not exceed 255 characters.
A variable must be unique within the same scope, defined as the range from which a variable can be accessed, such as a procedure, a form, or a module.
NOTE
A module is defined as a collection of procedures where a procedure is a set of statements used to perform some specific tasks.
You learned how to declare a variable. You will now learn how to initialize variables.
856 |
Part X |
APPENDIXES |
|
|
|
Variable Initialization
A variable contains a value when it is declared. Consider the following example: By default, an Integer variable contains 0 and a Boolean variable stores False as the value.
To set a start value, you can initialize a variable. The following code explains the variable:
Dim int1 as Integer int1 = 20
An Integer variable, int1, is declared by the first statement, while the second statement initializes it to the value 20. In the earlier versions of Visual Basic, the initialization of variables was not allowed in the same line as their declarations. But now, Visual Basic .NET allows it.Therefore, the code can now be written as:
Dim int1 As Integer = 20
Variable Scope
The scope of a variable determines the part of the program or application that can use the variable. Consider an example. A variable can be used only within a particular block of code or the entire program. Based on its scope, a variable can be called local or module-level. You can also refer to the scope of a variable as its accessibility.
If a variable is declared inside a procedure, it can only be accessed within that procedure. The variable is then referred to as a local variable. At times, you need to use a variable across modules within an application or throughout the application. The variable is then referred to as module-level variables.The declaration section of the module declares these variables. Module-level variables can be further clas-
sified as private or public.
The modules that can be used within the module in which they are declared are known as private modules.These modules are declared only at the module-level. A private variable is declared in the following statements:
Private Dim int1 As Integer
or
Private int1 As Integer