A PROJECT REPORT

ON

ONLINE JOB PORTAL

Submitted by
Prateek kulshrestha
Vishesh vashisht
Jayant kumar

Under the Guidance of

Ms. Simple Sharma
Asst. Professor

in partial fulfillment for the award of the degree of

BACHELOR OF TECHNOLOGY
IN
INFORMATION TECHNOLOGY

Faculty of Engineering & Technology

Manav Rachna International University, Faridabad
June, 2013
 Acknowledgement

We would like to express our sincere gratitude to our project guide Ms.
Simple Sharma, Assistant Professor, Dept. Of CSE,(FET, MRIU) for
giving us the opportunity to work on this topic. She continually and
convincingly conveyed a spirit of adventure in regard to research and
scholarship, and an excitement in regard to teaching. Without her
guidance and persistent help this project would not have been possible.

We also take this opportunity to express a deep sense of gratitude to Dr.

S.S. Tyagi (Head Of Department) Dept. Of CSE,(FET,MRIU), for his
cordial support, valuable information and guidance, which helped us in
completing this task through various stages

We would like to take opportunity to express my humble gratitude to

Prof. Naresh Grover(Director) of (FET,MRIU) whom we executed this
project. His constant guidance and willingness to share his vast
knowledge made us understand this project and its manifestations in
great depths and helped us to complete the assigned tasks.

We wish to express sincere thanks and gratitude to Dr. M.K. Soni(Dean)

of (FET,MRIU) for his commendable support and encouragement
towards the completion of the project with perfection, which has been a
guiding force and constant source of inspiration to us. It would never be
possible for us to take this project to this level without their innovative
ideas and their relentless support and encouragement.
1. Prateek Kulshrestha 10/FET/IT(S)/2008
2. Vishesh Vashisht 10/FET/IT(S)2019
3. Jayant kumar 10/FET/IT(S)2010
 Declaration

We hereby declare that this project report entitled ONLINE JOB PORTAL
by Prateek Kulshrestha, 10/FET/IT(S)/2008, Vishesh
Vashisht,10/FET/IT(S)2019, Jayant kumar, 10/FET/IT(S)2010 being submitted
in partial fulfillment of the requirements for the degree of Bachelor of Technology
in INFORMATION TECHNOLOGY under Faculty of Engineering & Technology
of Manav Rachna International University Faridabad, during the academic year
2013-2014, is a bonafide record of our original work carried out under guidance
and supervision of Ms. Simple Sharma , Assistant Professor, CSE and has not been
presented elsewhere.

1. Prateek Kulshrestha 10/FET/IT(S)/2008

2. Vishesh Vashisht 10/FET/IT(S)2019

3. Jayant kumar 10/FET/IT(S)2010

 Manav Rachna International University, Faridabad
Faculty of Engineering & Technology
Department of Computer Science & Engineering
June, 2013

Certificate
This is to certify that this project report entitled ONLINE JOB
PORTAL by Prateek Kulshrestha, 10/FET/IT(S)/2008, Vishesh
Vashisht, 10/FET/IT(S)2019, Jayant kumar 10/FET/IT(S)2010
submitted in partial fulfillment of the requirements for the degree of
Bachelor of Technology in INFORMATION TECHNLOGY under
Faculty of Engineering & Technology of Manav Rachna International
University Faridabad, during the academic year 2013-2014, is a bonafide
record of work carried out under my guidance and supervision.

(Signature of Project Guide)

Ms. Simple Sharma
Assistant Professor
Department Of Computer Science & Engineering

(Signature of HoD)
Dr. S.S. Tyagi
Professor and Head
Department Of Computer Science & Engineering
 TABLE OF CONTENTS
1. INTRODUCTION

a. INTRODUCTION TO PROJECT
b. ORGANIZATION PROFILE
c. PURPOSE OF THE PROJECT
d. PROBLEM IN EXISTING SYSTEM
e. SOLUTION OF THESE PROBLEMS

2. SYSTEM ANALYSIS

a. INTRODUCTION
b. SYSTEM WORKFLOW
c. STUDY OF THE SYSTEM
d. HARDWARE & SOFTWARE REQUIRMENT
e. PROPOSED SYSTEM
f. INPUT & OUTPUT
g. PROCESS MODELS USED WITH JUSTIFICATION

3. SOFTWARE REQUIREMENT SPECIFICATIONS

a. FUNCIONAL REQUIREMENTS
b. PERFORMANCE REQUIREMENTS

4. SELECTED SOFTWARE

a. INTRODUCTION TO .NET FRAMEWORK

b. ASP.NET
c. C#.NET
d. SQL SERVER

5. SYSTEM DESIGN

a. E-R DIAGRAM
b. DATA FLOW DIAGRAMS
c. DATA DICTIONARY

6. OUTPUT SCREENS

7. SYSTEM TESTING AND IMPLEMENTATION

 a. INTRODUCTION
b. STRATEGIC APPROACH OF SOFTWARE TESTING

8. SYSTEM SECURITY

a. INTRODUCTION
b. SECURITY IN SOFTWARE

9. CONCLUSION

10. BIBLIOGRAPHY
 ABSTRACT

This project is aimed at developing an online search Portal for the Placement
Dept. of the college. The system is an online application that can be
accessed throughout the organization and outside as well with proper login
provided. This system can be used as an Online Job Portal for the Placement
Dept of the college to manage the student information with regards to
placement. Students logging should be able to upload their information in
the form of a CV. Visitors/Company representatives logging in may also
access/search any information put up by Students.
The project has been planned to be having the view of distributed
architecture, with centralized storage of the database. The application for the
storage of the data has been planned. Using the constructs of MS-SQL
Server and all the user interfaces have been designed using the ASP.Net
technologies. The database connectivity is planned using the SQL
Connection methodology. The standards of security and data protective
mechanism have been given a big choice for proper usage. The application
takes care of different modules and their associated reports, which are
produced as per the applicable strategies and standards that are put
forwarded by the administrative staff.
The entire project has been developed keeping in view of the
distributed client server computing technology, in mind. The specification has
been normalized up to 3NF to eliminate all the anomalies that may arise due
to the database transaction that are executed by the general users and the
organizational administration. The user interfaces are browser specific to
give distributed accessibility for the overall system. The internal database
has been selected as MS-SQL server 200.The basic constructs of table
spaces, clusters and indexes have been exploited to provide higher
consistency and reliability for the data storage. The MS-SQL server 200 was
a choice as it provides the constructs of high-level reliability and security.
The total front end was dominated using the ASP.Net technologies. At all
proper levels high care was taken to check that the system manages the
data consistency with proper business rules or validations. The database
connectivity was planned using the latest SQL Connection technology
provided by Microsoft Corporation. The authentication and authorization was
crosschecked at all the relevant stages. The user level accessibility has been
restricted into two zones namely.
 Chapter 1
INTRODUCTION

1.1. INTRODUCTION TO PROJECT

This project is aimed at developing an online search Portal for the
Placement Details for job seekers. The system is an online application that
can be accessed throughout the organization and outside as well with
proper login provided. This system can be used as an Online Job Portal for
job seekers. Job Seekers logging should be able to upload their information
in the form of a CV. Visitors/Company representatives logging in may also
access/search any information put up by Job aspirants.
.

1.2. ORGANIZATION PROFILE

SOFTWARE SOLUTIONS

xxx Software Solutions is an IT solution provider for a dynamic

environment where business and technology strategies converge. Their
approach focuses on new ways of business combining IT innovation and
adoption while also leveraging an organizations current IT assets. Their
work with large global corporations and new products or services and to
implement prudent business and technology strategies in todays
environment.

XXXS RANGE OF EXPERTISE INCLUDES:

Software Development Services
Engineering Services
Systems Integration
Customer Relationship Management

-9-
 Product Development
Electronic Commerce
Consulting
IT Outsourcing
We apply technology with innovation and responsibility to achieve two broad
objectives:
Effectively address the business issues our customers face today.
Generate new opportunities that will help them stay ahead in the future.

THIS APPROACH RESTS ON:

A strategy where we architect, integrate and manage technology services
and solutions - we call it AIM for success.
A robust offshore development methodology and reduced demand on
customer resources.
A focus on the use of reusable frameworks to provide cost and times
benefits.
They combine the best people, processes and technology to achieve
excellent results - consistency. We offer customers the advantages of:

SPEED:
They understand the importance of timing, of getting there before the
competition. A rich portfolio of reusable, modular frameworks helps jump-
start projects. Tried and tested methodology ensures that we follow a
predictable, low - risk path to achieve results. Our track record is testimony
to complex projects delivered within and evens before schedule.

EXPERTISE:
Our teams combine cutting edge technology skills with rich domain
expertise. Whats equally important - they share a strong customer
orientation that means they actually start by listening to the customer.

- 10 -
Theyre focused on coming up with solutions that serve customer
requirements today and anticipate future needs.

A FULL SERVICE PORTFOLIO:

They offer customers the advantage of being able to Architect,
integrate and manage technology services. This means that they can rely on
one, fully accountable source instead of trying to integrate disparate multi
vendor solutions.

SERVICES:
Xxx is providing its services to companies which are in the field of
production, quality control etc With their rich expertise and experience and
information technology they are in best position to provide software
solutions to distinct business requirements.

1.3. PURPOSE OF THE PROJECT

This system can be used as an Online Job Portal for the Placements
providing to the un employees who are seeking for a job placement. Job
Seeker logging into the system and he can should be able to upload their
information in the form of a CV. Visitors/Company representatives logging in
may also access/search any information put up by Job Seeker.

1.4. PROBLEM IN EXISTING SYSTEM

Cannot Upload and Download the latest updates.
No use of Web Services and Remoting.
Risk of mismanagement and of data when the project is under
development.
Less Security.

- 11 -
 No proper coordination between different Applications and Users.
Fewer Users - Friendly.

1.5. SOLUTION OF THESE PROBLEMS

The development of the new system contains the following activities, which
try to automate the entire process keeping in view of the database
integration approach.

1. User friendliness is provided in the application with various controls.

2. The system makes the overall project management much easier and
flexible.

3. Readily upload the latest updates, allows user to download the alerts
by clicking the URL.

4. There is no risk of data mismanagement at any level while the project

development is under process.

5. It provides high level of security with different level of authentication.

- 12 -
 Chapter 2

SYSTEM ANALYSIS

2.1. INTRODUCTION
After analyzing the requirements of the task to be performed, the next step
is to analyze the problem and understand its context. The first activity in the
phase is studying the existing system and other is to understand the
requirements and domain of the new system. Both the activities are equally
important, but the first activity serves as a basis of giving the functional
specifications and then successful design of the proposed system.
Understanding the properties and requirements of a new system is more
difficult and requires creative thinking and understanding of existing running
system is also difficult, improper understanding of present system can lead
diversion from solution.

2.2. ANALYSIS MODEL

The model that is basically being followed is the WATER FALL MODEL,
which states that the phases are organized in a linear order. First of all the
feasibility study is done. Once that part is over the requirement analysis and
project planning begins. If system exists one and modification and addition
of new module is needed, analysis of present system can be used as basic
model.
The design starts after the requirement analysis is complete and the
coding begins after the design is complete. Once the programming is
completed, the testing is done. In this model the sequence of activities
performed in a software development project are: -
Requirement Analysis

- 13 -
 Project Planning
System design
Detail design
Coding
Unit testing
System integration & testing

Here the linear ordering of these activities is critical. End of the phase
and the output of one phase is the input of other phase. The output of each
phase is to be consistent with the overall requirement of the system. Some
of the qualities of spiral model are also incorporated like after the people
concerned with the project review completion of each of the phase the work
done.

- 14 -
 WATER FALL MODEL was being chosen because all requirements were
known beforehand and the objective of our software development is the
computerization/automation of an already existing manual working system.

Changed Requirements

Communicated
Requirements

Requirements Specification
Requirements Engineering

Design Specification
Design

Executable Software Modules

Programming Maintenance

Integrated Software Product

Process
Integration

Delivered Software Product

Product Product Delivery
Input Output

Fig 2.2: Water Fall Model

2.3. STUDY OF THE SYSTEM

GUIS

In the flexibility of the uses the interface has been developed a graphics concept in
mind, associated through a browses interface. The GUIS at the top level have been
categorized as

- 15 -
 1. Administrative user interface

2. The operational or generic user interface

The administrative user interface concentrates on the consistent information that is

practically, part of the organizational activities and which needs proper
authentication for the data collection. The interfaces help the administrations with
all the transactional states like Data insertion, Data deletion and Date updation
along with the extensive data search capabilities.

The operational or generic user interface helps the users upon the system in
transactions through the existing data and required services. The operational user
interface also helps the ordinary users in managing their own information helps the
ordinary users in managing their own information in a customized manner as per
the assisted flexibilities.

NUMBER OF MODULES

The system after careful analysis has been identified to be presented with the
following modules:

The modules involved are:

Admin
Job Seeker
Job Provider
Notification
Search
Report
Authentication

Admin

In this module Admin will add all the qualifications, skill, experience, city,
state, country and update and delete information about the job provider or
job seeker he can also search for the job seeker and he can send mail to
offer the job to job seeker and he can also see the jobs add by the job
provider.

- 16 -
Job Seeker

In this module Job Seeker register him self and upload his resume and fill
the profile give by admin and after login he will search for the job on various
conditions and he can change his profiles and resume and he can apply for
the jobs based on various conditions. He can see the response of the
company and he can call the company person for the interview.

Job provider

In this module Job Provider register him self and his company and after login
he will add new job and he can search for the job seekers on various
condition and he can offer the job to job seeker according to the job profile
and he can also see the response from the job seekers and send the mail.

Notification

In this module admin and job provider send the notification to the job seeker
in the form of email.

Reports:-
This module contains all the information about the reports generated by the
admin based on the particular job seeker, particular job provider, all job
seeker and job provider, all jobs generated by the job providers.

Authentication:-
This module contains all the information about the authenticated user. User
without his username and password cant enter into the login if he is only
the authenticated user then he can enter to his login.

PROJECT INSTRUCTIONS:
Based on the given requirements, conceptualize the Solution Architecture.
Choose the domain of your interest otherwise develop the application for

- 17 -
 ultimatedotnet.com. Depict the various architectural components, show
interactions and connectedness and show internal and external elements.
Design the web services, web methods and database infrastructure
needed both and client and server.

Provide an environment for upgradation of application for newer versions

that are available in the same domain as web service target.

2.4. HARDWARE SPEDIFICATIONS

HARDWARE REQUIREMENTS:

PIV 2.8 GHz Processor and Above

RAM 512MB and Above
HDD 20 GB Hard Disk Space and Above

SOFTWARE REQUIREMENTS:

WINDOWS OS (XP / 2000 / 200 Server / 2003 Server)

Visual Studio .Net 2005 Enterprise Edition
Internet Information Server 5.0 (IIS)
Visual Studio .Net Framework (Minimal for Deployment)
SQL Server 2000 Enterprise Edition

2.5. PROPOSED SYSTEM

To debug the existing system, remove procedures those cause data

redundancy, make navigational sequence proper. To provide information
about audits on different level and also to reflect the current work status
depending on organization/auditor or date. To build strong password
mechanism.

- 18 -
NEED FOR COMPUTERIZATION

We all know the importance of computerization. The world is moving

ahead at lightening speed and every one is running short of time. One
always wants to get the information and perform a task he/she/they
desire(s) within a short period of time and too with amount of efficiency and
accuracy. The application areas for the computerization have been selected
on the basis of following factors:

Minimizing the manual records kept at different locations.

There will be more data integrity.
Facilitating desired information display, very quickly, by retrieving
information from users.
Facilitating various statistical information which helps in decision-making?
To reduce manual efforts in activities that involved repetitive work.
Updating and deletion of such a huge amount of data will become easier.

FUNCTIONAL FEATURES OF THE MODEL

As far as the project is developed the functionality is simple, the

objective of the proposal is to strengthen the functioning of Audit Status
Monitoring and make them effective and better. The entire scope has been
classified into five streams knows as Coordinator Level, management Level,
Auditor Level, User Level and State Web Coordinator Level. The proposed
software will cover the information needs with respect to each request of the
user group viz. accepting the request, providing vulnerability document
report and the current status of the audit.

WORKING OF THE SYSTEM

The entire scope has been classified into five streams known as: -

- 19 -
Coordinator Level
(Addressing the information management needs of coordinator)
Management Level
(Addressing the information management needs of management)
Auditor Level
(Addressing the information management needs of auditors)
User Level
(Addressing the information management needs of the user group)
State Web Coordinator level
(Addressing the needs of coordinator of the state)

2.6. INPUT AND OUTPUT

The main inputs, outputs and major functions of the system are as follows

INPUTS:

Head operator enters his or her user id and password.

Operators enter his or her user id and password.
Technicians enter his or her user id and password.
Sub technicians enter his or her user id and password.
User requests the reports.
User requests the search.
Head operator can edits the personal details and so on.

OUTPUTS:

Head operator receives personal details.

Operator receives the personal details.
Technicians receive personal and technical details.
Users receive requested reports.
Displays search result.

- 20 -
2.7. PROCESS MODELS USED WITH JUSTIFICATION
ACCESS CONTROL FOR DATA WHICH REQUIRE USER AUTHENTICATION

The following commands specify access control identifiers and they are
typically used to authorize and authenticate the user (command codes are
shown in parentheses)

USER NAME (USER)

The user identification is that which is required by the server for access to its
file system. This command will normally be the first command transmitted
by the user after the control connections are made (some servers may
require this).

PASSWORD (PASS)

This command must be immediately preceded by the user name command,

and, for some sites, completes the user's identification for access control.
Since password information is quite sensitive, it is desirable in general to
"mask" it or suppress type out.

- 21 -
 Chapter 3

SOFTWARE REQUIREMENT
SPECIFICATION
The software, Site Explorer is designed for management of web sites from a
remote location.

INTRODUCTION

Purpose: The main purpose for preparing this document is to give a general
insight into the analysis and requirements of the existing system or situation
and for determining the operating characteristics of the system.

Scope: This Document plays a vital role in the development life cycle (SDLC)
and it describes the complete requirement of the system. It is meant for use
by the developers and will be the basic during testing phase. Any changes
made to the requirements in the future will have to go through formal
change approval process.

DEVELOPERS RESPONSIBILITIES OVERVIEW:

The developer is responsible for:

Developing the system, which meets the SRS and solving all the
requirements of the system?

- 22 -
 Demonstrating the system and installing the system at client's location
after the acceptance testing is successful.
Submitting the required user manual describing the system interfaces to
work on it and also the documents of the system.
Conducting any user training that might be needed for using the system.
Maintaining the system for a period of one year after installation.

4.1. FUNCTIONAL REQUIREMENTS:

OUTPUT DESIGN

Outputs from computer systems are required primarily to

communicate the results of processing to users. They are also used to
provides a permanent copy of the results for later consultation. The various
types of outputs in general are:
External Outputs, whose destination is outside the organization.
Internal Outputs whose destination is with in organization and they are
the
Users main interface with the computer.
Operational outputs whose use is purely with in the computer
department.
Interface outputs, which involve the user in communicating directly with

OUTPUT DEFINITION
The outputs should be defined in terms of the following points:

Type of the output

Content of the output
Format of the output
Location of the output

- 23 -
 Frequency of the output
Volume of the output
Sequence of the output

It is not always desirable to print or display data as it is held on a

computer. It should be decided as which form of the output is the most
suitable.

For Example
Will decimal points need to be inserted
Should leading zeros be suppressed.

Output Media:
In the next stage it is to be decided that which medium is the most
appropriate for the output. The main considerations when deciding about the
output media are:
The suitability for the device to the particular application.
The need for a hard copy.
The response time required.
The location of the users
The software and hardware available.
Keeping in view the above description the project is to have outputs mainly
coming under the category of internal outputs. The main outputs desired
according to the requirement specification are:
The outputs were needed to be generated as a hot copy and as well as
queries to be viewed on the screen. Keeping in view these outputs, the
format for the output is taken from the outputs, which are currently being
obtained after manual processing. The standard printer is to be used as
output media for hard copies.

INPUT DESIGN

- 24 -
Input design is a part of overall system design. The main objective during
the input design is as given below:

To produce a cost-effective method of input.

To achive the highest possible level of accuracy.
To ensure that the input is acceptable and understood by the user.

INPUT STAGES:
The main input stages can be listed as below:

Data recording
Data transcription
Data conversion
Data verification
Data control
Data transmission
Data validation
Data correction

INPUT TYPES:
It is necessary to determine the various types of inputs. Inputs can be
categorized as follows:
External inputs, which are prime inputs for the system.
Internal inputs, which are user communications with the system.
Operational, which are computer departments communications to the
system?
Interactive, which are inputs entered during a dialogue.

- 25 -
INPUT MEDIA:
At this stage choice has to be made about the input media. To
conclude about the input media consideration has to be given to;
Type of input
Flexibility of format
Speed
Accuracy
Verification methods
Rejection rates
Ease of correction
Storage and handling requirements
Security
Easy to use
Portability

Keeping in view the above description of the input types and input
media, it can be said that most of the inputs are of the form of internal and
interactive. As
Input data is to be the directly keyed in by the user, the keyboard can be
considered to be the most suitable input device.

ERROR AVOIDANCE
At this stage care is to be taken to ensure that input data remains
accurate form the stage at which it is recorded upto the stage in which the
data is accepted by the system. This can be achieved only by means of
careful control each time the data is handled.

- 26 -
ERROR DETECTION
Even though every effort is make to avoid the occurrence of errors,
still a small proportion of errors is always likely to occur, these types of
errors can be discovered by using validations to check the input data.

- 27 -
DATA VALIDATION
Procedures are designed to detect errors in data at a lower level of detail.
Data validations have been included in the system in almost every area where there
is a possibility for the user to commit errors. The system will not accept invalid
data. Whenever an invalid data is keyed in, the system immediately prompts the
user and the user has to again key in the data and the system will accept the data
only if the data is correct. Validations have been included where necessary.
The system is designed to be a user friendly one. In other words the system
has been designed to communicate effectively with the user. The system has been
designed with pop up menus.

USER INTERFACE DESIGN

It is essential to consult the system users and discuss their needs while
designing the user interface:

USER INTERFACE SYSTEMS CAN BE BROADLY CLASIFIED AS:

1. User initiated interface the user is in charge, controlling the progress of the
user/computer dialogue. In the computer-initiated interface, the computer
selects the next stage in the interaction.
2. Computer initiated interfaces

In the computer initiated interfaces the computer guides the progress of the
user/computer dialogue. Information is displayed and the user response of the
computer takes action or displays further information.

USER_INITIATED INTERGFACES
User initiated interfaces fall into tow approximate classes:
1. Command driven interfaces: In this type of interface the user inputs commands
or queries which are interpreted by the computer.
2. Forms oriented interface: The user calls up an image of the form to his/her
screen and fills in the form. The forms oriented interface is chosen because it is
the best choice.

- 28 -
COMPUTER-INITIATED INTERFACES
The following computer initiated interfaces were used:
1. The menu system for the user is presented with a list of alternatives and the
user chooses one; of alternatives.
2. Questions answer type dialog system where the computer asks question and
takes action based on the basis of the users reply.

Right from the start the system is going to be menu driven, the opening
menu displays the available options. Choosing one option gives another popup
menu with more options. In this way every option leads the users to data entry
form where the user can key in the data.

ERROR MESSAGE DESIGN:

The design of error messages is an important part of the user interface
design. As user is bound to commit some errors or other while designing a system
the system should be designed to be helpful by providing the user with information
regarding the error he/she has committed.

This application must be able to produce output at different modules for

different inputs.

4.2. PERFORMANCE REQUIREMENTS

Performance is measured in terms of the output provided by the application.

Requirement specification plays an important part in the analysis of a

system. Only when the requirement specifications are properly given, it is possible
to design a system, which will fit into required environment. It rests largely in the
part of the users of the existing system to give the requirement specifications
because they are the people who finally use the system. This is because the
requirements have to be known during the initial stages so that the system can be
designed according to those requirements. It is very difficult to change the system
once it has been designed and on the other hand designing a system, which does
not cater to the requirements of the user, is of no use.

- 29 -
The requirement specification for any system can be broadly stated as given below:
The system should be able to interface with the existing system
The system should be accurate
The system should be better than the existing system

The existing system is completely dependent on the user to perform all the duties.

- 30 -
 Chapter 4

SELECTED SOFTWARE

5.1. INTRODUCTION TO .NET Framework

The .NET Framework is a new computing platform that simplifies application

development in the highly distributed environment of the Internet. The .NET
Framework is designed to fulfill the following objectives:

To provide a consistent object-oriented programming environment whether

object code is stored and executed locally, executed locally but Internet-
distributed, or executed remotely.
To provide a code-execution environment that minimizes software deployment
and versioning conflicts.
To provide a code-execution environment that guarantees safe execution of
code, including code created by an unknown or semi-trusted third party.
To provide a code-execution environment that eliminates the performance
problems of scripted or interpreted environments.
To make the developer experience consistent across widely varying types of
applications, such as Windows-based applications and Web-based applications.
To build all communication on industry standards to ensure that code based on
the .NET Framework can integrate with any other code.

The .NET Framework has two main components: the common language runtime
and the .NET Framework class library. The common language runtime is the
foundation of the .NET Framework. You can think of the runtime as an agent that
manages code at execution time, providing core services such as memory

- 31 -
management, thread management, and Remoting, while also enforcing strict type
safety and other forms of code accuracy that ensure security and robustness. In
fact, the concept of code management is a fundamental principle of the runtime.
Code that targets the runtime is known as managed code, while code that does not
target the runtime is known as unmanaged code. The class library, the other main
component of the .NET Framework, is a comprehensive, object-oriented collection
of reusable types that you can use to develop applications ranging from traditional
command-line or graphical user interface (GUI) applications to applications based
on the latest innovations provided by ASP.NET, such as Web Forms and XML Web
services.

The .NET Framework can be hosted by unmanaged components that load the
common language runtime into their processes and initiate the execution of
managed code, thereby creating a software environment that can exploit both
managed and unmanaged features. The .NET Framework not only provides several
runtime hosts, but also supports the development of third-party runtime hosts.

For example, ASP.NET hosts the runtime to provide a scalable, server-side

environment for managed code. ASP.NET works directly with the runtime to enable
Web Forms applications and XML Web services, both of which are discussed later in
this topic.

Internet Explorer is an example of an unmanaged application that hosts the

runtime (in the form of a MIME type extension). Using Internet Explorer to host the
runtime enables you to embed managed components or Windows Forms controls in
HTML documents. Hosting the runtime in this way makes managed mobile code
(similar to Microsoft ActiveX controls) possible, but with significant
improvements that only managed code can offer, such as semi-trusted execution
and secure isolated file storage.

- 32 -
 The following illustration shows the relationship of the common language
runtime and the class library to your applications and to the overall system. The
illustration also shows how managed code operates within a larger architecture.

- 33 -
FEATURES OF THE COMMON LANGUAGE RUNTIME

The common language runtime manages memory, thread execution, code

execution, code safety verification, compilation, and other system services. These
features are intrinsic to the managed code that runs on the common language
runtime.

With regards to security, managed components are awarded varying degrees

of trust, depending on a number of factors that include their origin (such as the
Internet, enterprise network, or local computer). This means that a managed
component might or might not be able to perform file-access operations, registry-
access operations, or other sensitive functions, even if it is being used in the same
active application.

The runtime enforces code access security. For example, users can trust that
an executable embedded in a Web page can play an animation on screen or sing a
song, but cannot access their personal data, file system, or network. The security
features of the runtime thus enable legitimate Internet-deployed software to be
exceptionally featuring rich.

The runtime also enforces code robustness by implementing a strict type-

and code-verification infrastructure called the common type system (CTS). The CTS
ensures that all managed code is self-describing. The various Microsoft and third-
party language compilers

Generate managed code that conforms to the CTS. This means that managed
code can consume other managed types and instances, while strictly enforcing type
fidelity and type safety.

In addition, the managed environment of the runtime eliminates many

common software issues. For example, the runtime automatically handles object
layout and manages references to objects, releasing them when they are no longer
being used. This automatic memory management resolves the two most common
application errors, memory leaks and invalid memory references.

- 34 -
 The runtime also accelerates developer productivity. For example,
programmers can write applications in their development language of choice, yet
take full advantage of the runtime, the class library, and components written in
other languages by other developers. Any compiler vendor who chooses to target
the runtime can do so. Language compilers that target the .NET Framework make
the features of the .NET Framework available to existing code written in that
language, greatly easing the migration process for existing applications.

While the runtime is designed for the software of the future, it also supports
software of today and yesterday. Interoperability between managed and
unmanaged code enables developers to continue to use necessary COM components
and DLLs.

The runtime is designed to enhance performance. Although the common

language runtime provides many standard runtime services, managed code is never
interpreted. A feature called just-in-time (JIT) compiling enables all managed code
to run in the native machine language of the system on which it is executing.
Meanwhile, the memory manager removes the possibilities of fragmented memory
and increases memory locality-of-reference to further increase performance.

Finally, the runtime can be hosted by high-performance, server-side

applications, such as Microsoft SQL Server and Internet Information Services
(IIS). This infrastructure enables you to use managed code to write your business
logic, while still enjoying the superior performance of the industry's best enterprise
servers that support runtime hosting.

.NET FRAMEWORK CLASS LIBRARY

The .NET Framework class library is a collection of reusable types that tightly
integrate with the common language runtime. The class library is object oriented,
providing types from which your own managed code can derive functionality. This
not only makes the .NET Framework types easy to use, but also reduces the time

- 35 -
associated with learning new features of the .NET Framework. In addition, third-
party components can integrate seamlessly with classes in the .NET Framework.

For example, the .NET Framework collection classes implement a set of

interfaces that you can use to develop your own collection classes. Your collection
classes will blend seamlessly with the classes in the .NET Framework.

As you would expect from an object-oriented class library, the .NET

Framework types enable you to accomplish a range of common programming tasks,
including tasks such as string management, data collection, database connectivity,
and file access. In addition to these common tasks, the class library includes types
that support a variety of specialized development scenarios. For example, you can
use the .NET Framework to develop the following types of applications and services:

Console applications.
Scripted or hosted applications.
Windows GUI applications (Windows Forms).
ASP.NET applications.
XML Web services.
Windows services.

For example, the Windows Forms classes are a comprehensive set of

reusable types that vastly simplify Windows GUI development. If you write an
ASP.NET Web Form application, you can use the Web Forms classes.

CLIENT APPLICATION DEVELOPMENT

Client applications are the closest to a traditional style of application in

Windows-based programming. These are the types of applications that display
windows or forms on the desktop, enabling a user to perform a task. Client
applications include applications such as word processors and spreadsheets, as well

- 36 -
as custom business applications such as data-entry tools, reporting tools, and so
on. Client applications usually employ windows, menus, buttons, and other GUI
elements, and they likely access local resources such as the file system and
peripherals such as printers.

Another kind of client application is the traditional ActiveX control (now

replaced by the managed Windows Forms control) deployed over the Internet as a
Web page. This application is much like other client applications: it is executed
natively, has access to local resources, and includes graphical elements.

In the past, developers created such applications using C/C++ in conjunction

with the Microsoft Foundation Classes (MFC) or with a rapid application
development (RAD) environment such as Microsoft Visual Basic. The .NET
Framework incorporates aspects of these existing products into a single, consistent
development environment that drastically simplifies the development of client
applications.

The Windows Forms classes contained in the .NET Framework are designed
to be used for GUI development. You can easily create command windows, buttons,
menus, toolbars, and other screen elements with the flexibility necessary to
accommodate shifting business needs.

For example, the .NET Framework provides simple properties to adjust visual
attributes associated with forms. In some cases the underlying operating system
does not support changing these attributes directly, and in these cases the .NET
Framework automatically recreates the forms. This is one of many ways in which
the .NET Framework integrates the developer interface, making coding simpler and
more consistent.

Unlike ActiveX controls, Windows Forms controls have semi-trusted access to

a user's computer. This means that binary or natively executing code can access
some of the resources on the user's system (such as GUI elements and limited file
access) without being able to access or compromise other resources. Because of
code access security, many applications that once needed to be installed on a user's

- 37 -
system can now be safely deployed through the Web. Your applications can
implement the features of a local application while being deployed like a Web page.

ASP.NET

Server Application Development

Server-side applications in the managed world are implemented through

runtime hosts. Unmanaged applications host the common language runtime, which
allows your custom managed code to control the behavior of the server. This model
provides you with all the features of the common language runtime and class
library while gaining the performance and scalability of the host server.

The following illustration shows a basic network schema with managed code
running in different server environments. Servers such as IIS and SQL Server can
perform standard operations while your application logic executes through the
managed code.

SERVER-SIDE MANAGED CODE

ASP.NET is the hosting environment that enables developers to use the .NET
Framework to target Web-based applications. However, ASP.NET is more than just a
runtime host; it is a complete architecture for developing Web sites and Internet-
distributed objects using managed code. Both Web Forms and XML Web services
use IIS and ASP.NET as the publishing mechanism for applications, and both have a
collection of supporting classes in the .NET Framework.

XML Web services, an important evolution in Web-based technology, are

distributed, server-side application components similar to common Web sites.
However, unlike Web-based applications, XML Web services components have no UI
and are not targeted for browsers such as Internet Explorer and Netscape

- 38 -
Navigator. Instead, XML Web services consist of reusable software components
designed to be consumed by other applications, such as traditional client
applications, Web-based applications, or even other XML Web services. As a result,
XML Web services technology is rapidly moving application development and
deployment into the highly distributed environment of the Internet.

If you have used earlier versions of ASP technology, you will immediately
notice the improvements that ASP.NET and Web Forms offers. For example, you can
develop Web Forms pages in any language that supports the .NET Framework. In
addition, your code no longer needs to share the same file with your HTTP text
(although it can continue to do so if you prefer). Web Forms pages execute in
native machine language because, like any other managed application, they take
full advantage of the runtime. In contrast, unmanaged ASP pages are always
scripted and interpreted. ASP.NET pages are faster, more functional, and easier to
develop than unmanaged ASP pages because they interact with the runtime like
any managed application.

The .NET Framework also provides a collection of classes and tools to aid in
development and consumption of XML Web services applications. XML Web services
are built on standards such as SOAP (a remote procedure-call protocol), XML (an
extensible data format), and WSDL ( the Web Services Description Language).
The .NET Framework is built on these standards to promote interoperability with
non-Microsoft solutions.

For example, the Web Services Description Language tool included with
the .NET Framework SDK can query an XML Web service published on the Web,
parse its WSDL description, and produce C# or Visual Basic source code that your
application can use to become a client of the XML Web service. The source code can
create classes derived from classes in the class library that handle all the underlying
communication using SOAP and XML parsing. Although you can use the class library
to consume XML Web services directly, the Web Services Description Language tool
and the other tools contained in the SDK facilitate your development efforts with
the .NET Framework.

- 39 -
 If you develop and publish your own XML Web service, the .NET Framework
provides a set of classes that conform to all the underlying communication
standards, such as SOAP, WSDL, and XML. Using those classes enables you to focus
on the logic of your service, without concerning yourself with the communications
infrastructure required by distributed software development.

Finally, like Web Forms pages in the managed environment, your XML Web service
will run with the speed of native machine language using the scalable
communication of IIS.

ACTIVE SERVER PAGES.NET

ASP.NET is a programming framework built on the common language runtime

that can be used on a server to build powerful Web applications. ASP.NET offers
several important advantages over previous Web development models:

Enhanced Performance. ASP.NET is compiled common language runtime

code running on the server. Unlike its interpreted predecessors, ASP.NET can
take advantage of early binding, just-in-time compilation, native optimization,
and caching services right out of the box. This amounts to dramatically better
performance before you ever write a line of code.
World-Class Tool Support. The ASP.NET framework is complemented by a
rich toolbox and designer in the Visual Studio integrated development
environment. WYSIWYG editing, drag-and-drop server controls, and automatic
deployment are just a few of the features this powerful tool provides.
Power and Flexibility. Because ASP.NET is based on the common language
runtime, the power and flexibility of that entire platform is available to Web
application developers. The .NET Framework class library, Messaging, and Data
Access solutions are all seamlessly accessible from the Web. ASP.NET is also
language-independent, so you can choose the language that best applies to your
application or partition your application across many languages. Further,
common language runtime interoperability guarantees that your existing
investment in COM-based development is preserved when migrating to ASP.NET.

- 40 -
 Simplicity. ASP.NET makes it easy to perform common tasks, from simple
form submission and client authentication to deployment and site configuration.
For example, the ASP.NET page framework allows you to build user interfaces
that cleanly separate application logic from presentation code and to handle
events in a simple, Visual Basic - like forms processing model. Additionally, the
common language runtime simplifies development, with managed code services
such as automatic reference counting and garbage collection.
Manageability. ASP.NET employs a text-based, hierarchical configuration
system, which simplifies applying settings to your server environment and Web
applications. Because configuration information is stored as plain text, new
settings may be applied without the aid of local administration tools. This "zero
local administration" philosophy extends to deploying ASP.NET Framework
applications as well. An ASP.NET Framework application is deployed to a server
simply by copying the necessary files to the server. No server restart is required,
even to deploy or replace running compiled code.
Scalability and Availability. ASP.NET has been designed with scalability in
mind, with features specifically tailored to improve performance in clustered and
multiprocessor environments. Further, processes are closely monitored and
managed by the ASP.NET runtime, so that if one misbehaves (leaks, deadlocks),
a new process can be created in its place, which helps keep your application
constantly available to handle requests.
Customizability and Extensibility. ASP.NET delivers a well-factored
architecture that allows developers to "plug-in" their code at the appropriate
level. In fact, it is possible to extend or replace any subcomponent of the
ASP.NET runtime with your own custom-written component. Implementing
custom authentication or state services has never been easier.
Security. With built in Windows authentication and per-application
configuration, you can be assured that your applications are secure.

LANGUAGE SUPPORT
The Microsoft .NET Platform currently offers built-in support for three
languages: C#, Visual Basic, and JScript.

- 41 -
WHAT IS ASP.NET WEB FORMS?

The ASP.NET Web Forms page framework is a scalable common language

runtime programming model that can be used on the server to dynamically
generate Web pages.

Intended as a logical evolution of ASP (ASP.NET provides syntax compatibility

with existing pages), the ASP.NET Web Forms framework has been specifically
designed to address a number of key deficiencies in the previous model. In
particular, it provides:

The ability to create and use reusable UI controls that can encapsulate common
functionality and thus reduce the amount of code that a page developer has to
write.
The ability for developers to cleanly structure their page logic in an orderly
fashion (not "spaghetti code").
The ability for development tools to provide strong WYSIWYG design support for
pages (existing ASP code is opaque to tools).

ASP.NET Web Forms pages are text files with an .aspx file name extension.
They can be deployed throughout an IIS virtual root directory tree. When a browser
client requests .aspx resources, the ASP.NET runtime parses and compiles the
target file into a .NET Framework class. This class can then be used to dynamically
process incoming requests. (Note that the .aspx file is compiled only the first time it
is accessed; the compiled type instance is then reused across multiple requests).

An ASP.NET page can be created simply by taking an existing HTML file and
changing its file name extension to .aspx (no modification of code is required). For
example, the following sample demonstrates a simple HTML page that collects a
user's name and category preference and then performs a form postback to the
originating page when a button is clicked:

- 42 -
 ASP.NET provides syntax compatibility with existing ASP pages. This includes
support for <% %> code render blocks that can be intermixed with HTML content
within an .aspx file. These code blocks execute in a top-down manner at page
render time.

CODE-BEHIND WEB FORMS

ASP.NET supports two methods of authoring dynamic pages. The first is the
method shown in the preceding samples, where the page code is physically
declared within the originating .aspx file. An alternative approach--known as the
code-behind method--enables the page code to be more cleanly separated from the
HTML content into an entirely separate file.

INTRODUCTION TO ASP.NET SERVER CONTROLS

In addition to (or instead of) using <% %> code blocks to program dynamic
content, ASP.NET page developers can use ASP.NET server controls to program Web
pages. Server controls are declared within an .aspx file using custom tags or
intrinsic HTML tags that contain a runat="server" attributes value. Intrinsic HTML
tags are handled by one of the controls in the System.Web.UI.HtmlControls
namespace. Any tag that doesn't explicitly map to one of the controls is assigned
the type of System.Web.UI.HtmlControls.HtmlGenericControl.

Server controls automatically maintain any client-entered values between

round trips to the server. This control state is not stored on the server (it is instead
stored within an <input type="hidden"> form field that is round-tripped between
requests). Note also that no client-side script is required.

In addition to supporting standard HTML input controls, ASP.NET enables

developers to utilize richer custom controls on their pages. For example, the

- 43 -
following sample demonstrates how the <asp:adrotator> control can be used to
dynamically display rotating ads on a page.

1. ASP.NET Web Forms provide an easy and powerful way to build dynamic Web UI.
2. ASP.NET Web Forms pages can target any browser client (there are no script
library or cookie requirements).
3. ASP.NET Web Forms pages provide syntax compatibility with existing ASP pages.
4. ASP.NET server controls provide an easy way to encapsulate common
functionality.
5. ASP.NET ships with 45 built-in server controls. Developers can also use controls
built by third parties.
6. ASP.NET server controls can automatically project both uplevel and downlevel
HTML.
7. ASP.NET templates provide an easy way to customize the look and feel of list
server controls.
8. ASP.NET validation controls provide an easy way to do declarative client or
server data validation.

C#.NET

ADO.NET OVERVIEW

ADO.NET is an evolution of the ADO data access model that directly

addresses user requirements for developing scalable applications. It was designed
specifically for the web with scalability, statelessness, and XML in mind.

ADO.NET uses some ADO objects, such as the Connection and Command objects,
and also introduces new objects. Key new ADO.NET objects include the DataSet,
DataReader, and DataAdapter.

- 44 -
 The important distinction between this evolved stage of ADO.NET and
previous data architectures is that there exists an object -- the DataSet -- that is
separate and distinct from any data stores. Because of that, the DataSet functions
as a standalone entity. You can think of the DataSet as an always disconnected
recordset that knows nothing about the source or destination of the data it
contains. Inside a DataSet, much like in a database, there are tables, columns,
relationships, constraints, views, and so forth.

A DataAdapter is the object that connects to the database to fill the

DataSet. Then, it connects back to the database to update the data there, based
on operations performed while the DataSet held the data. In the past, data
processing has been primarily connection-based. Now, in an effort to make multi-
tiered apps more efficient, data processing is turning to a message-based approach
that revolves around chunks of information. At the center of this approach is the
DataAdapter, which provides a bridge to retrieve and save data between a
DataSet and its source data store. It accomplishes this by means of requests to
the appropriate SQL commands made against the data store.

The XML-based DataSet object provides a consistent programming model

that works with all models of data storage: flat, relational, and hierarchical. It does
this by having no 'knowledge' of the source of its data, and by representing the
data that it holds as collections and data types. No matter what the source of the
data within the DataSet is, it is manipulated through the same set of standard APIs
exposed through the DataSet and its subordinate objects.

While the DataSet has no knowledge of the source of its data, the managed
provider has detailed and specific information. The role of the managed provider is
to connect, fill, and persist the DataSet to and from data stores. The OLE DB and
SQL Server .NET Data Providers (System.Data.OleDb and System.Data.SqlClient)
that are part of the .Net Framework provide four basic objects: the Command,
Connection, DataReader and DataAdapter. In the remaining sections of this

- 45 -
document, we'll walk through each part of the DataSet and the OLE DB/SQL Server
.NET Data Providers explaining what they are, and how to program against them.

The following sections will introduce you to some objects that have evolved, and
some that are new. These objects are:

Connections. For connection to and managing transactions against a

database.
Commands. For issuing SQL commands against a database.
DataReaders. For reading a forward-only stream of data records from a SQL
Server data source.
DataSets. For storing, Remoting and programming against flat data, XML
data and relational data.
DataAdapters. For pushing data into a DataSet, and reconciling data
against a database.

When dealing with connections to a database, there are two different

options: SQL Server .NET Data Provider (System.Data.SqlClient) and OLE DB .NET
Data Provider (System.Data.OleDb). In these samples we will use the SQL
Server .NET Data Provider. These are written to talk directly to Microsoft SQL
Server. The OLE DB .NET Data Provider is used to talk to any OLE DB provider (as it
uses OLE DB underneath).

Connections:

Connections are used to 'talk to' databases, and are represented by provider-
specific classes such as SqlConnection. Commands travel over connections and
resultsets are returned in the form of streams which can be read by a DataReader
object, or pushed into a DataSet object.

Commands:

- 46 -
 Commands contain the information that is submitted to a database, and are
represented by provider-specific classes such as SqlCommand. A command can be
a stored procedure call, an UPDATE statement, or a statement that returns results.
You can also use input and output parameters, and return values as part of your
command syntax. The example below shows how to issue an INSERT statement
against the Northwind database.

DataReaders:

The DataReader object is somewhat synonymous with a read-only/forward-only

cursor over data. The DataReader API supports flat as well as hierarchical data. A
DataReader object is returned after executing a command against a database. The
format of the returned DataReader object is different from a recordset. For
example, you might use the DataReader to show the results of a search list in a
web page.

- 47 -
DATASETS AND DATA ADAPTERS:

DataSets
The DataSet object is similar to the ADO Recordset object, but more powerful,
and with one other important distinction: the DataSet is always disconnected. The
DataSet object represents a cache of data, with database-like structures such as
tables, columns, relationships, and constraints. However, though a DataSet can
and does behave much like a database, it is important to remember that DataSet
objects do not interact directly with databases, or other source data. This allows the
developer to work with a programming model that is always consistent, regardless
of where the source data resides. Data coming from a database, an XML file, from
code, or user input can all be placed into DataSet objects. Then, as changes are
made to the DataSet they can be tracked and verified before updating the source
data. The GetChanges method of the DataSet object actually creates a second
DatSet that contains only the changes to the data. This DataSet is then used by a
DataAdapter (or other objects) to update the original data source.

The DataSet has many XML characteristics, including the ability to produce and
consume XML data and XML schemas. XML schemas can be used to describe
schemas interchanged via WebServices. In fact, a DataSet with a schema can
actually be compiled for type safety and statement completion.

DATAADAPTERS (OLEDB/SQL)

The DataAdapter object works as a bridge between the DataSet and the
source data. Using the provider-specific SqlDataAdapter (along with its associated
SqlCommand and SqlConnection) can increase overall performance when
working with a Microsoft SQL Server databases. For other OLE DB-supported
databases, you would use the OleDbDataAdapter object and its associated
OleDbCommand and OleDbConnection objects.

- 48 -
 The DataAdapter object uses commands to update the data source after
changes have been made to the DataSet. Using the Fill method of the
DataAdapter calls the SELECT command; using the Update method calls the
INSERT, UPDATE or DELETE command for each changed row. You can explicitly set
these commands in order to control the statements used at runtime to resolve
changes, including the use of stored procedures. For ad-hoc scenarios, a
CommandBuilder object can generate these at run-time based upon a select
statement. However, this run-time generation requires an extra round-trip to the
server in order to gather required metadata, so explicitly providing the INSERT,
UPDATE, and DELETE commands at design time will result in better run-time
performance.

1. ADO.NET is the next evolution of ADO for the .Net Framework.

2. ADO.NET was created with n-Tier, statelessness and XML in the forefront. Two
new objects, the DataSet and DataAdapter, are provided for these scenarios.
3. ADO.NET can be used to get data from a stream, or to store data in a cache
for updates.
4. There is a lot more information about ADO.NET in the documentation.
5. Remember, you can execute a command directly against the database in
order to do inserts, updates, and deletes. You don't need to first put data into a
DataSet in order to insert, update, or delete it.
6. Also, you can use a DataSet to bind to the data, move through the data, and
navigate data relationships

SQL SERVER
A database management, or DBMS, gives the user access to their data and
helps them transform the data into information. Such database management
systems include dBase, paradox, IMS, SQL Server and SQL Server. These systems
allow users to create, update and extract information from their database.
A database is a structured collection of data. Data refers to the
characteristics of people, things and events. SQL Server stores each data item in
its own fields. In SQL Server, the fields relating to a particular person, thing or

- 49 -
event are bundled together to form a single complete unit of data, called a record
(it can also be referred to as raw or an occurrence). Each record is made up of a
number of fields. No two fields in a record can have the same field name.
During an SQL Server Database design project, the analysis of your business
needs identifies all the fields or attributes of interest. If your business needs
change over time, you define any additional fields or change the definition of
existing fields.

SQL SERVER TABLES

SQL Server stores records relating to each other in a table. Different tables
are created for the various groups of information. Related tables are grouped
together to form a database.

PRIMARY KEY
Every table in SQL Server has a field or a combination of fields that uniquely
identifies each record in the table. The Unique identifier is called the Primary Key,
or simply the Key. The primary key provides the means to distinguish one record
from all other in a table. It allows the user and the database system to identify,
locate and refer to one particular record in the database.

RELATIONAL DATABASE
Sometimes all the information of interest to a business operation can be
stored in one table. SQL Server makes it very easy to link the data in multiple
tables. Matching an employee to the department in which they work is one
example. This is what makes SQL Server a relational database management
system, or RDBMS. It stores data in two or more tables and enables you to define
relationships between the table and enables you to define relationships between the
tables.

FOREIGN KEY
When a field is one table matches the primary key of another field is referred
to as a foreign key. A foreign key is a field or a group of fields in one table whose
values match those of the primary key of another table.

- 50 -
REFERENTIAL INTEGRITY
Not only does SQL Server allow you to link multiple tables, it also maintains
consistency between them. Ensuring that the data among related tables is
correctly matched is referred to as maintaining referential integrity.

DATA ABSTRACTION
A major purpose of a database system is to provide users with an abstract
view of the data. This system hides certain details of how the data is stored and
maintained. Data abstraction is divided into three levels.

Physical level: This is the lowest level of abstraction at which one describes how
the data are actually stored.

Conceptual Level: At this level of database abstraction all the attributed and
what data are actually stored is described and entries and relationship among
them.

View level: This is the highest level of abstraction at which one describes only
part of the database.

ADVANTAGES OF RDBMS

Redundancy can be avoided

Inconsistency can be eliminated
Data can be Shared
Standards can be enforced
Security restrictions ca be applied
Integrity can be maintained
Conflicting requirements can be balanced
Data independence can be achieved.

DISADVANTAGES OF DBMS
A significant disadvantage of the DBMS system is cost. In addition to the
cost of purchasing of developing the software, the hardware has to be upgraded to
allow for the extensive programs and the workspace required for their execution

- 51 -
and storage. While centralization reduces duplication, the lack of duplication
requires that the database be adequately backed up so that in case of failure the
data can be recovered.

- 52 -
FEATURES OF SQL SERVER (RDBMS)
SQL SERVER is one of the leading database management systems (DBMS)
because it is the only Database that meets the uncompromising requirements of
todays most demanding information systems. From complex decision support
systems (DSS) to the most rigorous online transaction processing (OLTP)
application, even application that require simultaneous DSS and OLTP access to the
same critical data, SQL Server leads the industry in both performance and
capability

SQL SERVER is a truly portable, distributed, and open DBMS that delivers
unmatched performance, continuous operation and support for every database.
SQL SERVER RDBMS is high performance fault tolerant DBMS which is specially
designed for online transactions processing and for handling large database
application.

SQL SERVER with transactions processing option offers two features which
contribute to very high level of transaction processing throughput, which are

The row level lock manager

ENTERPRISE WIDE DATA SHARING

The unrivaled portability and connectivity of the SQL SERVER DBMS enables
all the systems in the organization to be linked into a singular, integrated computing
resource.

PORTABILITY
SQL SERVER is fully portable to more than 80 distinct hardware and
operating systems platforms, including UNIX, MSDOS, OS/2, Macintosh and dozens
of proprietary platforms. This portability gives complete freedom to choose the
database sever platform that meets the system requirements.

OPEN SYSTEMS
SQL SERVER offers a leading implementation of industry standard SQL.
SQL Servers open architecture integrates SQL SERVER and non SQL SERVER

- 53 -
DBMS with industries most comprehensive collection of tools, application, and third
party software products SQL Servers Open architecture provides transparent
access to data from other relational database and even non-relational database.

DISTRIBUTED DATA SHARING

SQL Servers networking and distributed database capabilities to access data
stored on remote server with the same ease as if the information was stored on a
single local computer. A single SQL statement can access data at multiple sites.
You can store data where system requirements such as performance, security or
availability dictate.

UNMATCHED PERFORMANCE
The most advanced architecture in the industry allows the SQL SERVER
DBMS to deliver unmatched performance.

SOPHISTICATED CONCURRENCY CONTROL

Real World applications demand access to critical data. With most database
Systems application becomes contention bound which performance is limited
not by the CPU power or by disk I/O, but user waiting on one another for data
access . SQL Server employs full, unrestricted row-level locking and contention free
queries to minimize and in many cases entirely eliminates contention wait times.

NO I/O BOTTLENECKS
SQL Servers fast commit groups commit and deferred write technologies
dramatically reduce disk I/O bottlenecks. While some database write whole data
block to disk at commit time, SQL Server commits transactions with at most
sequential log file on disk at commit time, On high throughput systems, one
sequential writes typically group commit multiple transactions. Data read by the
transaction remains as shared memory so that other transactions may access that
data without reading it again from disk. Since fast commits write all data necessary
to the recovery to the log file, modified blocks are written back to the database
independently of the transaction commit, when written from memory to disk.

- 54 -
 Chapter 5

E R DIAGRAMS
The relation upon the system is structure through a conceptual
ER-Diagram, which not only specifics the existential entities but also the
standard relations through which the system exists and the cardinalities
that are necessary for the system state to continue.

The entity Relationship Diagram (ERD) depicts the relationship between

the data objects. The ERD is the notation that is used to conduct the date
modeling activity the attributes of each data object noted is the ERD can
be described resign a data object descriptions.

The set of primary components that are identified by the ERD are

Data object Relationships

Attributes Various types of indicators.

The primary purpose of the ERD is to represent data objects and their
relationships.

6.4. DATA FLOW DIAGRAMS

A data flow diagram is graphical tool used to describe and analyze

movement of data through a system. These are the central tool and the
basis from which the other components are developed. The transformation
of data from input to output, through processed, may be described logically
and independently of physical components associated with the system.

- 55 -
These are known as the logical data flow diagrams. The physical data flow
diagrams show the actual implements and movement of data between
people, departments and workstations. A full description of a system
actually consists of a set of data flow diagrams. Using two familiar notations
Yourdon, Gane and Sarson notation develops the data flow diagrams. Each
component in a DFD is labeled with a descriptive name. Process is further
identified with a number that will be used for identification purpose. The
development of DFDS is done in several levels. Each process in lower level
diagrams can be broken down into a more detailed DFD in the next level.
The lop-level diagram is often called context diagram. It consists a single
process bit, which plays vital role in studying the current system. The
process in the context level diagram is exploded into other process at the
first level DFD.
The idea behind the explosion of a process into more process is that
understanding at one level of detail is exploded into greater detail at the
next level. This is done until further explosion is necessary and an adequate
amount of detail is described for analyst to understand the process.
Larry Constantine first developed the DFD as a way of expressing
system requirements in a graphical from, this lead to the modular design.
A DFD is also known as a bubble Chart has the purpose of clarifying
system requirements and identifying major transformations that will become
programs in system design. So it is the starting point of the design to the
lowest level of detail. A DFD consists of a series of bubbles joined by data
flows in the system.

DFD SYMBOLS:
In the DFD, there are four symbols
1. A square defines a source(originator) or destination of system data

- 56 -
2. An arrow identifies data flow. It is the pipeline through which the
information flows
3. A circle or a bubble represents a process that transforms incoming data
flow into outgoing data flows.
4. An open rectangle is a data store, data at rest or a temporary repository
of data

Process that transforms data flow.

Source or Destination of data

Data flow

Data Store

CONSTRUCTING A DFD:
Several rules of thumb are used in drawing DFDS:

1. Process should be named and numbered for an easy reference. Each

name should be representative of the process.
2. The direction of flow is from top to bottom and from left to right. Data
traditionally flow from source to the destination although they may flow
back to the source. One way to indicate this is to draw long flow line
back to a source. An alternative way is to repeat the source symbol as a
destination. Since it is used more than once in the DFD it is marked with
a short diagonal.
3. When a process is exploded into lower level details, they are numbered.

- 57 -
4. The names of data stores and destinations are written in capital letters.
Process and dataflow names have the first letter of each work capitalized

A DFD typically shows the minimum contents of data store. Each data
store should contain all the data elements that flow in and out.
Questionnaires should contain all the data elements that flow in and
out. Missing interfaces redundancies and like is then accounted for often
through interviews.

SAILENT FEATURES OF DFDS

1. The DFD shows flow of data, not of control loops and decision are
controlled considerations do not appear on a DFD.
2. The DFD does not indicate the time factor involved in any process
whether the dataflow take place daily, weekly, monthly or yearly.
3. The sequence of events is not brought out on the DFD.

TYPES OF DATA FLOW DIAGRAMS

1. Current Physical
2. Current Logical
3. New Logical
4. New Physical

CURRENT PHYSICAL:

In Current Physical DFD proecess label include the name of people or

their positions or the names of computer systems that might provide some
of the overall system-processing label includes an identification of the
technology used to process the data. Similarly data flows and data stores
are often labels with the names of the actual physical media on which data
are stored such as file folders, computer files, business forms or computer
tapes.

- 58 -
CURRENT LOGICAL:
The physical aspects at the system are removed as mush as possible
so that the current system is reduced to its essence to the data and the
processors that transform them regardless of actual physical form.

NEW LOGICAL:
This is exactly like a current logical model if the user were completely
happy with he user were completely happy with the functionality of the
current system but had problems with how it was implemented typically
through the new logical model will differ from current logical model while
having additional functions, absolute function removal and inefficient flows
recognized.

NEW PHYSICAL:
The new physical represents only the physical implementation of the
new system.

RULES GOVERNING THE DFDS

PROCESS

1) No process can have only outputs.

2) No process can have only inputs. If an object has only inputs than it
must be a sink.
3) A process has a verb phrase label.

DATA STORE
1) Data cannot move directly from one data store to another data store, a
process must move data.
2) Data cannot move directly from an outside source to a data store, a
process, which receives, must move data from the source and place the
data into data store
3) A data store has a noun phrase label.

- 59 -
SOURCE OR SINK
The origin and /or destination of data.

1) Data cannot move direly from a source to sink it must be moved by a

process
2) A source and /or sink has a noun phrase land

DATA FLOW

1) A Data Flow has only one direction of flow between symbols. It may flow
in both directions between a process and a data store to show a read
before an update. The later is usually indicated however by two separate
arrows since these happen at different type.
2) A join in DFD means that exactly the same data comes from any of two or
more different processes data store or sink to a common location.
3) A data flow cannot go directly back to the same process it leads. There
must be atleast one other process that handles the data flow produce
some other data flow returns the original data into the beginning process.
4) A Data flow to a data store means update (delete or change).
5) A data Flow from a data store means retrieve or use.

A data flow has a noun phrase label more than one data flow noun phrase
can appear on a single arrow as long as all of the flows on the same arrow
move together as one package.

1st Level DFDs

DFD For New Job Seeker Creation

Job Seeker Registratio

Details
n Details

- 60 -
 Insert New Check for
Job Seeker Verify Data Registration Verify Data
Details

Insert

Job Seeker

Details

DFD For New Job Seeker Creation

Job Provider Registratio

Details
n Details

Insert New Check for

Job Provider Verify Data Registration Verify Data
Details
- 61 -
 Insert

Job Provider

Details

DFD For New Job Search Creation

Registration Search Job

Job Seeker Details
Details
Details
- 62 -
 Check for
Insert New Verify Data Check For
Verify Data Registration
Job Seeker Job
Verify Data

Insert

Job Seeker
Details

2nd Level DFDs

DFD For New Recruitment Creation

- 63 -
 Designation Job Provider
Job Seeker Type Details Details
Details

Check for
Insert New Verify Data Designation
Job Seeker Verify Data
Verify Data

Check for
Job Provider

Check for Job

Seeker Info

Check for Type Check for

Verify Data Verify Data Status Verify Data

Job Provider Job Seeker

Job Seeker Details
Details Status Details

Insert

Job Seeker
Details

- 64 -
 3rd Level DFDS

DFD For New Recruitment Creation

Job Provider Details
Job Seeker Details Designation Type Details

Request for new Validate Prod-Id ()

Job Seeker Generate Emp-Id Validate Desg-Id
() ()

Validate Prod- Validate Job-Seek-Id ()

Commit () Status-ID ()

Database
Updated
Job Provider Status Details Job Seeker status Details
Job Seeker Details

- 65 -
Collaboration Diagrams
Admin Login
Admin Add Collaboration Diagram

DAL : sqlhelper

4 : ExecuteNonQuery()
3 : ExecuteNonQuery()

DataBase 5 : Response To ExecuteNonQuery()

BAL : clsCountry

2 : InsertCountry()

6 : Return Response()

7 : Show Result()
Country

1 : Add Country()

Admin

Admin Add City Collaboration Diagram

- 66 -
 DAL : sqlhelper
4 : ExecuteNonQuery()

DataBase

3 : ExecuteNonQuery()
5 : Response To ExecuteNonQuery()

BAL : clsState

2 : InsertCity()
6 : Return Response()

7 : Show Result()
City
1 : Add City()

Admin

Registration Collaboration Diagram

- 67 -
 DAL : SqlHelper

3 : ExecuteNonQuery()

DataBase

2 : ExecuteNonQuery()

4 : Response to ExecuteNonQuery()

BAL : ClsRegistration

1 : Registration()

6 : Show Result() 5 : Return Response()

Registration

JobRecuriter Update Profile

- 68 -
 5 : Response To ExecuteNonQuery()
DataBase

BAL : clsJ obrecuriterProfile

4 : ExecuteNonQuery() 3 : ExecuteNonQuery()

2 : UpdateProfile()
6 : Return Response()

DAL : sqlhelper

7 : Show Result()
Update J obRecuriter Profile

1 : ModifyProfile()

J obRecuriter

City

- 69 -
 DataBase 5 : Execute_Nonquery() Dal : sqlhelper

4 : InsertCities()

6 : return response() Bal : clsCity

3 : btn_Add()

2 : Invalid Data()
frmCity

1 : lnkCity()

Admin

Country

- 70 -
 DataBase

5 : Execute_Nonquery()
Dal : sqlhelper

4 : InsertCountries()

6 : return response()

Bal : clsCountry

3 : btn_Add()

2 : Invalid Data()
frmCountry

1 : lnkCountry()

Admin

User Registration

- 71 -
 DataBase 5 : Execute_Nonquery()
Dal : sqlhelper

4 : InsertUserDetails()

6 : return response()

Bal : clsUser

3 : btn_submit()

2 : Invalid Data()
frmUser

1 : lnkUser()

Home

Sequence Diagrams:

SEQUENCE DIAGRAMS
Sequence Diagrams Represent the objects participating the interaction
horizontally and time vertically.
Admin Login

- 72 -
 Bal : AdminLogin Dal : SqlHelper DataBase
Admin Login

1 : Login()

2 : CheckUser()

3 : Execute NonQuery()

4 : Exeute NonQuery()

5 : Response to ExecuteNonQuery()

6 : Get Response()

7 : Show Result()

- 73 -
Admin Add Country Sequence Diagram

Admin Country BAL : clsCountry DAL : sqlhelper DataBase

1 : Add Country()

2 : InsertCountry()

3 : ExecuteNonQuery()

4 : ExecuteNonQuery()

5 : Response To ExecuteNonQuery()

6 : Return Response()

7 : Show Result()

- 74 -
Admin Add State Sequence Diagram

Admin State BAL : clsState DAL : sqlhelper DataBase

1 : Add State()

2 : InsertState()

3 : ExecuteNonQuery()

4 : ExecuteNonQuery()

5 : Response To ExecuteNonQuery()

6 : Return Response()

7 : Show Result()

- 75 -
Admin Add City Sequence Diagram

Admin City BAL : clsState DAL : sqlhelper DataBase

1 : Add City()

2 : InsertCity()

3 : ExecuteNonQuery()

4 : ExecuteNonQuery()

5 : Response To ExecuteNonQuery()

6 : Return Response()

7 : Show Result()

Jobseeker Update Profile Sequence Diagram

- 76 -
 J obSeeker Update J obseeker Profile BAL : clsUpdateJ obSeekerProfile DAL : sqlhelper DataBase

1 : ModifyProfile()

2 : UpdateProfile()

3 : ExecuteNonQuery()

4 : ExecuteNonQuery()

5 : Response To ExecuteNonQuery()

6 : Return Response()

7 : Show Result()

JobRecuriter Update Profile Sequence Diagram

J obRecuriter Update J obRecuriter Profile BAL : clsJ obrecuriterProfile DAL : sqlhelper DataBase

1 : ModifyProfile()

2 : UpdateProfile()

3 : ExecuteNonQuery()

4 : ExecuteNonQuery()

5 : Response To ExecuteNonQuery()

6 : Return Response()

7 : Show Result()

Registration Sequence Diagram

- 77 -
 DAL : SqlHelper
Registration BAL : ClsRegistration DataBase

1 : Registration()

2 : ExecuteNonQuery()

3 : ExecuteNonQuery()

4 : Response to ExecuteNonQuery()

5 : Return Response()

6 : Show Result()

Activity Diagrams:

Activity Diagrams:

Login Activity

- 78 -
 [Enter User Name and Password]

Get Details

[Submit]

Validate Data

Rejected No yes Accepted

Jobseeker Registration Activity

- 79 -
Admin Activity Diagram:

- 80 -
Job Recuriter Activity Diagram:

- 81 -
- 82 -
6.5. DATA DICTONARY
After carefully understanding the requirements of the client the the entire
data storage requirements are divided into tables. The below tables are normalized
to avoid any anomalies during the course of data entry.

City Details

Country Details

Experience Detail

Functional Area

Job Openinng Detail

- 83 -
Jobseeker Response to Recruiter

Job Type Detail

Location Master

Qualification

Recruiter Account Details

Recruiter Organization Details

- 84 -
Recruiter Response to Jobseeker

Skill Master

State detail

Student Detail

Admin Login

Jobseeker Background Details

- 85 -
Contact Details

Jobseeker Job Details

Jobseeker Registration

- 86 -
Jobseeker Resume

Jobseeker Technical Details

- 87 -
 Chapter 6

OUTPUT SCREENS

- 88 -
- 89 -
- 90 -
- 91 -
- 92 -
- 93 -
- 94 -
- 95 -
- 96 -
- 97 -
- 98 -
- 99 -
- 100 -
- 101 -
- 102 -
- 103 -
- 104 -
- 105 -
- 106 -
- 107 -
- 108 -
- 109 -
- 110 -
- 111 -
- 112 -
- 113 -
- 114 -
- 115 -
- 116 -
- 117 -
- 118 -
- 119 -
- 120 -
- 121 -
- 122 -
- 123 -
- 124 -
- 125 -
- 126 -
- 127 -
- 128 -
- 129 -
- 130 -
- 131 -
- 132 -
- 133 -
 Chapter 7

SYSTEM TESTING AND

IMPLEMENTATION

8.1. INTRODUCTION
Software testing is a critical element of software quality assurance and
represents the ultimate review of specification, design and coding. In fact,
testing is the one step in the software engineering process that could be
viewed as destructive rather than constructive.

A strategy for software testing integrates software test case design

methods into a well-planned series of steps that result in the successful
construction of software. Testing is the set of activities that can be planned
in advance and conducted systematically. The underlying motivation of
program testing is to affirm software quality with methods that can
economically and effectively apply to both strategic to both large and small-
scale systems.

8.2. STRATEGIC APPROACH TO SOFTWARE TESTING

The software engineering process can be viewed as a spiral. Initially
system engineering defines the role of software and leads to software
requirement analysis where the information domain, functions, behavior,
performance, constraints and validation criteria for software are established.
Moving inward along the spiral, we come to design and finally to coding. To
develop computer software we spiral in along streamlines that decrease the
level of abstraction on each turn.

- 134 -
 A strategy for software testing may also be viewed in the context of
the spiral. Unit testing begins at the vertex of the spiral and concentrates on
each unit of the software as implemented in source code. Testing progress
by moving outward along the spiral to integration testing, where the focus is
on the design and the construction of the software architecture. Talking
another turn on outward on the spiral we encounter validation testing where
requirements established as part of software requirements analysis are
validated against the software that has been constructed. Finally we arrive at
system testing, where the software and other system elements are tested as
a whole.

UNIT TESTING

MODULE TESTING

Component Testing
SUB-SYSTEM TESING

SYSTEM TESTING
Integration Testing

ACCEPTANCE TESTING

User Testing

- 135 -
 Chapter 8

System Security
9.1. Introduction
The protection of computer based resources that includes hardware,
software, data, procedures and people against unauthorized use or natural

Disaster is known as System Security.

System Security can be divided into four related issues:

Security
Integrity
Privacy
Confidentiality

SYSTEM SECURITY refers to the technical innovations and procedures

applied to the hardware and operation systems to protect against deliberate
or accidental damage from a defined threat.

DATA SECURITY is the protection of data from loss, disclosure,

modification and destruction.

SYSTEM INTEGRITY refers to the power functioning of hardware and

programs, appropriate physical security and safety against external threats
such as eavesdropping and wiretapping.

PRIVACY defines the rights of the user or organizations to determine what

information they are willing to share with or accept from others and how the

- 136 -
organization can be protected against unwelcome, unfair or excessive
dissemination of information about it.

Chapter 9

CODING

CITY
using System;
using System.Data;
using System.Configuration;
using System.Web;
using System.Web.Security;
using System.Web.UI;
using System.Web.UI.WebControls;
using System.Web.UI.WebControls.WebParts;
using System.Web.UI.HtmlControls;
using CareerPath.DAL;
using System.Data.SqlClient;
/// <summary>
/// Summary description for CityBL
/// </summary>
public class CityBL:Connection
{
public CityBL()
{
//
// TODO: Add constructor logic here
//
}

public static DataSet ds;

string _Name, _Description;

public string Name
{
get { return _Name; }
set { _Name = value; }
}

public string Description

{
get { return _Description; }

- 137 -
 set { _Description = value; }
}

int _StateId,_CityId;
public int StateId
{
get { return _StateId; }
set { _StateId = value; }
}
public int CityId
{
get { return _CityId; }
set { _CityId = value; }
}
public void InsertCity()
{

SqlParameter[] p = new SqlParameter[3];

p[0] = new SqlParameter("@Name", this._Name);
p[0].DbType =DbType.String;
p[1] = new SqlParameter("@Description", this._Description);
p[1].DbType =DbType.String;
p[2] = new SqlParameter("@StateId", this._StateId);
p[2].DbType = DbType.Int16;
SqlHelper.ExecuteNonQuery(con, CommandType.StoredProcedure,
"Sp_Insert_City", p);

}
public DataSet ShowAllCity()
{
DataSet ds = new DataSet();
ds = SqlHelper.ExecuteDataset(con,
CommandType.StoredProcedure, "Sp_Show_City");
return ds;
}
public DataSet GetCityByState()
{
ds = new DataSet();
SqlParameter[] p = new SqlParameter[1];
p[0] = new SqlParameter("stateid", this.StateId);
p[0].DbType = DbType.Int16;
ds = SqlHelper.ExecuteDataset(con,
CommandType.StoredProcedure, "spGetCityByStateId", p);
return ds;
}
public void DeleteCity()
{
SqlParameter[] p = new SqlParameter[1];
p[0] = new SqlParameter("@CityId", this._CityId);
p[0].DbType = DbType.Int16;
SqlHelper.ExecuteNonQuery(con, CommandType.StoredProcedure,
"Sp_Delete_City", p);

- 138 -
 }
public void UpdateCity()
{
SqlParameter[] p = new SqlParameter[3];
p[0] = new SqlParameter("@CityId", this._CityId);
p[0].DbType = DbType.Int16;
p[1] = new SqlParameter("@CityName", this._Name);
p[1].DbType = DbType.String;
p[2] = new SqlParameter("@Description", this._Description);
p[2].DbType = DbType.String;
SqlHelper.ExecuteNonQuery(con, CommandType.StoredProcedure,
"Sp_Update_City", p);

}
public DataSet ShowCityInfoById()
{
SqlParameter[] p = new SqlParameter[1];
p[0] = new SqlParameter("@CityId", this._CityId);
p[0].DbType = DbType.Int16;
ds = new DataSet();
ds = SqlHelper.ExecuteDataset(con,
CommandType.StoredProcedure, "Sp_ShowCityInfoById", p);
return ds;
}
}

- 139 -
 CONNECTION

using System;
using System.Data;
using System.Configuration;
using System.Web;
using System.Web.Security;
using System.Web.UI;
using System.Web.UI.WebControls;
using System.Web.UI.WebControls.WebParts;
using System.Web.UI.HtmlControls;
using CareerPath.DAL;
/// <summary>
/// Summary description for Connection
/// </summary>
public class Connection
{
public static string con =
ConfigurationManager.ConnectionStrings["CareerPathConnectionString"].C
onnectionString;

- 140 -
 COUNTRY BUSSINESS LAYER
using System;
using System.Data;
using System.Configuration;
using System.Web;
using System.Web.Security;
using System.Web.UI;
using System.Web.UI.WebControls;
using System.Web.UI.WebControls.WebParts;
using System.Web.UI.HtmlControls;
using System.Data.SqlClient;
using CareerPath.DAL;

/// <summary>
/// Summary description for AdminAddingBusinessLayer
/// </summary>

public class CountryBusinessLayer:Connection

{
public static DataSet ds;
public CountryBusinessLayer()
{
//
// TODO: Add constructor logic here
//
}
string _Name, _Description;

public string Name

{
get { return _Name; }
set { _Name = value; }
}

public string Description

{
get { return _Description; }
set { _Description = value; }
}

private int _CountryId;

public int CountryId
{
get { return _CountryId; }
set { _CountryId = value; }
}
public void InsertCountry()

- 141 -
 {
SqlParameter[] p = new SqlParameter[2];
p[0] = new SqlParameter("@Name", this._Name);
p[0].DbType = DbType.String;
p[1] = new SqlParameter("@Description",
this._Description);
p[1].DbType = DbType.String;
SqlHelper.ExecuteNonQuery(con,
CommandType.StoredProcedure, "Sp_Insert_Country", p);

}
public DataSet ShowCountry()
{
ds = new DataSet();
ds = SqlHelper.ExecuteDataset(con,
CommandType.StoredProcedure, "Sp_Show_Country");
return ds;
}
public DataSet GetStateByCountry()
{
SqlParameter[] p = new SqlParameter[1];
p[0] = new SqlParameter("@countryid", this._CountryId);
p[0].DbType = DbType.Int16;
ds = new DataSet();
ds = SqlHelper.ExecuteDataset(con,
CommandType.StoredProcedure, "SpGetStateByCountry", p);
return ds;
}
public DataSet GetCountryIdByName()
{
SqlParameter[] p = new SqlParameter[1];
p[0] = new SqlParameter("@name", this._Name);
p[0].DbType = DbType.Int16;
ds = new DataSet();
ds = SqlHelper.ExecuteDataset(con,
CommandType.StoredProcedure, "SpShowCountryId", p);
return ds;
}
public void DeleteCountry()
{
SqlParameter[] p = new SqlParameter[1];
p[0] = new SqlParameter("@CountryId", this._CountryId);
p[0].DbType = DbType.Int16;
SqlHelper.ExecuteNonQuery(con,
CommandType.StoredProcedure, "Sp_Delete_Country", p);

}
public void UpdateCountry()
{
SqlParameter[] p = new SqlParameter[3];
p[0] = new SqlParameter("@CountryId", this._CountryId);
p[0].DbType = DbType.Int16;

- 142 -
 p[1] = new SqlParameter("@CountryName", this._Name);
p[1].DbType = DbType.String;
p[2] = new SqlParameter("@Description",
this._Description);
p[2].DbType = DbType.String;
SqlHelper.ExecuteNonQuery(con,
CommandType.StoredProcedure, "Sp_Update_Country", p);

}
public DataSet ShowCountryInfoById()
{
SqlParameter[] p = new SqlParameter[1];
p[0] = new SqlParameter("@CountryId", this._CountryId);
p[0].DbType = DbType.Int16;
ds = new DataSet();
ds = SqlHelper.ExecuteDataset(con,
CommandType.StoredProcedure, "Sp_ShowCountryInfoById", p);
return ds;
}
}

- 143 -
 EXPERIENCE
using System;
using System.Data;
using System.Configuration;
using System.Web;
using System.Web.Security;
using System.Web.UI;
using System.Web.UI.WebControls;
using System.Web.UI.WebControls.WebParts;
using System.Web.UI.HtmlControls;
using System.Data.SqlClient;
using CareerPath.DAL;
/// <summary>
/// Summary description for ExperianceBL
/// </summary>
public class ExperianceBL:Connection
{
public static DataSet ds;
public ExperianceBL()
{
//
// TODO: Add constructor logic here
//
}
string _ExpType, _Duration;
public string ExpType
{
get { return _ExpType; }
set { _ExpType = value; }
}
public string Duration
{
get { return _Duration; }
set { _Duration = value; }
}
private int _ExpId;
public int ExpId
{
get { return _ExpId; }
set { _ExpId = value; }
}
public void InsertExperiance()
{
SqlParameter[] p = new SqlParameter[2];
p[0] = new SqlParameter("@ExpType", this._ExpType);
p[0].DbType = DbType.String;
p[1] = new SqlParameter("@Duration", this._Duration);
p[1].DbType = DbType.String;
SqlHelper.ExecuteNonQuery(con, CommandType.StoredProcedure,
"Sp_Insert_Experiance", p);

- 144 -
 }
public DataSet ShowExperience()
{
ds = new DataSet();
ds = SqlHelper.ExecuteDataset(con,
CommandType.StoredProcedure, "Sp_Show_Experience");
return ds;
}
public void DeleteExperience()
{
SqlParameter[] p = new SqlParameter[1];
p[0] = new SqlParameter("@ExpId", this._ExpId);
p[0].DbType = DbType.Int16;
SqlHelper.ExecuteNonQuery(con, CommandType.StoredProcedure,
"Sp_Delete_Experience", p);

}
public void UpdateExperience()
{
SqlParameter[] p = new SqlParameter[3];
p[0] = new SqlParameter("@ExpId", this._ExpId);
p[0].DbType = DbType.Int16;
p[1] = new SqlParameter("@ExpType", this._ExpType);
p[1].DbType = DbType.String;
p[2] = new SqlParameter("@Duration", this._Duration);
p[2].DbType = DbType.String;
SqlHelper.ExecuteNonQuery(con, CommandType.StoredProcedure,
"Sp_Update_Experience", p);

}
public DataSet ShowExperienceInfoById()
{
SqlParameter[] p = new SqlParameter[1];
p[0] = new SqlParameter("@ExpId", this._ExpId);
p[0].DbType = DbType.Int16;
ds = new DataSet();
ds = SqlHelper.ExecuteDataset(con,
CommandType.StoredProcedure, "Sp_ShowExperienceInfoById", p);
return ds;
}
}

- 145 -
 FUNCTIONAL AREA
using System;
using System.Data;
using System.Configuration;
using System.Web;
using System.Web.Security;
using System.Web.UI;
using System.Web.UI.WebControls;
using System.Web.UI.WebControls.WebParts;
using System.Web.UI.HtmlControls;
using System.Data.SqlClient;
using CareerPath.DAL;
/// <summary>
/// Summary description for FunctionalAreaBL
/// </summary>
public class FunctionalAreaBL:Connection
{
public static DataSet ds;
public FunctionalAreaBL()
{
//
// TODO: Add constructor logic here
//
}
string _FunctionalArea, _Description;
public string FunctionalArea
{
get { return _FunctionalArea; }
set { _FunctionalArea = value; }
}
public string Description
{
get { return _Description; }
set { _Description = value; }
}
private int _FunctionalId;
public int FunctionalId
{
get { return _FunctionalId; }
set { _FunctionalId = value; }
}
public void InsertQualification()
{
SqlParameter[] p = new SqlParameter[2];
p[0] = new SqlParameter("@FunctionalArea",
this._FunctionalArea);
p[0].DbType = DbType.String;
p[1] = new SqlParameter("@Description", this._Description);
p[1].DbType = DbType.String;

- 146 -
 SqlHelper.ExecuteNonQuery(con, CommandType.StoredProcedure,
"Sp_Insert_FunctionalArea", p);
}
public DataSet ShowFunctionalArea()
{
ds = new DataSet();
ds = SqlHelper.ExecuteDataset(con,
CommandType.StoredProcedure, "Sp_Show_FunctionalArea");
return ds;
}
public void DeleteFunctionalArea()
{
SqlParameter[] p = new SqlParameter[1];
p[0] = new SqlParameter("@FunctionalId", this._FunctionalId);
p[0].DbType = DbType.Int16;
SqlHelper.ExecuteNonQuery(con, CommandType.StoredProcedure,
"Sp_Delete_FunctionalArea", p);

}
public void UpdateFunctionalArea()
{
SqlParameter[] p = new SqlParameter[3];
p[0] = new SqlParameter("@FunctionalId", this._FunctionalId);
p[0].DbType = DbType.Int16;
p[1] = new SqlParameter("@FunctionalArea",
this._FunctionalArea);
p[1].DbType = DbType.String;
p[2] = new SqlParameter("@Description", this._Description);
p[2].DbType = DbType.String;
SqlHelper.ExecuteNonQuery(con, CommandType.StoredProcedure,
"Sp_Update_FunctionalArea", p);

}
public DataSet ShowFunctionInfoById()
{
SqlParameter[] p = new SqlParameter[1];
p[0] = new SqlParameter("@FunctionalId", this._FunctionalId);
p[0].DbType = DbType.Int16;
ds = new DataSet();
ds = SqlHelper.ExecuteDataset(con,
CommandType.StoredProcedure, "Sp_ShowFunctionInfoById", p);
return ds;
}
}

- 147 -
 JOB SEEKER REGISTRATION

using System;
using System.Data;
using System.Configuration;
using System.Web;
using System.Web.Security;
using System.Web.UI;
using System.Web.UI.WebControls;
using System.Web.UI.WebControls.WebParts;
using System.Web.UI.HtmlControls;
using System.Data.SqlClient;
using CareerPath.DAL;
/// <summary>
/// Summary description for JobSeekerRegistrationBL
/// </summary>
public class JobSeekerRegistrationBL:Connection
{
public static DataSet ds;
public JobSeekerRegistrationBL()
{
//
// TODO: Add constructor logic here
//
}
//Registration Details
private string _JobSeekerId, _Password, _HintQuestion, _Answer;
public string JobSeekerId
{
get { return _JobSeekerId; }
set { _JobSeekerId = value; }
}
public string Password
{
get { return _Password; }
set { _Password = value; }
}
public string HintQuestion
{
get { return _HintQuestion; }
set { _HintQuestion = value; }
}
public string Answer
{
get { return _Answer; }
set { _Answer = value; }
}

- 148 -
 //Contact Information

private string
_FirstName,_LastName,_Address,_City,_State,_PinCode,_Country,_EmailID,
_Phone1,_Phone2,_FaxNo;
public string FaxNo
{
get { return _FaxNo; }
set { _FaxNo = value; }
}
public string FirstName
{
get { return _FirstName; }
set { _FirstName = value; }
}
public string LastName
{
get { return _LastName; }
set { _LastName = value; }
}

public string Address

{
get { return _Address; }
set { _Address = value; }
}
public string City
{
get { return _City; }
set { _City = value; }
}
public string State
{
get { return _State; }
set { _State = value; }
}
public string PinCode
{
get { return _PinCode; }
set { _PinCode = value; }
}
public string Country
{
get { return _Country; }
set { _Country = value; }
}
public string EmailID
{
get { return _EmailID; }
set { _EmailID = value; }
}

- 149 -
 public string Phone1
{
get { return _Phone1; }
set { _Phone1 = value; }
}
public string Phone2
{
get { return _Phone2; }
set { _Phone2 = value; }
}
private DateTime _DOB;
public DateTime DOB
{
get { return _DOB; }
set { _DOB = value; }
}
private DateTime _FromDate, _ToDate;
public DateTime FromDate
{
get { return _FromDate; }
set { _FromDate = value; }
}
public DateTime ToDate
{
get { return _ToDate; }
set { _ToDate = value; }
}
//BackGround Information

private string
_HighestDegree,_Specialisation,_University,_TechnicalExp,_WorkField;
private int _PassingYear;
private float _Percentage;
public string HighestDegree
{
get { return _HighestDegree; }
set { _HighestDegree = value; }
}
public string Specialisation
{
get { return _Specialisation; }
set { _Specialisation = value; }
}
public int PassingYear
{
get { return _PassingYear; }
set { _PassingYear = value; }
}
public float Percentage
{
get { return _Percentage; }
set { _Percentage = value; }

- 150 -
 }
public string University
{
get { return _University; }
set { _University = value; }
}

public string TechnicalExp

{
get { return _TechnicalExp; }
set { _TechnicalExp = value; }
}
public string WorkField
{
get { return _WorkField; }
set { _WorkField = value; }
}

//JobDetail Information

private string
_JobTitle,_Location1,_State1,_Country1,_Location2,_State2,_Country2,_W
illRelocate,_WillTelecommute,_WillTravel;
public string JobTitle
{
get { return _JobTitle; }
set { _JobTitle = value; }
}
public string Location1
{
get { return _Location1; }
set { _Location1 = value; }
}
public string State1
{
get { return _State1; }
set { _State1 = value; }
}
public string Country1
{
get { return _Country1; }
set { _Country1 = value; }
}
public string Location2
{
get { return _Location2; }
set { _Location2 = value; }
}
public string State2
{
get { return _State2; }

- 151 -
 set { _State2 = value; }
}
public string Country2
{
get { return _Country2; }
set { _Country2 = value; }
}
public string WillRelocate
{
get { return _WillRelocate; }
set { _WillRelocate = value; }
}
public string WillTelecommute
{
get { return _WillTelecommute; }
set { _WillTelecommute = value; }
}
public string WillTravel
{
get { return _WillTravel; }
set { _WillTravel = value; }
}

private string _FullTimeSalary, _HourlySalary, _TypeOfEmployment1,

_TypeOfEmployment2, _TypeOfEmployment3;
public string FullTimeSalary
{
get { return _FullTimeSalary; }
set { _FullTimeSalary = value; }
}
public string HourlySalary
{
get { return _HourlySalary; }
set { _HourlySalary = value; }
}
public string TypeOfEmployment1
{
get { return _TypeOfEmployment1; }
set { _TypeOfEmployment1 = value; }
}
public string TypeOfEmployment2
{
get { return _TypeOfEmployment2; }
set { _TypeOfEmployment2 = value; }
}
public string TypeOfEmployment3
{
get { return _TypeOfEmployment3; }
set { _TypeOfEmployment3 = value; }
}
private DateTime _Date;

- 152 -
 public DateTime Date
{
get { return _Date; }
set { _Date = value; }
}
public void InsertJobSeekerLoginInfo()
{
SqlParameter[] p = new SqlParameter[5];
p[0] = new SqlParameter("@JobSeekerId", this._JobSeekerId);
p[0].DbType = DbType.String;
p[1] = new SqlParameter("@Password", this._Password);
p[1].DbType = DbType.String;
p[2] = new SqlParameter("@HintQuestion", this._HintQuestion);
p[2].DbType = DbType.String;
p[3] = new SqlParameter("@Answer", this._Answer);
p[3].DbType = DbType.String;
p[4] = new SqlParameter("@Date", this._Date);
p[4].DbType = DbType.Date;
SqlHelper.ExecuteNonQuery(con, CommandType.StoredProcedure,
"Sp_InsertJobSeekerRegestration", p);

//Contact Information

public void InsertJobSeekerContactInfo()

{
SqlParameter[] p = new SqlParameter[13];
p[0] = new SqlParameter("@JobSeekerId", this._JobSeekerId);
p[0].DbType = DbType.String;
p[1] = new SqlParameter("@FirstName", this._FirstName);
p[1].DbType = DbType.String;
p[2] = new SqlParameter("@LastName", this._LastName);
p[2].DbType = DbType.String;
p[3] = new SqlParameter("@DOB", this._DOB);
p[3].DbType = DbType.Date;
p[4] = new SqlParameter("@Address", this._Address);
p[4].DbType = DbType.String;
p[5] = new SqlParameter("@City", this._City);
p[5].DbType = DbType.String;
p[6] = new SqlParameter("@State", this._State);
p[6].DbType = DbType.String;
p[7] = new SqlParameter("@PinCode", this._PinCode);
p[7].DbType = DbType.String;
p[8] = new SqlParameter("@Country", this._Country);
p[8].DbType = DbType.String;
p[9] = new SqlParameter("@EmailID", this._EmailID);
p[9].DbType = DbType.String;
p[10] = new SqlParameter("@Phone1", this._Phone1);
p[10].DbType = DbType.String;
p[11] = new SqlParameter("@Phone2", this._Phone2);
p[11].DbType = DbType.String;

- 153 -
 p[12] = new SqlParameter("@Fax", this._FaxNo);
p[12].DbType = DbType.String;
SqlHelper.ExecuteNonQuery(con, CommandType.StoredProcedure,
"Sp_InsertJobSeekerContactDetails", p);

//BackGround Information

public void InsertJobSeekerBackgroundDetails()

{
SqlParameter[] p = new SqlParameter[9];
p[0] = new SqlParameter("@JobSeekerId", this._JobSeekerId);
p[0].DbType = DbType.String;
p[1] = new SqlParameter("@HighestDegree",
this._HighestDegree);
p[1].DbType = DbType.String;
p[2] = new SqlParameter("@Specialisation",
this._Specialisation);
p[2].DbType = DbType.String;
p[3] = new SqlParameter("@PassingYear", this._PassingYear);
p[3].DbType = DbType.Int16;
p[4] = new SqlParameter("@Percentage", this._Percentage);
p[4].DbType = DbType.Double;
p[5] = new SqlParameter("@University", this._University);
p[5].DbType = DbType.String;
p[6] = new SqlParameter("@Country", this._Country);
p[6].DbType = DbType.String;
p[7] = new SqlParameter("@TechnicalExp", this._TechnicalExp);
p[7].DbType = DbType.String;
p[8] = new SqlParameter("@WorkField", this._WorkField);
p[8].DbType = DbType.String;
SqlHelper.ExecuteNonQuery(con, CommandType.StoredProcedure,
"Sp_InsertJobSeekerBackgroundDetails", p);

}
//JobDetails Information

public void InsertJobSeekerJobDetails()

{
SqlParameter[] p = new SqlParameter[16];
p[0] = new SqlParameter("@JobSeekerId", this._JobSeekerId);
p[0].DbType = DbType.String;
p[1] = new SqlParameter("@JobTitle", this._JobTitle);
p[1].DbType = DbType.String;
p[2] = new SqlParameter("@Location1", this._Location1);
p[2].DbType = DbType.String;
p[3] = new SqlParameter("@State1", this._State1);
p[3].DbType = DbType.String;
p[4] = new SqlParameter("@Country1", this._Country1);
p[4].DbType = DbType.String;
p[5] = new SqlParameter("@Location2", this._Location2);

- 154 -
 p[5].DbType = DbType.String;
p[6] = new SqlParameter("@State2", this._State2);
p[6].DbType = DbType.String;
p[7] = new SqlParameter("@Country2", this._Country2);
p[7].DbType = DbType.String;
p[8] = new SqlParameter("@WillRelocate", this._WillRelocate);
p[8].DbType = DbType.String;
p[9] = new SqlParameter("@WillTelecommute",
this._WillTelecommute);
p[9].DbType = DbType.String;
p[10] = new SqlParameter("@WillTravel", this._WillTravel);
p[10].DbType = DbType.String;
p[11] = new SqlParameter("@FullTimeSalary",
this._FullTimeSalary);
p[11].DbType = DbType.String;
p[12] = new SqlParameter("@HourlySalary", this._HourlySalary);
p[12].DbType = DbType.String;
p[13] = new SqlParameter("@TypeOfEmployment1",
this._TypeOfEmployment1);
p[13].DbType = DbType.String;
p[14] = new SqlParameter("@TypeOfEmployment2",
this._TypeOfEmployment2);
p[14].DbType = DbType.String;
p[15] = new SqlParameter("@TypeOfEmployment3",
this._TypeOfEmployment3);
p[15].DbType = DbType.String;
SqlHelper.ExecuteNonQuery(con, CommandType.StoredProcedure,
"Sp_InsertJobSeekerJobDetails", p);

}
//Technical skills Details
private string _Skill1, _Skill2, _Skill3, _Skill4;
public string Skill1
{
get { return _Skill1; }
set { _Skill1 = value; }
}
public string Skill2
{
get { return _Skill2; }
set { _Skill2 = value; }
}
public string Skill3
{
get { return _Skill3; }
set { _Skill3 = value; }
}
public string Skill4
{
get { return _Skill4; }
set { _Skill4 = value; }
}

- 155 -
 private int _Skill1Year, _Skill1Lastused, _Skill2Year,
_Skill2Lastused ,_Skill3Year, _Skill3Lastused, _Skill4Year,
_Skill4Lastused;
public int Skill1Year
{
get { return _Skill1Year; }
set { _Skill1Year = value; }
}
public int Skill2Year
{
get { return _Skill2Year; }
set { _Skill2Year = value; }
}
public int Skill3Year
{
get { return _Skill3Year; }
set { _Skill3Year = value; }
}
public int Skill4Year
{
get { return _Skill4Year; }
set { _Skill4Year = value; }
}
public int Skill1Lastused
{
get { return _Skill1Lastused; }
set { _Skill1Lastused = value; }
}
public int Skill2Lastused
{
get { return _Skill2Lastused; }
set { _Skill2Lastused = value; }
}
public int Skill3Lastused
{
get { return _Skill3Lastused; }
set { _Skill3Lastused = value; }
}
public int Skill4Lastused
{
get { return _Skill4Lastused; }
set { _Skill4Lastused = value; }
}
public void InsertJobSeekertechnicalSkills()
{
SqlParameter[] p = new SqlParameter[13];
p[0] = new SqlParameter("@JobSeekerId", this._JobSeekerId);
p[0].DbType = DbType.String;
p[1] = new SqlParameter("@Skill1", this._Skill1);
p[1].DbType = DbType.String;
p[2] = new SqlParameter("@Skill1Year", this._Skill1Year);
p[2].DbType = DbType.Int16;

- 156 -
 p[3] = new SqlParameter("@Skill1Lastused",
this._Skill1Lastused);
p[3].DbType = DbType.Int16;
p[4] = new SqlParameter("@Skill2", this._Skill2);
p[4].DbType = DbType.String;
p[5] = new SqlParameter("@Skill2Year", this._Skill2Year);
p[5].DbType = DbType.Int16;
p[6] = new SqlParameter("@Skill2Lastused",
this._Skill2Lastused);
p[6].DbType = DbType.Int16;
p[7] = new SqlParameter("@Skill3", this._Skill3);
p[7].DbType = DbType.String;
p[8] = new SqlParameter("@Skill3Year", this._Skill3Year);
p[8].DbType = DbType.Int16;
p[9] = new SqlParameter("@Skill3Lastused",
this._Skill3Lastused);
p[9].DbType = DbType.Int16;
p[10] = new SqlParameter("@Skill4", this._Skill4);
p[10].DbType = DbType.String;
p[11] = new SqlParameter("@Skill4Year", this._Skill4Year);
p[11].DbType = DbType.Int16;
p[12] = new SqlParameter("@Skill4Lastused",
this._Skill4Lastused);
p[12].DbType = DbType.Int16;
SqlHelper.ExecuteNonQuery(con, CommandType.StoredProcedure,
"Sp_InsertJobSeekertechnicalSkills", p);

//ResumeDetails Information
private string _Resume,_ResumePath;
public string Resume
{
get { return _Resume; }
set { _Resume = value; }
}
public string ResumePath
{
get { return _ResumePath; }
set { _ResumePath = value; }
}
private DateTime _ResumeUpLoadDate,_LastModifiedDate;
public DateTime ResumeUpLoadDate
{
get { return _ResumeUpLoadDate; }
set { _ResumeUpLoadDate = value; }
}
public DateTime LastModifiedDate
{
get { return _LastModifiedDate; }
set { _LastModifiedDate = value; }
}

- 157 -
 public void InsertJobSeekerResume()
{
SqlParameter[] p = new SqlParameter[5];
p[0] = new SqlParameter("@JobSeekerId", this._JobSeekerId);
p[0].DbType = DbType.String;
p[1] = new SqlParameter("@Resume", this._Resume);
p[1].SqlDbType = SqlDbType.NText;
p[2] = new SqlParameter("@ResumeUpLoadDate",
this._ResumeUpLoadDate);
p[2].DbType = DbType.Date;
p[3] = new SqlParameter("@LastModifiedDate",
this._LastModifiedDate);
p[3].DbType = DbType.Date;
p[4] = new SqlParameter("@ResumePath", this._ResumePath);
p[4].DbType = DbType.String;
SqlHelper.ExecuteNonQuery(con, CommandType.StoredProcedure,
"Sp_InsertJobSeekerResume", p);
}
public bool CheckUserAvailability()
{
int count;
SqlParameter[] p = new SqlParameter[1];
p[0] = new SqlParameter("@JobSeekerId", this._JobSeekerId);
p[0].DbType = DbType.String;
count = int.Parse(SqlHelper.ExecuteScalar(con,
CommandType.StoredProcedure, "SpCheckUserAvailability",
p).ToString());
if (count > 0)
return true;
else

return false;

}
public DataSet ShowJobSeekerDetail()
{
SqlParameter[] p = new SqlParameter[1];
p[0] = new SqlParameter("@JobseekerId", this.JobSeekerId);
p[0].DbType = DbType.String;
ds = new DataSet();
ds = SqlHelper.ExecuteDataset(con,
CommandType.StoredProcedure, "Sp_ShowJobSeekerContactDetail", p);
return ds;
}
public bool ForgotPasswordCheck()
{
int count;
SqlParameter[] p = new SqlParameter[3];
p[0] = new SqlParameter("@JobSeekerId", this._JobSeekerId);
p[0].DbType = DbType.String;
p[1] = new SqlParameter("@HintQuestion", this._HintQuestion);

- 158 -
 p[1].DbType = DbType.String;
p[2] = new SqlParameter("@Answer", this._Answer);
p[2].DbType = DbType.String;
count = int.Parse(SqlHelper.ExecuteScalar(con,
CommandType.StoredProcedure, "Sp_ForgotPasswordCheck", p).ToString());
if (count > 0)
return true;
else

return false;
}
public DataSet ShowForgotPassword()
{
SqlParameter[] p = new SqlParameter[3];
p[0] = new SqlParameter("@JobSeekerId", this._JobSeekerId);
p[0].DbType = DbType.String;
p[1] = new SqlParameter("@HintQuestion", this._HintQuestion);
p[1].DbType = DbType.String;
p[2] = new SqlParameter("@Answer", this._Answer);
p[2].DbType = DbType.String;
ds = new DataSet();
ds = SqlHelper.ExecuteDataset(con,
CommandType.StoredProcedure, "SpShow_ForgotPassword", p);
return ds;
}
public DataSet ShowLoginInfo()
{
SqlParameter[] p = new SqlParameter[1];
p[0] = new SqlParameter("@JobSeekerId", this._JobSeekerId);
p[0].DbType = DbType.String;
ds = new DataSet();
ds = SqlHelper.ExecuteDataset(con,
CommandType.StoredProcedure, "Sp_Show_LoginInfo", p);
return ds;
}
public DataSet PasswordCheck()
{
SqlParameter[] p = new SqlParameter[1];
p[0] = new SqlParameter("@JobSeekerId", this._JobSeekerId);
p[0].DbType = DbType.String;
ds = new DataSet();
ds = SqlHelper.ExecuteDataset(con,
CommandType.StoredProcedure, "Sp_PasswordCheck", p);
return ds;
}
public void ModifyJobseekerRegestration()
{
SqlParameter[] p = new SqlParameter[4];
p[0] = new SqlParameter("@JobSeekerId", this._JobSeekerId);
p[0].DbType = DbType.String;
p[1] = new SqlParameter("@Password", this._Password);
p[1].DbType = DbType.String;

- 159 -
 p[2] = new SqlParameter("@HintQuestion", this._HintQuestion);
p[2].DbType = DbType.String;
p[3] = new SqlParameter("@Answer", this._Answer);
p[3].DbType = DbType.String;
SqlHelper.ExecuteNonQuery(con, CommandType.StoredProcedure,
"Sp_Modify_JobseekerRegestration", p);
}
public DataSet ShowContactDetail()
{
SqlParameter[] p = new SqlParameter[1];
p[0] = new SqlParameter("@JobSeekerId", this.JobSeekerId);
p[0].DbType = DbType.String;
ds = new DataSet();
ds = SqlHelper.ExecuteDataset(con,
CommandType.StoredProcedure, "SpShow_ContactDetail", p);
return ds;
}
public void ModifyJobseekerContactDetails()
{
SqlParameter[] p = new SqlParameter[13];
p[0] = new SqlParameter("@JobSeekerId", this._JobSeekerId);
p[0].DbType = DbType.String;
p[1] = new SqlParameter("@FirstName", this._FirstName);
p[1].DbType = DbType.String;
p[2] = new SqlParameter("@LastName", this._LastName);
p[2].DbType = DbType.String;
p[3] = new SqlParameter("@DOB", this._DOB);
p[3].DbType = DbType.Date;
p[4] = new SqlParameter("@Address", this._Address);
p[4].DbType = DbType.String;
p[5] = new SqlParameter("@City", this._City);
p[5].DbType = DbType.String;
p[6] = new SqlParameter("@State", this._State);
p[6].DbType = DbType.String;
p[7] = new SqlParameter("@PinCode", this._PinCode);
p[7].DbType = DbType.String;
p[8] = new SqlParameter("@Country", this._Country);
p[8].DbType = DbType.String;
p[9] = new SqlParameter("@EmailID", this._EmailID);
p[9].DbType = DbType.String;
p[10] = new SqlParameter("@Phone1", this._Phone1);
p[10].DbType = DbType.String;
p[11] = new SqlParameter("@Phone2", this._Phone2);
p[11].DbType = DbType.String;
p[12] = new SqlParameter("@FaxNo", this._FaxNo);
p[12].DbType = DbType.String;
SqlHelper.ExecuteNonQuery(con, CommandType.StoredProcedure,
"Sp_Modify_JobseekerContactDetails", p);

- 160 -
 //BackGround Information

public DataSet ShowJobseekerBackgroundDetail()

{
SqlParameter[] p = new SqlParameter[1];
p[0] = new SqlParameter("@JobSeekerId", this.JobSeekerId);
p[0].DbType = DbType.String;
ds = new DataSet();
ds = SqlHelper.ExecuteDataset(con,
CommandType.StoredProcedure, "Sp_Show_JobseekerBackgroundDetail", p);
return ds;
}

public void ModifyJobseekerBackgroundDetails()

{
SqlParameter[] p = new SqlParameter[9];
p[0] = new SqlParameter("@JobSeekerId", this._JobSeekerId);
p[0].DbType = DbType.String;
p[1] = new SqlParameter("@HighestDegree",
this._HighestDegree);
p[1].DbType = DbType.String;
p[2] = new SqlParameter("@Specialisation",
this._Specialisation);
p[2].DbType = DbType.String;
p[3] = new SqlParameter("@PassingYear", this._PassingYear);
p[3].DbType = DbType.Int16;
p[4] = new SqlParameter("@Percentage", this._Percentage);
p[4].DbType = DbType.Double;
p[5] = new SqlParameter("@University", this._University);
p[5].DbType = DbType.String;
p[6] = new SqlParameter("@Country", this._Country);
p[6].DbType = DbType.String;
p[7] = new SqlParameter("@TechnicalExp", this._TechnicalExp);
p[7].DbType = DbType.String;
p[8] = new SqlParameter("@WorkField", this._WorkField);
p[8].DbType = DbType.String;
SqlHelper.ExecuteNonQuery(con, CommandType.StoredProcedure,
"Sp_Modify_JobseekerBackgroundDetails", p);

//JobDetails Information

public DataSet ShowJobseekerJobDetail()

{
SqlParameter[] p = new SqlParameter[1];
p[0] = new SqlParameter("@JobSeekerId", this.JobSeekerId);
p[0].DbType = DbType.String;
ds = new DataSet();
ds = SqlHelper.ExecuteDataset(con,
CommandType.StoredProcedure, "Sp_Show_JobseekerJobDetail", p);

- 161 -
 return ds;
}

public void ModifyJobseekerJobDetails()

{
SqlParameter[] p = new SqlParameter[16];
p[0] = new SqlParameter("@JobSeekerId", this._JobSeekerId);
p[0].DbType = DbType.String;
p[1] = new SqlParameter("@JobTitle", this._JobTitle);
p[1].DbType = DbType.String;
p[2] = new SqlParameter("@Location1", this._Location1);
p[2].DbType = DbType.String;
p[3] = new SqlParameter("@State1", this._State1);
p[3].DbType = DbType.String;
p[4] = new SqlParameter("@Country1", this._Country1);
p[4].DbType = DbType.String;
p[5] = new SqlParameter("@Location2", this._Location2);
p[5].DbType = DbType.String;
p[6] = new SqlParameter("@State2", this._State2);
p[6].DbType = DbType.String;
p[7] = new SqlParameter("@Country2", this._Country2);
p[7].DbType = DbType.String;
p[8] = new SqlParameter("@WillRelocate", this._WillRelocate);
p[8].DbType = DbType.String;
p[9] = new SqlParameter("@WillTelecommute",
this._WillTelecommute);
p[9].DbType = DbType.String;
p[10] = new SqlParameter("@WillTravel", this._WillTravel);
p[10].DbType = DbType.String;
p[11] = new SqlParameter("@FullTimeSalary",
this._FullTimeSalary);
p[11].DbType = DbType.String;
p[12] = new SqlParameter("@HourlySalary", this._HourlySalary);
p[12].DbType = DbType.String;
p[13] = new SqlParameter("@TypeOfEmployment1",
this._TypeOfEmployment1);
p[13].DbType = DbType.String;
p[14] = new SqlParameter("@TypeOfEmployment2",
this._TypeOfEmployment2);
p[14].DbType = DbType.String;
p[15] = new SqlParameter("@TypeOfEmployment3",
this._TypeOfEmployment3);
p[15].DbType = DbType.String;
SqlHelper.ExecuteNonQuery(con, CommandType.StoredProcedure,
"Sp_Modify_JobseekerJobDetails", p);

//TechnicalSkillDetail
public DataSet ShowJobSeekerTechnicalSkillDetail()
{

- 162 -
 SqlParameter[] p = new SqlParameter[1];
p[0] = new SqlParameter("@JobSeekerId", this.JobSeekerId);
p[0].DbType = DbType.String;
ds = new DataSet();
ds = SqlHelper.ExecuteDataset(con,
CommandType.StoredProcedure, "Sp_Show_JobSeekerTechnicalSkillDetail",
p);
return ds;
}
public void ModifyJobseekerTechnicalSkills()
{
SqlParameter[] p = new SqlParameter[13];
p[0] = new SqlParameter("@JobSeekerId", this._JobSeekerId);
p[0].DbType = DbType.String;
p[1] = new SqlParameter("@Skill1", this._Skill1);
p[1].DbType = DbType.String;
p[2] = new SqlParameter("@Skill1Year", this._Skill1Year);
p[2].DbType = DbType.Int16;
p[3] = new SqlParameter("@Skill1Lastused",
this._Skill1Lastused);
p[3].DbType = DbType.Int16;
p[4] = new SqlParameter("@Skill2", this._Skill2);
p[4].DbType = DbType.String;
p[5] = new SqlParameter("@Skill2Year", this._Skill2Year);
p[5].DbType = DbType.Int16;
p[6] = new SqlParameter("@Skill2Lastused",
this._Skill2Lastused);
p[6].DbType = DbType.Int16;
p[7] = new SqlParameter("@Skill3", this._Skill3);
p[7].DbType = DbType.String;
p[8] = new SqlParameter("@Skill3Year", this._Skill3Year);
p[8].DbType = DbType.Int16;
p[9] = new SqlParameter("@Skill3Lastused",
this._Skill3Lastused);
p[9].DbType = DbType.Int16;
p[10] = new SqlParameter("@Skill4", this._Skill4);
p[10].DbType = DbType.String;
p[11] = new SqlParameter("@Skill4Year", this._Skill4Year);
p[11].DbType = DbType.Int16;
p[12] = new SqlParameter("@Skill4Lastused",
this._Skill4Lastused);
p[12].DbType = DbType.Int16;
SqlHelper.ExecuteNonQuery(con, CommandType.StoredProcedure,
"Sp_Modify_JobseekerTechnicalSkills", p);

//JobSeeker resume Detail

public DataSet ShowJobSeekerResumeDetail()
{
SqlParameter[] p = new SqlParameter[1];
p[0] = new SqlParameter("@JobSeekerId", this.JobSeekerId);

- 163 -
 p[0].DbType = DbType.String;
ds = new DataSet();
ds = SqlHelper.ExecuteDataset(con,
CommandType.StoredProcedure, "Sp_Show_JobSeekerResumeDetail", p);
return ds;
}
public void ModifyJobseekerResumeDetail()
{
SqlParameter[] p = new SqlParameter[4];
p[0] = new SqlParameter("@JobSeekerId", this._JobSeekerId);
p[0].DbType = DbType.String;
p[1] = new SqlParameter("@Resume", this._Resume);
p[1].SqlDbType = SqlDbType.NText;
p[2] = new SqlParameter("@LastModifiedDate",
this._LastModifiedDate);
p[2].DbType = DbType.Date;
p[3] = new SqlParameter("@ResumePath", this._ResumePath);
p[3].DbType = DbType.String;
SqlHelper.ExecuteNonQuery(con, CommandType.StoredProcedure,
"Sp_Modify_JobseekerResumeDetail", p);
}
public bool CheckJobSeekerLoginInfo()
{
int count;
SqlParameter[] p = new SqlParameter[2];
p[0] = new SqlParameter("@JobSeekerId", this._JobSeekerId);
p[0].DbType = DbType.String;
p[1] = new SqlParameter("@Password", this._Password);
p[1].DbType = DbType.String;
count = int.Parse(SqlHelper.ExecuteScalar(con,
CommandType.StoredProcedure, "Sp_CheckJobSeekerLoginInfo",
p).ToString());
if (count > 0)
return true;
else

return false;
}

//View JobSeeker

public DataSet ShowAllRegisteredJobSeekerByDate()

{
SqlParameter[] p = new SqlParameter[2];
p[0] = new SqlParameter("@FromDate", this._FromDate);
p[0].DbType = DbType.Date;
p[1] = new SqlParameter("@ToDate", this._ToDate);
p[1].DbType = DbType.Date;
ds = new DataSet();
ds = SqlHelper.ExecuteDataset(con,
CommandType.StoredProcedure, "Sp_Show_AllRegisteredJobSeeker", p);
return ds;

- 164 -
 }
public void DeleteRegisterJobseekerInfo()
{
SqlParameter[] p = new SqlParameter[1];
p[0] = new SqlParameter("@JobSeekerId", this._JobSeekerId);
p[0].DbType = DbType.String;
SqlHelper.ExecuteNonQuery(con, CommandType.StoredProcedure,
"Sp_Delete_RegisterJobseekerInfo", p);
}
}

- 165 -
 JOB SEEKER RESPONSE TO JOB
using System;
using System.Data;
using System.Configuration;
using System.Web;
using System.Web.Security;
using System.Web.UI;
using System.Web.UI.WebControls;
using System.Web.UI.WebControls.WebParts;
using System.Web.UI.HtmlControls;
using System.Data.SqlClient;
using CareerPath.DAL;
/// <summary>
/// Summary description for JobSeekerResponseToJobBL
/// </summary>
public class JobSeekerResponseToJobBL:Connection
{
public static DataSet ds;
public JobSeekerResponseToJobBL()
{
//
// TODO: Add constructor logic here
//
}
private string _JobSeekerId,_RecruiterName,_JobID;
private DateTime _DateOfResponse;
public string JobSeekerId
{
get { return _JobSeekerId; }
set { _JobSeekerId = value; }
}
public string RecruiterName
{
get { return _RecruiterName; }
set { _RecruiterName = value; }
}
public string JobID
{
get { return _JobID; }
set { _JobID = value; }
}
public DateTime DateOfResponse
{
get { return _DateOfResponse; }
set { _DateOfResponse = value; }
}

//JobSeeker Response

- 166 -
 public void InsertJobSeekerResponseToRecruiter()
{
SqlParameter[] p = new SqlParameter[4];
p[0] = new SqlParameter("@JobSeekerId", this._JobSeekerId);
p[0].DbType = DbType.String;
p[1] = new SqlParameter("@RecruiterName",
this._RecruiterName);
p[1].DbType = DbType.String;
p[2] = new SqlParameter("@JobID", this._JobID);
p[2].DbType = DbType.String;
p[3] = new SqlParameter("@DateOfResponse",
this._DateOfResponse);
p[3].DbType = DbType.Date;
SqlHelper.ExecuteNonQuery(con, CommandType.StoredProcedure,
"Sp_InsertJobSeekerResponseToRecruiter", p);

}
private string _UserName;
public string UserName
{
get { return _UserName; }
set { _UserName = value; }
}
public DataSet ShowJobSeekerFullDetail()
{
SqlParameter[] p = new SqlParameter[1];
p[0] = new SqlParameter("@JobSeekerId", this._JobSeekerId);
p[0].DbType = DbType.String;
ds = new DataSet();
ds = SqlHelper.ExecuteDataset(con,
CommandType.StoredProcedure, "Sp_ShowJobSeekerFullDetail", p);
return ds;
}
public DataSet ShowAllJobSeeker()
{
ds = new DataSet();
ds = SqlHelper.ExecuteDataset(con,
CommandType.StoredProcedure, "Sp_ShowAllJobSeeker");
return ds;
}
public DataSet ShowAllJobsByRecruiter()
{
SqlParameter[] p = new SqlParameter[1];
p[0] = new SqlParameter("@UserName", this._UserName);
p[0].DbType = DbType.String;
ds = new DataSet();
ds = SqlHelper.ExecuteDataset(con,
CommandType.StoredProcedure, "Sp_Show_AllJobsByRecruiter", p);
return ds;
}
public DataSet ShowJobSeekerResponseDetail()
{

- 167 -
 ds = new DataSet();
ds = SqlHelper.ExecuteDataset(con,
CommandType.StoredProcedure, "Sp_ShowJobSeekerResponseDetail1");
return ds;
}

public DataSet ShowJobInfoByJobId()

{
SqlParameter[] p = new SqlParameter[1];
p[0] = new SqlParameter("@JobId", this._JobID);
p[0].DbType = DbType.String;
ds = new DataSet();
ds = SqlHelper.ExecuteDataset(con,
CommandType.StoredProcedure, "Sp_ShowJobInfoByJobId", p);
return ds;
}
public bool ShowJobApplyStatus()
{
int count;
SqlParameter[] p = new SqlParameter[2];
p[0] = new SqlParameter("@JobSeekerId", this._JobSeekerId);
p[0].DbType = DbType.String;
p[1] = new SqlParameter("@JobID", this._JobID);
p[1].DbType = DbType.String;
count = int.Parse(SqlHelper.ExecuteScalar(con,
CommandType.StoredProcedure, "Sp_ShowJobAllpyStatus", p).ToString());
if (count > 0)
return true;
else

return false;
}
}

- 168 -
 JOB TYPE
using System;
using System.Data;
using System.Configuration;
using System.Web;
using System.Web.Security;
using System.Web.UI;
using System.Web.UI.WebControls;
using System.Web.UI.WebControls.WebParts;
using System.Web.UI.HtmlControls;
using System.Data.SqlClient;
using CareerPath.DAL;
/// <summary>
/// Summary description for JobTypeBL
/// </summary>
public class JobTypeBL:Connection
{
public static DataSet ds;
public JobTypeBL()
{
//
// TODO: Add constructor logic here
//
}
string _JobType, _Description;
public string JobType
{
get { return _JobType; }
set { _JobType = value; }
}
public string Description
{
get { return _Description; }
set { _Description = value; }
}
private int _JobId;
public int JobId
{
get { return _JobId; }
set { _JobId = value; }
}
public void InsertJobType()
{
SqlParameter[] p = new SqlParameter[2];
p[0] = new SqlParameter("@JobType", this._JobType);
p[0].DbType = DbType.String;
p[1] = new SqlParameter("@Description", this._Description);
p[1].DbType = DbType.String;
SqlHelper.ExecuteNonQuery(con, CommandType.StoredProcedure,
"Sp_Insert_JobType", p);

- 169 -
 }
public DataSet ShowJobType()
{
ds = new DataSet();
ds = SqlHelper.ExecuteDataset(con,
CommandType.StoredProcedure, "Sp_Show_JobType");
return ds;
}
public void DeleteJobType()
{
SqlParameter[] p = new SqlParameter[1];
p[0] = new SqlParameter("@JobId", this._JobId);
p[0].DbType = DbType.Int16;
SqlHelper.ExecuteNonQuery(con, CommandType.StoredProcedure,
"Sp_Delete_JobType", p);

}
public void UpdateJobType()
{
SqlParameter[] p = new SqlParameter[3];
p[0] = new SqlParameter("@JobId", this._JobId);
p[0].DbType = DbType.Int16;
p[1] = new SqlParameter("@JobType", this._JobType);
p[1].DbType = DbType.String;
p[2] = new SqlParameter("@Description", this._Description);
p[2].DbType = DbType.String;
SqlHelper.ExecuteNonQuery(con, CommandType.StoredProcedure,
"Sp_Update_JobType", p);

}
public DataSet ShowJobTypeInfoById()
{
SqlParameter[] p = new SqlParameter[1];
p[0] = new SqlParameter("@JobId", this._JobId);
p[0].DbType = DbType.Int16;
ds = new DataSet();
ds = SqlHelper.ExecuteDataset(con,
CommandType.StoredProcedure, "Sp_ShowJobTypeInfoById", p);
return ds;
}
}

- 170 -
 QUALIFICATION
using System;
using System.Data;
using System.Configuration;
using System.Web;
using System.Web.Security;
using System.Web.UI;
using System.Web.UI.WebControls;
using System.Web.UI.WebControls.WebParts;
using System.Web.UI.HtmlControls;
using CareerPath.DAL;
using System.Data.SqlClient;
/// <summary>
/// Summary description for QualificationBL
/// </summary>
public class QualificationBL:Connection
{
public static DataSet ds;
public QualificationBL()
{
//
// TODO: Add constructor logic here
//
}
string _Qualification, _Description;
private int _QualificationLevel,_QualificationId;
public string Qualification
{
get { return _Qualification; }
set { _Qualification = value; }
}
public string Description
{
get { return _Description; }
set { _Description = value; }
}
public int QualificationLevel
{
get { return _QualificationLevel; }
set { _QualificationLevel = value; }
}
public int QualificationId
{
get { return _QualificationId; }
set { _QualificationId = value; }
}
public void InsertQualification()
{
SqlParameter[] p = new SqlParameter[3];
p[0] = new SqlParameter("@Qualification",
this._Qualification);

- 171 -
 p[0].DbType = DbType.String;
p[1] = new SqlParameter("@Description", this._Description);
p[1].DbType = DbType.String;
p[2] = new SqlParameter("@QualificationLevel",
this._QualificationLevel);
p[2].DbType = DbType.Int16;
SqlHelper.ExecuteNonQuery(con, CommandType.StoredProcedure,
"Sp_Insert_Qualification", p);
}
public DataSet ShowQualification()
{
ds = new DataSet();
ds = SqlHelper.ExecuteDataset(con,
CommandType.StoredProcedure, "Sp_Show_Qualification");
return ds;
}
public void DeleteQualification()
{
SqlParameter[] p = new SqlParameter[1];
p[0] = new SqlParameter("@QualificationId",
this._QualificationId);
p[0].DbType = DbType.Int16;
SqlHelper.ExecuteNonQuery(con, CommandType.StoredProcedure,
"Sp_Delete_Qualification", p);

}
public void UpdateQualification()
{
SqlParameter[] p = new SqlParameter[3];
p[0] = new SqlParameter("@QualificationId",
this._QualificationId);
p[0].DbType = DbType.Int16;
p[1] = new SqlParameter("@Qualification",
this._Qualification);
p[1].DbType = DbType.String;
p[2] = new SqlParameter("@Description", this._Description);
p[2].DbType = DbType.String;
SqlHelper.ExecuteNonQuery(con, CommandType.StoredProcedure,
"Sp_Update_Qualification", p);

}
public DataSet ShowQualificationInfoById()
{
SqlParameter[] p = new SqlParameter[1];
p[0] = new SqlParameter("@QualificationId",
this._QualificationId);
p[0].DbType = DbType.Int16;
ds = new DataSet();
ds = SqlHelper.ExecuteDataset(con,
CommandType.StoredProcedure, "Sp_ShowQualificationInfoById", p);
return ds;
}}

- 172 -
Recruiter Job Opening And Other Detail
using System;
using System.Data;
using System.Configuration;
using System.Web;
using System.Web.Security;
using System.Web.UI;
using System.Web.UI.WebControls;
using System.Web.UI.WebControls.WebParts;
using System.Web.UI.HtmlControls;
using System.Data.SqlClient;
using CareerPath.DAL;
/// <summary>
/// Summary description for RecruiterJobOpeningAndOtherDetail
/// </summary>
public class RecruiterJobOpeningAndOtherDetail:Connection
{
public static DataSet ds;
public RecruiterJobOpeningAndOtherDetail()
{
//
// TODO: Add constructor logic here
//
}
private string _UserName, _JobID, _JobCategory, _SkillsRequired,
_Role, _MinimumQualification, _JobLocation, _JobDescription;
private int _MaximumAge, _ExperienceYears;
private decimal _ExpectedSalary;
private DateTime _JobOpeningDate, _JobClosingDate;
public string UserName
{
get { return _UserName; }
set { _UserName = value; }
}
public string JobID
{
get { return _JobID; }
set { _JobID = value; }
}
public string JobCategory
{
get { return _JobCategory; }
set { _JobCategory = value; }
}
public string SkillsRequired
{
get { return _SkillsRequired; }
set { _SkillsRequired = value; }
}

- 173 -
public string Role
{
get { return _Role; }
set { _Role = value; }
}
public string MinimumQualification
{ get { return _MinimumQualification; }
set { _MinimumQualification = value; }
}
public string JobLocation
{
get { return _JobLocation; }
set { _JobLocation = value; }
}
public string JobDescription
{
get { return _JobDescription; }
set { _JobDescription = value; }
}

public int MaximumAge

{
get { return _MaximumAge; }
set { _MaximumAge = value; }
}
public int ExperienceYears
{
get { return _ExperienceYears; }
set { _ExperienceYears = value; }
}
public decimal ExpectedSalary
{
get { return _ExpectedSalary; }
set { _ExpectedSalary = value; }
}
public DateTime JobOpeningDate
{
get { return _JobOpeningDate; }
set { _JobOpeningDate = value; }
}
public DateTime JobClosingDate
{
get { return _JobClosingDate; }
set { _JobClosingDate = value; }
}
public void InsertJobOpeningDetails()
{
SqlParameter[] p = new SqlParameter[13];
p[0] = new SqlParameter("@UserName", this._UserName);
p[0].DbType = DbType.String;
p[1] = new SqlParameter("@JobID", this._JobID);
p[1].DbType = DbType.String;

- 174 -
 p[2] = new SqlParameter("@JobCategory", this._JobCategory);
p[2].DbType = DbType.String;
p[3] = new SqlParameter("@SkillsRequired",
this._SkillsRequired);
p[3].DbType = DbType.String;
p[4] = new SqlParameter("@Role", this._Role);
p[4].DbType = DbType.String;
p[5] = new SqlParameter("@MinimumQualification",
this._MinimumQualification);
p[5].DbType = DbType.String;
p[6] = new SqlParameter("@JobLocation", this._JobLocation);
p[6].DbType = DbType.String;
p[7] = new SqlParameter("@JobDescription",
this._JobDescription);
p[7].DbType = DbType.String;
p[8] = new SqlParameter("@MaximumAge", this._MaximumAge);
p[8].DbType = DbType.Int16;
p[9] = new SqlParameter("@ExperienceYears",
this._ExperienceYears);
p[9].DbType = DbType.Int16;
p[10] = new SqlParameter("@ExpectedSalary",
this._ExpectedSalary);
p[10].DbType = DbType.Decimal;
p[11] = new SqlParameter("@JobOpeningDate",
this._JobOpeningDate);
p[11].DbType = DbType.String;
p[12] = new SqlParameter("@JobClosingDate",
this._JobClosingDate);
p[12].DbType = DbType.String;
SqlHelper.ExecuteNonQuery(con, CommandType.StoredProcedure,
"Sp_InsertJobOpeningDetails", p);

}
public DataSet ShowAllJobs()
{
ds = new DataSet();
ds = SqlHelper.ExecuteDataset(con,
CommandType.StoredProcedure, "Sp_Show_AllJobs");
return ds;
}
private string _OrgName;
public string OrgName
{
get { return _OrgName; }
set { _OrgName = value; }
}
//Job Search
public DataSet ShowFullJobDetailByJobId()
{
SqlParameter[] p = new SqlParameter[2];
p[0] = new SqlParameter("@OrgName", this._OrgName);
p[0].DbType = DbType.String;

- 175 -
 p[1] = new SqlParameter("@JobID", this._JobID);
p[1].DbType = DbType.String;
ds = new DataSet();
ds = SqlHelper.ExecuteDataset(con,
CommandType.StoredProcedure, "Sp_Show_FullJobDetailByJobId",p);
return ds;
}
//Job By Category
public DataSet ShowAllJobByCategory()
{
SqlParameter[] p = new SqlParameter[1];
p[0] = new SqlParameter("@JobCategory", this._JobCategory);
p[0].DbType = DbType.String;
ds = new DataSet();
ds = SqlHelper.ExecuteDataset(con,
CommandType.StoredProcedure, "Sp_Show_AllJobByCategory", p);
return ds;
}

//Job By Location
public DataSet ShowAllJobByLocation()
{
SqlParameter[] p = new SqlParameter[1];
p[0] = new SqlParameter("@JobLocation", this._JobLocation);
p[0].DbType = DbType.String;
ds = new DataSet();
ds = SqlHelper.ExecuteDataset(con,
CommandType.StoredProcedure, "Sp_Show_AllJobByLocation", p);
return ds;
}
//Job By Role
public DataSet ShowAllJobByRole()
{
SqlParameter[] p = new SqlParameter[1];
p[0] = new SqlParameter("@Role", this._Role);
p[0].DbType = DbType.String;
ds = new DataSet();
ds = SqlHelper.ExecuteDataset(con,
CommandType.StoredProcedure, "Sp_Show_AllJobByRole", p);
return ds;
}
//Job By AnyCondition
public DataSet ShowAllJobByAnyCondition()
{
SqlParameter[] p = new SqlParameter[4];
p[0] = new SqlParameter("@JobCategory", this._JobCategory);
p[0].DbType = DbType.String;
p[1] = new SqlParameter("@JobLocation", this._JobLocation);
p[1].DbType = DbType.String;
p[2] = new SqlParameter("@Role", this._Role);
p[2].DbType = DbType.String;

- 176 -
 p[3] = new SqlParameter("@ExpectedSalary",
this._ExpectedSalary);
p[3].DbType = DbType.Decimal;
ds = new DataSet();
ds = SqlHelper.ExecuteDataset(con,
CommandType.StoredProcedure, "Sp_Show_AllJobByAnyCondition", p);
return ds;
}
public DataSet CompareDate()
{
SqlParameter[] p = new SqlParameter[1];
p[0] = new SqlParameter("@JobId", this._JobID);
p[0].DbType = DbType.String;
ds = new DataSet();
ds = SqlHelper.ExecuteDataset(con,
CommandType.StoredProcedure, "Sp_CompareDate", p);
return ds;
}

//JobSeeker By Role
public DataSet ShowAllJobSeekerByRole()
{
SqlParameter[] p = new SqlParameter[1];
p[0] = new SqlParameter("@Role", this._Role);
p[0].DbType = DbType.String;
ds = new DataSet();
ds = SqlHelper.ExecuteDataset(con,
CommandType.StoredProcedure, "Sp_Show_AllJobSeekerByRole", p);
return ds;
}
private string _JobSeekerId;
public string JobSeekerId
{
get { return _JobSeekerId; }
set { _JobSeekerId = value; }
}
public DataSet ShowAllSkills()
{
SqlParameter[] p = new SqlParameter[1];
p[0] = new SqlParameter("@JobSeekerId", this._JobSeekerId);
p[0].DbType = DbType.String;
ds = new DataSet();
ds = SqlHelper.ExecuteDataset(con,
CommandType.StoredProcedure, "Sp_Show_AllSkills", p);
return ds;
}

public DataSet ShowAllLocation()

{
SqlParameter[] p = new SqlParameter[1];
p[0] = new SqlParameter("@JobSeekerId", this._JobSeekerId);
p[0].DbType = DbType.String;

- 177 -
 ds = new DataSet();
ds = SqlHelper.ExecuteDataset(con,
CommandType.StoredProcedure, "Sp_Show_AllLocation", p);
return ds;
}
//Jobseeker By Location
public DataSet ShowAllJobSeekerByLocation()
{
SqlParameter[] p = new SqlParameter[1];
p[0] = new SqlParameter("@Location", this._JobLocation);
p[0].DbType = DbType.String;
ds = new DataSet();
ds = SqlHelper.ExecuteDataset(con,
CommandType.StoredProcedure, "Sp_Show_AllJobSeekerByLocation", p);
return ds;
}
private string _Qualification,_Salary;
public string Qualification
{
get { return _Qualification; }
set { _Qualification = value; }
}
public string Salary
{
get { return _Salary; }
set { _Salary = value; }
}
//Jobseeker By Qualification
public DataSet ShowAllJobSeekerByQualification()
{
SqlParameter[] p = new SqlParameter[1];
p[0] = new SqlParameter("@Qualification",
this._Qualification);
p[0].DbType = DbType.String;
ds = new DataSet();
ds = SqlHelper.ExecuteDataset(con,
CommandType.StoredProcedure, "Sp_Show_AllJobSeekerByQualification",
p);
return ds;
}
//Jobseeker By Salary
public DataSet ShowAllJobSeekerBySalary()
{
SqlParameter[] p = new SqlParameter[1];
p[0] = new SqlParameter("@ExpectedSalary", this._Salary);
p[0].DbType = DbType.String;
ds = new DataSet();
ds = SqlHelper.ExecuteDataset(con,
CommandType.StoredProcedure, "Sp_Show_AllJobSeekerBySalary", p);
return ds;
}

- 178 -
 //JobSeeker By AnyCondition
public DataSet ShowAllJobSeekerByAnyCondition()
{
SqlParameter[] p = new SqlParameter[4];
p[0] = new SqlParameter("@Role", this._Role);
p[0].DbType = DbType.String;
p[1] = new SqlParameter("@Qualification",
this._Qualification);
p[1].DbType = DbType.String;
p[2] = new SqlParameter("@Location", this._JobLocation);
p[2].DbType = DbType.String;
p[3] = new SqlParameter("@ExpectedSalary", this._Salary);
p[3].DbType = DbType.String;
ds = new DataSet();
ds = SqlHelper.ExecuteDataset(con,
CommandType.StoredProcedure, "Sp_Show_AllJobSeekerByAnyCondition", p);
return ds;
}
}

- 179 -
 RECRUITER REGESTRATION
using System;
using System.Data;
using System.Configuration;
using System.Web;
using System.Web.Security;
using System.Web.UI;
using System.Web.UI.WebControls;
using System.Web.UI.WebControls.WebParts;
using System.Web.UI.HtmlControls;
using System.Data.SqlClient;
using CareerPath.DAL;
/// <summary>
/// Summary description for RecruiterRegistrationBL
/// </summary>
public class RecruiterRegistrationBL:Connection
{
public static DataSet ds;
public RecruiterRegistrationBL()
{
//
// TODO: Add constructor logic here
//
}
private string _UserName, _Password, _HintQuestion, _Answer;
public string UserName
{
get { return _UserName; }
set { _UserName = value; }
}
public string Password
{
get { return _Password; }
set { _Password = value; }
}
public string HintQuestion
{
get { return _HintQuestion; }
set { _HintQuestion = value; }
}
public string Answer
{
get { return _Answer; }
set { _Answer = value; }
}
private DateTime _Date;
public DateTime Date
{

- 180 -
 get { return _Date; }
set { _Date = value; }
}
private DateTime _FromDate, _ToDate;
public DateTime FromDate
{
get { return _FromDate; }
set { _FromDate = value; }
}
public DateTime ToDate
{
get { return _ToDate; }
set { _ToDate = value; }
}
public void InsertRecruiterAccountDetail()
{
SqlParameter[] p = new SqlParameter[5];
p[0] = new SqlParameter("@UserName", this._UserName);
p[0].DbType = DbType.String;
p[1] = new SqlParameter("@Password", this._Password);
p[1].DbType = DbType.String;
p[2] = new SqlParameter("@HintQuestion", this._HintQuestion);
p[2].DbType = DbType.String;
p[3] = new SqlParameter("@Answer", this._Answer);
p[3].DbType = DbType.String;
p[4] = new SqlParameter("@Date", this._Date);
p[4].DbType = DbType.Date;
SqlHelper.ExecuteNonQuery(con, CommandType.StoredProcedure,
"Sp_InsertRecruiterAccountDetail", p);

}
//Recruiter Organization Detail
private string _OrganisationName ,_BusinessSector,_Certificate1
,_Certificate2 ,_Certificate3 ,_Website ,_EmailID1 ,_EmailID2
,_Address ,_OrganisationEnvironment ,_TermsAndCondition ,_Others;
public string OrganisationName
{
get { return _OrganisationName; }
set { _OrganisationName = value; }
}
public string BusinessSector
{
get { return _BusinessSector; }
set { _BusinessSector = value; }
}
public string Certificate1
{
get { return _Certificate1; }
set { _Certificate1 = value; }
}
public string Certificate2
{

- 181 -
 get { return _Certificate2; }
set { _Certificate2 = value; }
}
public string Certificate3
{
get { return _Certificate3; }
set { _Certificate3 = value; }
}
public string Website
{
get { return _Website; }
set { _Website = value; }
}
public string EmailID1
{
get { return _EmailID1; }
set { _EmailID1 = value; }
}
public string EmailID2
{
get { return _EmailID2; }
set { _EmailID2 = value; }
}
public string Address
{ get { return _Address; }
set { _Address = value; }
}
public string OrganisationEnvironment
{
get { return _OrganisationEnvironment; }
set { _OrganisationEnvironment = value; }
}
public string TermsAndCondition
{ get { return _TermsAndCondition; }
set { _TermsAndCondition = value; }
}
public string Others
{
get { return _Others; }
set { _Others = value; }
}

private int _SizeOfOrganisation;

public int SizeOfOrganisation
{
get { return _SizeOfOrganisation; }
set { _SizeOfOrganisation = value; }
}
public void InsertRecruiterOrganisationDetails()
{
SqlParameter[] p = new SqlParameter[14];

- 182 -
 p[0] = new SqlParameter("@UserName", this._UserName);
p[0].DbType = DbType.String;
p[1] = new SqlParameter("@OrganisationName",
this._OrganisationName);
p[1].DbType = DbType.String;
p[2] = new SqlParameter("@BusinessSector",
this._BusinessSector);
p[2].DbType = DbType.String;
p[3] = new SqlParameter("@Certificate1", this._Certificate1);
p[3].DbType = DbType.String;
p[4] = new SqlParameter("@Certificate2", this._Certificate2);
p[4].DbType = DbType.String;
p[5] = new SqlParameter("@Certificate3", this._Certificate3);
p[5].DbType = DbType.String;
p[6] = new SqlParameter("@Website", this._Website);
p[6].DbType = DbType.String;
p[7] = new SqlParameter("@EmailID1", this._EmailID1);
p[7].DbType = DbType.String;
p[8] = new SqlParameter("@EmailID2", this._EmailID2);
p[8].DbType = DbType.String;
p[9] = new SqlParameter("@Address", this._Address);
p[9].DbType = DbType.String;
p[10] = new SqlParameter("@OrganisationEnvironment",
this._OrganisationEnvironment);
p[10].DbType = DbType.String;
p[11] = new SqlParameter("@TermsAndCondition",
this._TermsAndCondition);
p[11].DbType = DbType.String;
p[12] = new SqlParameter("@Others", this._Others);
p[12].DbType = DbType.String;
p[13] = new SqlParameter("@SizeOfOrganisation",
this._SizeOfOrganisation);
p[13].DbType = DbType.Int16;
SqlHelper.ExecuteNonQuery(con, CommandType.StoredProcedure,
"Sp_InsertRecruiterOrganisationDetails", p);

public bool CheckReruiterAvailability()

{
int count;
SqlParameter[] p = new SqlParameter[1];
p[0] = new SqlParameter("@UserName", this._UserName);
p[0].DbType = DbType.String;
count = int.Parse(SqlHelper.ExecuteScalar(con,
CommandType.StoredProcedure, "SpCheckReruiterAvailability",
p).ToString());
if (count > 0)
return true;
else

return false;

- 183 -
 }

public bool RecruiterPasswordCheck()

{
int count;
SqlParameter[] p = new SqlParameter[3];
p[0] = new SqlParameter("@UserName", this._UserName);
p[0].DbType = DbType.String;
p[1] = new SqlParameter("@HintQuestion", this._HintQuestion);
p[1].DbType = DbType.String;
p[2] = new SqlParameter("@Answer", this._Answer);
p[2].DbType = DbType.String;
count = int.Parse(SqlHelper.ExecuteScalar(con,
CommandType.StoredProcedure, "Sp_RecruiterPasswordCheck",
p).ToString());
if (count > 0)
return true;
else

return false;
}
public DataSet ShowRecruiterForgotPassword()
{
SqlParameter[] p = new SqlParameter[3];
p[0] = new SqlParameter("@UserName", this._UserName);
p[0].DbType = DbType.String;
p[1] = new SqlParameter("@HintQuestion", this._HintQuestion);
p[1].DbType = DbType.String;
p[2] = new SqlParameter("@Answer", this._Answer);
p[2].DbType = DbType.String;
ds = new DataSet();
ds = SqlHelper.ExecuteDataset(con,
CommandType.StoredProcedure, "SpShow_RecruiterForgotPassword", p);
return ds;
}
public DataSet ShowRecruiterLoginInfo()
{
SqlParameter[] p = new SqlParameter[1];
p[0] = new SqlParameter("@UserName", this._UserName);
p[0].DbType = DbType.String;
ds = new DataSet();
ds = SqlHelper.ExecuteDataset(con,
CommandType.StoredProcedure, "Sp_Show_RecruiterLoginInfo", p);
return ds;
}
public DataSet RecruiterPasswordVerify()
{
SqlParameter[] p = new SqlParameter[1];
p[0] = new SqlParameter("@UserName", this._UserName);
p[0].DbType = DbType.String;
ds = new DataSet();

- 184 -
 ds = SqlHelper.ExecuteDataset(con,
CommandType.StoredProcedure, "Sp_RecruiterPasswordVerify", p);
return ds;
}
public void ModifyRecruiterRegestration()
{
SqlParameter[] p = new SqlParameter[4];
p[0] = new SqlParameter("@UserName", this._UserName);
p[0].DbType = DbType.String;
p[1] = new SqlParameter("@Password", this._Password);
p[1].DbType = DbType.String;
p[2] = new SqlParameter("@HintQuestion", this._HintQuestion);
p[2].DbType = DbType.String;
p[3] = new SqlParameter("@Answer", this._Answer);
p[3].DbType = DbType.String;
SqlHelper.ExecuteNonQuery(con, CommandType.StoredProcedure,
"Sp_Modify_RecruiterRegestration", p);
}
//Recruiter Organization Detail
public DataSet ShowRecruiterProfile()
{
SqlParameter[] p = new SqlParameter[1];
p[0] = new SqlParameter("@UserName", this._UserName);
p[0].DbType = DbType.String;
ds = new DataSet();
ds = SqlHelper.ExecuteDataset(con,
CommandType.StoredProcedure, "Sp_Show_RecruiterProfile", p);
return ds;
}
public void ModifyRecruiterOrganisationDetails()
{
SqlParameter[] p = new SqlParameter[14];
p[0] = new SqlParameter("@UserName", this._UserName);
p[0].DbType = DbType.String;
p[1] = new SqlParameter("@OrganisationName",
this._OrganisationName);
p[1].DbType = DbType.String;
p[2] = new SqlParameter("@BusinessSector",
this._BusinessSector);
p[2].DbType = DbType.String;
p[3] = new SqlParameter("@Certificate1", this._Certificate1);
p[3].DbType = DbType.String;
p[4] = new SqlParameter("@Certificate2", this._Certificate2);
p[4].DbType = DbType.String;
p[5] = new SqlParameter("@Certificate3", this._Certificate3);
p[5].DbType = DbType.String;
p[6] = new SqlParameter("@Website", this._Website);
p[6].DbType = DbType.String;
p[7] = new SqlParameter("@EmailID1", this._EmailID1);
p[7].DbType = DbType.String;
p[8] = new SqlParameter("@EmailID2", this._EmailID2);
p[8].DbType = DbType.String;

- 185 -
 p[9] = new SqlParameter("@Address", this._Address);
p[9].DbType = DbType.String;
p[10] = new SqlParameter("@OrganisationEnvironment",
this._OrganisationEnvironment);
p[10].DbType = DbType.String;
p[11] = new SqlParameter("@TermsAndCondition",
this._TermsAndCondition);
p[11].DbType = DbType.String;
p[12] = new SqlParameter("@Others", this._Others);
p[12].DbType = DbType.String;
p[13] = new SqlParameter("@SizeOfOrganisation",
this._SizeOfOrganisation);
p[13].DbType = DbType.Int16;
SqlHelper.ExecuteNonQuery(con, CommandType.StoredProcedure,
"Sp_Modify_RecruiterOrganisationDetails", p);

}
public bool CheckRecruiterLoginInfo()
{
int count;
SqlParameter[] p = new SqlParameter[2];
p[0] = new SqlParameter("@UserName", this._UserName);
p[0].DbType = DbType.String;
p[1] = new SqlParameter("@Password", this._Password);
p[1].DbType = DbType.String;
count = int.Parse(SqlHelper.ExecuteScalar(con,
CommandType.StoredProcedure, "Sp_CheckRecruiterLoginInfo",
p).ToString());
if (count > 0)
return true;
else

return false;
}
public DataSet ShowOrganizationDetailByOrg()
{
SqlParameter[] p = new SqlParameter[1];
p[0] = new SqlParameter("@OrgName", this._OrganisationName);
p[0].DbType = DbType.String;
ds = new DataSet();
ds = SqlHelper.ExecuteDataset(con,
CommandType.StoredProcedure, "Sp_ShowOrganizationDetailByOrg", p);
return ds;
}
public bool CheckAdminLoginInfo()
{
int count;
SqlParameter[] p = new SqlParameter[2];
p[0] = new SqlParameter("@UserName", this._UserName);
p[0].DbType = DbType.String;
p[1] = new SqlParameter("@Password", this._Password);
p[1].DbType = DbType.String;

- 186 -
 count = int.Parse(SqlHelper.ExecuteScalar(con,
CommandType.StoredProcedure, "Sp_CheckAdminLoginInfo", p).ToString());
if (count > 0)
return true;
else

return false;
}
//View Recruiter

public DataSet ShowAllRegisteredRecruiter()

{
SqlParameter[] p = new SqlParameter[2];
p[0] = new SqlParameter("@FromDate", this._FromDate);
p[0].DbType = DbType.Date;
p[1] = new SqlParameter("@ToDate", this._ToDate);
p[1].DbType = DbType.Date;
ds = new DataSet();
ds = SqlHelper.ExecuteDataset(con,
CommandType.StoredProcedure, "Sp_Show_AllRegisteredRecruiter", p);
return ds;
}
public void DeleteRegisterRecruiterInfo()
{
SqlParameter[] p = new SqlParameter[1];
p[0] = new SqlParameter("@UserName", this._UserName);
p[0].DbType = DbType.String;
SqlHelper.ExecuteNonQuery(con, CommandType.StoredProcedure,
"Sp_Delete_RegisterRecruiterInfo", p);
}
}

- 187 -
RECRUITER RESPONSE TO JOB SEEKER
using System;
using System.Data;
using System.Configuration;
using System.Web;
using System.Web.Security;
using System.Web.UI;
using System.Web.UI.WebControls;
using System.Web.UI.WebControls.WebParts;
using System.Web.UI.HtmlControls;
using System.Data.SqlClient;
using CareerPath.DAL;
/// <summary>
/// Summary description for RecruiterResponseToJobSeekeBL
/// </summary>
public class RecruiterResponseToJobSeekeBL:Connection
{
public static DataSet ds;
public RecruiterResponseToJobSeekeBL()
{
//
// TODO: Add constructor logic here
//
}
private string _JobSeekerId, _RecruiterName, _JobID;
private DateTime _DateOfResponse;
public string JobSeekerId
{
get { return _JobSeekerId; }
set { _JobSeekerId = value; }
}
public string RecruiterName
{
get { return _RecruiterName; }
set { _RecruiterName = value; }
}
public string JobID
{
get { return _JobID; }
set { _JobID = value; }
}
public DateTime DateOfResponse
{
get { return _DateOfResponse; }
set { _DateOfResponse = value; }
}

//Recruiter Response

- 188 -
 public void InsertRecruiterResponseToJobseeker()
{
SqlParameter[] p = new SqlParameter[4];
p[0] = new SqlParameter("@JobSeekerId", this._JobSeekerId);
p[0].DbType = DbType.String;
p[1] = new SqlParameter("@RecruiterName",
this._RecruiterName);
p[1].DbType = DbType.String;
p[2] = new SqlParameter("@JobID", this._JobID);
p[2].DbType = DbType.String;
p[3] = new SqlParameter("@DateOfResponse",
this._DateOfResponse);
p[3].DbType = DbType.Date;
SqlHelper.ExecuteNonQuery(con, CommandType.StoredProcedure,
"Sp_InsertRecruiterResponseToJobseeker", p);

}
public DataSet ShowAppliedJobDetailOfJobsseker()
{
SqlParameter[] p = new SqlParameter[1];
p[0] = new SqlParameter("@JobSeekerId", this._JobSeekerId);
p[0].DbType = DbType.String;
ds = new DataSet();
ds = SqlHelper.ExecuteDataset(con,
CommandType.StoredProcedure, "Sp_ShowAppliedJobDetailOfJobsseker", p);
return ds;
}
public DataSet ShowRecruiterResponseDetail()
{
SqlParameter[] p = new SqlParameter[1];
p[0] = new SqlParameter("@JobSeekerId", this._JobSeekerId);
p[0].DbType = DbType.String;
ds = new DataSet();
ds = SqlHelper.ExecuteDataset(con,
CommandType.StoredProcedure, "Sp_ShowRecruiterResponseDetail",p);
return ds;
}
public bool ShowJobOfferStatus()
{
int count;
SqlParameter[] p = new SqlParameter[3];
p[0] = new SqlParameter("@RecruiterName",
this._RecruiterName);
p[0].DbType = DbType.String;
p[1] = new SqlParameter("@JobSeekerId", this._JobSeekerId);
p[1].DbType = DbType.String;
p[2] = new SqlParameter("@JobID", this._JobID);
p[2].DbType = DbType.String;
count = int.Parse(SqlHelper.ExecuteScalar(con,
CommandType.StoredProcedure, "Sp_ShowJobOfferStatus", p).ToString());
if (count > 0)
return true;

- 189 -
 else

return false;
}
public DataSet ShowRecruiterResponse()
{
ds = new DataSet();
ds = SqlHelper.ExecuteDataset(con,
CommandType.StoredProcedure, "Sp_ShowRecruiterResponse");
return ds;
}
}

- 190 -
 SKILL MASTER
using System;
using System.Data;
using System.Configuration;
using System.Web;
using System.Web.Security;
using System.Web.UI;
using System.Web.UI.WebControls;
using System.Web.UI.WebControls.WebParts;
using System.Web.UI.HtmlControls;
using System.Data.SqlClient;
using CareerPath.DAL;
/// <summary>
/// Summary description for SkillMasterBL
/// </summary>
public class SkillMasterBL:Connection
{
public static DataSet ds;
public SkillMasterBL()
{
//
// TODO: Add constructor logic here
//
}
string _Type, _Description;
public string Type
{
get { return _Type; }
set { _Type = value; }
}
public string Description
{
get { return _Description; }
set { _Description = value; }
}
private int _SkillId;
public int SkillId
{
get { return _SkillId; }
set { _SkillId = value; }
}
public void InsertSkills()
{
SqlParameter[] p = new SqlParameter[2];
p[0] = new SqlParameter("@Type", this._Type);
p[0].DbType = DbType.String;
p[1] = new SqlParameter("@Description", this._Description);
p[1].DbType = DbType.String;

- 191 -
 SqlHelper.ExecuteNonQuery(con, CommandType.StoredProcedure,
"Sp_Insert_Skills", p);
}
public DataSet ShowSkills()
{
ds = new DataSet();
ds = SqlHelper.ExecuteDataset(con,
CommandType.StoredProcedure, "Sp_Show_Skills");
return ds;
}
public void DeleteSkill()
{
SqlParameter[] p = new SqlParameter[1];
p[0] = new SqlParameter("@SkillId", this._SkillId);
p[0].DbType = DbType.Int16;
SqlHelper.ExecuteNonQuery(con, CommandType.StoredProcedure,
"Sp_Delete_Skill", p);

}
public void UpdateSkill()
{
SqlParameter[] p = new SqlParameter[3];
p[0] = new SqlParameter("@SkillId", this._SkillId);
p[0].DbType = DbType.Int16;
p[1] = new SqlParameter("@SkillType", this._Type);
p[1].DbType = DbType.String;
p[2] = new SqlParameter("@Description", this._Description);
p[2].DbType = DbType.String;
SqlHelper.ExecuteNonQuery(con, CommandType.StoredProcedure,
"Sp_Update_Skill", p);

}
public DataSet ShowSkillInfoById()
{
SqlParameter[] p = new SqlParameter[1];
p[0] = new SqlParameter("@SkillId", this._SkillId);
p[0].DbType = DbType.Int16;
ds = new DataSet();
ds = SqlHelper.ExecuteDataset(con,
CommandType.StoredProcedure, "Sp_ShowSkillInfoById", p);
return ds;
}
}

- 192 -
 STATE
using System;
using System.Data;
using System.Configuration;
using System.Web;
using System.Web.Security;
using System.Web.UI;
using System.Web.UI.WebControls;
using System.Web.UI.WebControls.WebParts;
using System.Web.UI.HtmlControls;
using CareerPath.DAL;
using System.Data.SqlClient;
/// <summary>
/// Summary description for StateBL
/// </summary>
public class StateBL:Connection
{
public static DataSet ds;
public StateBL()
{
//
// TODO: Add constructor logic here
//
}
string _Name, _Description;
int countryId,_StateId;
public int StateId
{
get { return _StateId; }
set { _StateId = value; }
}
public int CountryId
{
get { return countryId; }
set { countryId = value; }
}
public string Name
{
get { return _Name; }
set { _Name = value; }
}

public string Description

{
get { return _Description; }
set { _Description = value; }
}

public void InsertState()

- 193 -
 {
SqlParameter[] p = new SqlParameter[3];
p[0] = new SqlParameter("@Name", this._Name);
p[0].DbType = DbType.String;
p[1] = new SqlParameter("@Description", this._Description);
p[1].DbType = DbType.String;
p[2] = new SqlParameter("@CountryId", this.countryId);
p[2].DbType = DbType.Int16;
SqlHelper.ExecuteNonQuery(con, CommandType.StoredProcedure,
"Sp_Insert_State", p);

}
public DataSet ShowAllState()
{ ds = new DataSet();
ds = SqlHelper.ExecuteDataset(con,
CommandType.StoredProcedure, "Sp_Show_State");
return ds;
}
public DataSet GetStateByCountryId()
{
SqlParameter[] p = new SqlParameter[1];
p[0] = new SqlParameter("@countryid", this.countryId);
p[0].DbType = DbType.Int16;
ds = new DataSet();
ds = SqlHelper.ExecuteDataset(con,
CommandType.StoredProcedure, "SpGetStateByCountryId", p);
return ds;
}
public void DeleteState()
{
SqlParameter[] p = new SqlParameter[1];
p[0] = new SqlParameter("@StateId", this._StateId);
p[0].DbType = DbType.Int16;
SqlHelper.ExecuteNonQuery(con, CommandType.StoredProcedure,
"Sp_Delete_State", p);

}
public void UpdateState()
{
SqlParameter[] p = new SqlParameter[3];
p[0] = new SqlParameter("@StateId", this._StateId);
p[0].DbType = DbType.Int16;
p[1] = new SqlParameter("@StateName", this._Name);
p[1].DbType = DbType.String;
p[2] = new SqlParameter("@Description", this._Description);
p[2].DbType = DbType.String;
SqlHelper.ExecuteNonQuery(con, CommandType.StoredProcedure,
"Sp_Update_State", p);

}
public DataSet ShowStateInfoById()
{

- 194 -
 SqlParameter[] p = new SqlParameter[1];
p[0] = new SqlParameter("@StateId", this._StateId);
p[0].DbType = DbType.Int16;
ds = new DataSet();
ds = SqlHelper.ExecuteDataset(con,
CommandType.StoredProcedure, "Sp_ShowStateInfoById", p);
return ds;
}
}

- 195 -
 STUDENT DETAIL
using System;
using System.Data;
using System.Configuration;
using System.Web;
using System.Web.Security;
using System.Web.UI;
using System.Web.UI.WebControls;
using System.Web.UI.WebControls.WebParts;
using System.Web.UI.HtmlControls;
using System.Data.SqlClient;
using CareerPath.DAL;
/// <summary>
/// Summary description for StudentDetailBL
/// </summary>
public class StudentDetailBL:Connection
{
public static DataSet ds;
public StudentDetailBL()
{
//
// TODO: Add constructor logic here
//
}
string _RollNo, _Name, _PassingYear;
public string RollNo
{
get { return _RollNo; }
set { _RollNo = value; }
}
public string Name
{
get { return _Name; }
set { _Name = value; }
}
public string PassingYear
{
get { return _PassingYear; }
set { _PassingYear = value; }
}
private int _QualificationId;
public int QualificationId
{
get { return _QualificationId; }
set { _QualificationId = value; }
}
public void InsertStudentDetail()
{

- 196 -
 SqlParameter[] p = new SqlParameter[4];
p[0] = new SqlParameter("@RollNo", this._RollNo);
p[0].DbType = DbType.String;
p[1] = new SqlParameter("@Name", this._Name);
p[1].DbType = DbType.String;
p[2] = new SqlParameter("@QualificationId",
this._QualificationId);
p[2].DbType = DbType.Int16;
p[3] = new SqlParameter("@PassingYear", this._PassingYear);
p[3].DbType = DbType.String;
SqlHelper.ExecuteNonQuery(con, CommandType.StoredProcedure,
"Sp_Insert_StudentDetail", p);
}
}

- 197 -
 Chapter 10

CONCLUSION

It has been a great pleasure for me to work on this exciting and challenging
project. This project proved good for me as it provided practical knowledge
of not only programming in ASP.NET and VB.NET web based application and
no some extent Windows Application and SQL Server, but also about all
handling procedure related with PROJECT NAME. It also provides
knowledge about the latest technology used in developing web enabled
application and client server technology that will be great demand in future.
This will provide better opportunities and guidance in future in developing
projects independently.

BENEFITS:

The project is identified by the merits of the system offered to the user. The
merits of this project are as follows: -

Its a web-enabled project.

This project offers user to enter the data through simple and interactive
forms. This is very helpful for the client to enter the desired information
through so much simplicity.

LIMITATIONS:

The size of the database increases day-by-day, increasing the load on the
database back up and data maintenance activity.
Training for simple computer operations is necessary for the users
working on the system.

- 198 -
 Chapter 11

BIBLIOGRAPHY

FOR .NET INSTALLATION

www.support.mircosoft.com
FOR DEPLOYMENT AND PACKING ON SERVER
www.developer.com
www.15seconds.com
FOR SQL
www.msdn.microsoft.com
FOR ASP.NET
www.msdn.microsoft.com/net/quickstart/aspplus/default.c
om
www.asp.net
www.fmexpense.com/quickstart/aspplus/default.com
www.asptoday.com
www.aspfree.com
www.4guysfromrolla.com/index.aspx

- 199 -