Online Voting Software

ABSTRACT:

The project "Voting Software" aims at making the voting process easy in cooperative
societies.
Presently voting is performed using ballot paper and the counting is done manually, hence it
consumes a lot of time. There can be possibility of invalid votes. All these make election a
tedious task.
In our proposed system voting and counting is done with the help of computer. It
saves time, avoid error in counting and there will be no invalid votes. It makes the election
process easy.

All the co-operative societies conduct voting process to select right person for holding
reputed position. Our project aims at helping the voting process in co-operative societies.
The manual involvement needed in the process becomes in reduced amount and make the
process easy. It saves our time and the result can be published quickly.

SYSTEM ANALYSIS

EXISTING SYSTEM:

There is no system which provides the convenience of voting though the system, hence
our system provides the easy way of voting. The online voting is a new trend in the market
where we focus on convenience and full voting percentage. Because many people don’t vote just
because they need to wait in the queue for registering the vote, hence our proposed application
will solve this problem.

DISADVATANGES:

1. Voting is not possible because one has to wait for registering the vote
 2. We need to use lot of resources which makes the traditional voting costlier

3. Many personnel is needed for this type of voting.

PROPOSED SYSTEM

1. Counting the total number of votes.

2. Percentage of total votes.

3. Number of votes for each candidate.

4. Percentage of votes for each candidate.

5. Checking for duplication.

6. Finding the winning person

7. . Finding the margin of votes

MODULES

We have devised the following modules according to the requirements of the

organization.

1. Administrator

2. User

3. CitizenInfo

4. Voting Details

5. Candidates information
Administrator has the whole authority of the organization .He is the one
who maintains all the aspects of voters and candidates. His functionalities include insertion,
updation, and deletion of both the voter and the candidate. He is responsible for allowing persons
to vote.

User's have the provision to view the list of voters’ candidates and results and to vote for their
desired candidate.

ADVANTAGES

1. To count the total number of votes.

2. To calculate the percentage of total votes.

3. To calculate votes for each candidate.

4. To calculate percentage of votes for each candidate.

5. To check for duplication.

6. To find the winning persons in each section.

All the process above mentioned should be done fast

1. It will reduce the manual work.

2. Retrieval and insertion of information becomes easy

3. Voting process becomes fast.

4. Duplication will be avoided.

5. Re-voting can be prevented.

 This system makes it easier for the co-operative societies in voting activities.
It will help to announce the results faster. It will reduce the manual work.
Reduce complaints about voting. It will also reduce the paper work.

Feasibility study
Analysis and evaluation of a proposed project to determine if it is technically feasible, is
feasible within the estimated cost, and will be profitable. Feasibility studies are almost always
conducted where large sums are at stake. Also called feasibility analysis.

The main difficulty with this You have probably noticed that the same web page may
look different depending on what browser you are using and even what version of the browser.
In some cases a web page will not work properly unless you upgrade to the latest version of a
particular browser. Likewise a web page may work fine with an older browser but not a newer
one.

Now consider the company that deploys several browser-based applications. And then suddenly
one of those applications comes out with an upgrade that requires an upgrade to the current
standard company browser. If the company decides to upgrade the browser, there is a likely
consequence that some features of at lease one of the browser-based applications will
not work with the new browser. This leaves the company paralyzed. Do they upgrade the
browser and risk breaking some of the other browser-based applications? Do they allocate
extensive resources to testing the deployed browser-based applications to see if they will still
work with the new browser before deploying it? Or do they stay entrenched on old technology?

LANGUAGES USED:

HTML:

Learn basic HTML to create your Web site. Basic HTML is not hard to learn. Learning HTML is
probably the single most important thing you'll ever do if you want to create your own personal
Web site. You must learn HTML to design good pages because it is the language in which Web
site on the Internet are based on.
Web sites are a great way to show off something in your life. Basic HTML will let you show the
world whatever it is you want to show them on your Web site. Adding colors, changing text size
and including pictures on your Web site are just a few of the things you can do when you learn
basic HTML.

To learn basic HTML you must keep in mind that it's simply a series of letters that are
abbreviations of what they actually stand for. For example, H1 stands for a heading for a
paragraph that is the first of five sizes and BR is a line break.

One important thing to remember, while you learn basic HTML, is that on a Web page the
HTML tags must come in a certain order and most HTML tags must have a start and end tag for
the browser to recognize the command. An end tag is just simply the same as the start tag except
that it starts with the / symbol. A heading would look like this<H1>Heading Here</H1>. There
is a start tag,H1, the heading, and an end tag, /H1.

Learn basic HTML the right way and remember that the tags must come in a certain order. The
basic structure of a web page is as follows:

<HTML>

<HEAD> Here you can put important document information such as frames, language, and
special instructions.

<TITLE>Title of your page.</TITLE>

</HEAD>

<BODY> Put your story, pictures, links, and everything else here.

<H1>Heading of your paragraph.</H1>

<P>This is where you enter the text of your document.</P>

This is how to write a link:
<A HREF="http://www.nameofpage.com">Title or what you want to say.</A>

</BODY>

</HTML>

You can also enter a link into the middle of a sentence. If I wanted to say "Microsoft has some
wonderful demos." It would look like this:

<A HREF="http://www.microsoft.com/en/us/default.aspx">Microsoft </A>has some

wonderful demos to help you learn basic HTML.

You not only can create links to other pages but you can also create links to another place on the
same page. If I wanted you to go back to the beginning of this article I would say something like
"Go Back" and by clicking on the hyperlink you would go back to the beginning. This one is a
little more difficult because there are two parts to it. First of all you create your link:

<A HREF="nameofdocument#There">Go Back</A>

The word "There" is the word I want to take you back to so now I must go to that word and
create and anchor so the link I just created knows where to go:

<A NAME="There">There</A>

When you learn basic HTML you can write your Web site in the text editor that comes with
Windows, programs such as NoteTab and Arachnophilia, or one that comes with your web
browser. Either way if you just follow the rules from when you learned basic HTML everything
will turn out just fine.
The CSS visual formatting model is a way of laying out documents on visual media (such as a
computer screen or a printed page). By all accounts, it is a very simple formatting model, and the
publishing world has seen much more complicated ones. Still, it is not something that is simple
to explain or grasp in a few words.

Various CSS properties are used to control how a document will appear in the context of this
formatting model. You have seen most of them in the examples used so far, but I haven't
explained their usage because I have to explain the formatting model first.

As I said, the formatting model is a pretty complicated affair. As if that wasn't enough, though,
the implementations that exist, most notably in Microsoft Internet Explorer and Netscape
Navigator, are respectably problematic and horrible. Explorer does a pretty good job of sticking
to the model, and will behave sensibly with a few exceptions that can be dealt with simply.
Navigator, on the other hand, has its own concept of what the various properties should do.

Instead of going through the theory and observing the bugs in Explorer and Navigator along the
way, as I have done in the tutorials so far, I will explain the theory, that is how the CSS
specification explains formatting should be done, in this tutorial, and deal with the
implementations in the next one. I hope this makes the whole process easier to understand.

What Is a Tag?

A tag is a method of formatting HTML documents.

With tags you can create italic or bold characters, make things blink, and can control
the color and size of the lettering.

Tags can be "nested". This means that you can make

something bold and italic and green and blinking by simply surrounding the previous tag with
the next.

Tags can be used to insert pictures and graphics.

Tags can be used to create bulleted lists like this one, or numbered lists.
Tags look something like this: <b> chosen text </b> .

All tags use the < and > (less-than and greater-than symbols) to signal the browser. These are
located above the comma and period keys.

Within a tag, capitalization doesn't matter. <FONT> is the same as <font> or <Font> . I usually

don't bother capitalizing when I use tags. Below, I have used capital letters when I felt that the
number "1" and the letter "l" might be confused.

It is essential to always close the tags! If not, the formatting will contaminate everything that
follows it. But don't panic, closing tags is very easy, and even the most experienced surfers
sometimes forget.

ASP.NET:

Open your favorite text editor, Notepad will suffice, and paste the following HTML

code. Save the document as nowhere.html. Next, open the HTML file in your browser

of choice. The following HTML code will set up a perfectly clear HTML form that sends

information into the ether:

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"

"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">

<html xmlns="http://www.w3.org/1999/xhtml">

<head>

<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" />

<title>HTML to Nowhere</title>

</head>

<body>
<form>

Please enter your name:<br/>

<input type="text" name="username"/>

<p/>

Press the button to receive all of your hopes and dreams:<br/>

<input type="submit" value="Dream Button" />

</form>

</body>

</html>

When you test the code after you enter your name and click the Dream Button (a thinly

disguised submit button), your output will look just like Figure 1-1.

Without some kind of mechanism to capture and store the information or pass it on

to somewhere else, all you have is an HTML white elephant. What ASP.NET 3.5 offers

is a way to store, retrieve, and process the information. Other than storing cookies on the

visitor’s computer, you can’t do too much with HTML when it comes to controlling the

state of your data.

Your Browser Is a Thin Client

Your browser’s main job is requesting pages from the server and displaying what the

server has processed. Using HTTP as a transfer protocol, your browser parses (interprets)

the HTML code it gets from the server, but otherwise does little processing. Because your

HTTP client (browser) leaves most of the processing work to the server, it is considered a
thin client. There’s nothing wrong with a thin client, and it can process JavaScript. With

plug-ins, which virtually all browsers have built in, a thin client can also process certain kinds of
files such as SWF (compiled Adobe Flash files), Java Applets, ActiveX Controls, as well as
other files requiring that the browser have compatible plug-ins. For the most part, though, the
thin client model is one where the server does the processing, and your browser’s job is to
display the contents it gets from the server.

A Protocol Without a Country: Stateless HTTP

In addition to being a thin client, your HTTP client browser is stateless. As soon as a

web page reaches your computer, the connection between your browser and the server is broken.
The browser does not remember the last page—it does not hold state. As soon as the next page
arrives, it does not remember the last page.

You may be thinking that your cache holds lots of previous pages and that your

browser’s history feature remembers previous pages. That’s not what retaining state

means. You cannot use the data and information in your cache or the browser’s history as states
to use with the current page in memory. What is in active memory is the web page that the server
has sent; the state of the previous page is not there. As soon as you load a page, the previous
page is kicked out, and the new page is placed there. Just as the information you place in a text
input box is sent to silicon oblivion when you click the Submit button, knowledge of the
previous page (its state) is gone when the new page arrives. A well-organized web site may
appear to maintain state as the links on pages connect to a set of related pages, but that is an
illusion that the web designer has crafted by good planning.

ASP.NET 3.5 as an Alternative to CGI

Microsoft’s alternative to a Common Gateway Interface (CGI) is ASP.NET, now in

version 3.5. As a unified web platform, ASP.NET provides what you need to develop

applications that hold state and use the information that you put into the HTML form.
Instead of sending form information into a vacuum when you click a submit button, your data
goes where it can be stored temporarily or permanently. Usually, when we think of saving state,
we imagine writing the data to a storage device like a hard drive. Using a word processor, every
time you save your file, you save its state. Using ASP.NET, you can do the same thing with
information from anyone who uses your web application. This allows you to build applications
where the information entered can be stored for use with either the next HTTP request or with a
whole set of data entered by users all over the world—that’s quite a feat compared with saving
state in your word processor file. ASP.NET’s state-management facilities provide you with the
tools that you need to control state. You do not necessarily want to save all states of a web page,
but you certainly want to save the state of data entered by users and perhaps the URL of a page.
Having state management allows you to do this.

Microsoft’s web server, Internet Information Services (IIS), uses the Internet Server

API (ISAPI) to make function calls instead of using CGI scripts. By using ISAPI,

developers can create web-based applications that execute faster and have greater

extensibility than CGI, among other advantages. At the lowest level, ASP.NET interfaces with
IIS through an ISAPI extension. However, this book focuses on the high-level interaction with
ISAPI in the form of ASP.NET and code written in C# (pronounced “C sharp”) that use
ASP.NET. So rather than having to deal with the fine-grained, low-level communications,
ASP.NET allows

you to write your scripts in C#. Another way of looking at ASP.NET is as a requestprocessing
engine that takes incoming requests and sends them to a point where you can attach your C#
script to process the request.

So while we are not going to spend time dwelling on the low-level operations, you can rest
assured that those operations are handled in an efficient manner. Using managed code, the
Microsoft name for code that executes under the management of the .NET framework,

an application is executed by a virtual machine rather than by your own processor. Both C# and
Visual Basic.NET (VB.NET) are languages for creating managed code that is efficiently run in
the .NET environment.
From Client Side to Server Side

As you saw in Figure 1-2, all that the web browser does is make requests to the server and
receive web pages in the form of HTML. The browser takes the HTML and constructs a page for
viewing on your browser. For the most part, that’s what will continue to occur when you adopt
ASP.NET. The main difference is that by writing and executing serverside code, you can
generate HTML that effectively handles dynamic states so that you can use and reuse a given
state. Figure 1-3 shows the general flow when an ASPX file on a Microsoft server receives a call
from the client.

In looking for an example, we need look no further than the original example of the

HTML page with the form. With a server-side program to catch the data that is sent to

the server, lots of processes on the server are possible. Suppose the user enters the name,

Willie B. Goode. The server-side file can use the property name, username, to extract a

value. In this case, it would extract the name Willie B. Goode and do something with it. It

might run a SQL script to store the name in a database, compare it with a password, or it

could pass information about Willie B. Goode back to the browser in HTML.

To get an idea of the differences and similarities between HTML and ASP.NET, we

can take the HTML form and add a calculated response from the server. In this next

example, you will see two scripts. One is the ASP.NET script and the other is the C# code

using a code behind file to serve as the event engine for the application. The form tag

includes a name and the code

runat="server"

SQL:
Structured Query Language (SQL)

To work with data in a database, you must use a set of commands and statements (language)
defined by the DBMS software. There are several different languages that can be used with
relational databases; the most common is SQL. Standards for SQL have been defined by both the
American National Standards Institute (ANSI) and the International Standards Organization
(ISO). Most modern DBMS products support the Entry Level of SQL-92, the latest SQL
standard (published in 1992).

Client/Server Architecture

Microsoft® SQL Server™ is designed to work effectively in a number of environments:

As a two-tier or multitier client/server database system

As a desktop database system

Client/Server Database Systems

Client/server systems are constructed so that the database can reside on a central computer,
known as a server, and be shared among several users. Users access the server through a client or
server application:

In a two-tier client/server system, users run an application on their local computer, known as a
client, that connects over a network to the server running SQL Server. The client application runs
both business logic and the code to display output to the user, and is also known as a thick client.

In a multitier client/server system, the client application logic is run in two locations:

The thin client is run on the user’s local computer and is focused on displaying results to the
user. The business logic is located in server applications running on a server. Thin clients
request functions from the server application, which is itself a multithreaded application capable
of working with many concurrent users. The server application is the one that opens connections
to the database server and can be running on the same server as the database, or it can connect
across the network to a separate server operating as a database server. This is a typical scenario
for an Internet application. For example, a server application can run on a Microsoft Internet
Information Services (IIS) and service thousands of thin clients running on the Internet or an
intranet. The server application uses a pool of connections to communicate with a copy of SQL
Server. SQL Server can be installed on the same computer as IIS, or it can be installed on a
separate server in the network. Having data stored and managed in a central location offers
several advantages:

Each data item is stored in a central location where all users can work with it. Separate copies of
the item are not stored on each client, which eliminates problems with users having to ensure
they are all working with the same information. Business and security rules can be defined one
time on the server and enforced equally among all users.

This can be done in a database through the use of constraints, stored procedures, and triggers. It
can also be done in a server application.

A relational database server optimizes network traffic by returning only the data an application
needs. For example, if an application working with a file server needs to display a list of the
names of sales representatives in Oregon, it must retrieve the entire employee file. If the
application is working with a relational database server, it sends this command:

SELECT first_name, last_name

FROM employees

WHERE emp_title = 'Sales Representative'

  AND emp_state = 'OR'

  

The relational database sends back only the names of the sales representatives in Oregon, not all
of the information about all employees.
 ABOUT SOFTWARE

INTRODUCTION ABOUT VB.NET

ASP.NET:

What distinguishes the web hobbyist from the professional developer is the ability to
store and retrieve data from a server over the Internet. Some readers may have made that step
with PHP or Perl, and for them the journey has already begun. For others, ASP.NET 3.5 is just
the next step in the growth and development of ASP.NET. For them, much will be familiar and
some will be very new. If the transition is from ASP.NET using Visual Basic to ASP.NET with
C#, then you will find even more new, and the transition to C# is going to be easier than many
imagine. Still others are making the first step into the realm of server-side programming, so just
about everything about ASP.NET 3.5 and C# 3.0 is new.For those using ASP.NET for the first
time, the good news is that the transition to the server side could hardly be easier. Everything in
this book is set up to learn ASP.NET 3.5 and C# 3.0 using Visual Studio 2008. Using the tools
built into Visual Studio 2008, you will quickly learn that most of what needs to be done can be
accomplished by dragging controls into a visual editor. And with the “code behind” method, C#
is added in a separate file, so when editing code, you will see a clear separation—the C# 3.0 code
comes “behind” the ASP.NET 3.5 code. For the most part, though, you need only a minimum of
coding skills in either ASP.NET, which feels a lot like HTML, or C#, which has many features
recognizable from JavaScript. However, make no mistake about it, C# 3.0 is a full-fledged
coding language with the power of any good object-oriented programming (OOP) language.
Most of the C# you need is simply working with functions and subroutines called by ASP.NET
events. As a result, learning C# is quite simple, and you’ll get a lot of help from Visual Studio
2008 coding tips and built-in IntelliSense. However, if you wish not to use Visual Studio 2008,
all of the code for both the ASP.NET and C# is provided as well. (You can program it all using
Notepad if you like!) You can find a free Express version of Visual Studio 2008 at www.micr
osoft.com/express/download/, and it has much of the functionality of the full-fledged version.
Likewise, you will find an Express Edition of SQL Server 2005, and with them both you can
learn ASP.NET 3.5 and C# 3.0 on a budget while using a powerful development tool.
 The main use of ASP.NET in conjunction with C# and Structured Query Language
(SQL) is to store user input in a database and get it back again. If you’ve ever dealt with forms in
HTML, you may know how frustrating it is to build a web site with data entry that cannot be
stored. In fact, without some kind of storage facility and the tools required to place the data in
storage, HTML forms have very limited use. However, not only can you use plain HTML forms,
ASP.NET 3.5 has some web controls that are almost identical to HTML forms except they have
far more functionality. In no time, you’ll be working with tables and databases to store, fetch,
change, and delete a wide variety of data. In addition to the HTML-like controls, a whole other
set of web controls is available to work with data and create objects that HTML cannot. For
example, if your web site needs a calendar, all you have to do with ASP.NET 3.5 is add a
calendar control by dragging it from the Toolbox and into the editor. Then you can use the
Calendar properties to perform other functions, like reminding you of your upcoming
anniversary. (Getting that right can be worth the price of this book!)

All in all, my hope is that you will enjoy working with ASP.NET 3.5 and C# 3.0 as much
as I have. Not only is it very easy to develop rich interactive web sites using ASP.NET, but in
conjunction with C# 3.0, the toolset is also a very powerful one. With it, you have the best

of all worlds.

In this tutorial we will explore this wonderful free tool along with its advantages
especially for new web developers. After downloading and installing the Visual Web Developer
2005 express edition form this link, run it and you will get this start up page as shown in figure1
below.
 As you see, it nearly seems like Visual Studio 2005. If you clicked the "File" menu you
will see the menu item "New Web Site ...", you can not create other types of applications except
web applications. As Visual Studio you will have a toolbox, a properties window, a solution
explorer window, a debugging menu, and so on. All these items give you the ability to control
your application and visually designing it in a simple WYSIWYG drag and drop interface.

Visually Design Your Data

Visual Web Developer provides a set of controls dialogs and wizards to help you in
communicating with a certain database or data source. First of all you can install SQL Server
2005 Express Edition while you are installing the Visual Web Developer. SQL Server Express
Edition is a lightweight database server designed for smaller load web sites. Now let's browse
what Visual Web Developer provides for ease of using manipulating and requesting data from a
data source.

Data Source Configuration Wizard provides a step by step wizard to help you connecting to a
data source, whether this source is an SQL database, an Access database, an XML database, and
more. The wizard dynamically pulls the tables along with their fields from the data source
allowing you to select the fields you want to display.

Figure 6 - Data Source Configuration Wizard

Basic .NET or C#.

Most of the samples in this book were written by hand, without the help of Visual
Studio .NET. That’s not a knock on Visual Studio .NET; it’s evidence of my belief that learning
is best accomplished by coding and not by having someone else code for you. Once you
understand what goes into a Windows form or a Web form or a Web service, you’ll find Visual
Studio .NET an able partner in helping to create them. Writing applications the old-fashioned
way first will increase your depth of understanding and better prepare you to work in an
environment in which tools shoulder part of the load for you.

C# (see section on name, pronunciation) is an object-oriented programming language

developed by Microsoft as part of the .NET initiative and later approved as a standard by ECMA
and ISO.

Anders Hejlsberg leads development of the C# language, which has a procedural, object-oriented
syntax based on C++ and includes aspects of several other programming languages (most
notably Delphi and Java) with a particular emphasis on simplification.
 C# principal designer and lead architect at Microsoft is Anders Hejlsberg. His previous
experience in programming language and framework design (Visual J++, Borland Delphi, and
Turbo Pascal) can be readily seen in the syntax of the C# language, as well as throughout the
Common Language Runtime (CLR) core.

C# is intended to be a simple, modern, general-purpose, object-oriented programming language.

.NET Framework 1.1 

This is the first major .NET Framework upgrade. It is available on its own as a
redistributable package or in a software development kit, and was published April 3, 2003. It is
also part of the second release of Microsoft Visual Studio .NET (released as Visual Studio .NET
2003). This is the first version of the .NET Framework to be included as part of the Windows
operating system, shipping with Windows Server 2003. 

Why C#? 

Many people believed that there was no need for a new programming language. Java, C+
+, Perl, Microsoft Visual Basic, and other existing languages were believed to offer all the
functionality needed.  

C# is a language derived from C and C++, but it was created from the ground up. Microsoft
started with what worked in C and C++ and included new features that would make these
languages easier to use. Many of these features are very similar to what can be found in Java.
Ultimately, Microsoft had a number of objectives when building the language. These objectives
can be summarized in the claims Microsoft makes about C#: 
C# is simple.

C# is modern.

C# is object-oriented.

In addition to Microsoft's reasons, there are other reasons to use C#:

C# is powerful and flexible.

C# is a language of few words.

C# is modular.

C# will be popular.

C# Is Simple 

C# removes some of the complexities of languages such as Java and C++, including the removal
of macros, templates (in the form of Generic in C# 2.0), multiple inheritance, and virtual base
classes. These are all areas that cause either confusion or potential problems for C++ developers.

What is C#? 

C# (pronounced C sharp) is a new programming language introduced by Microsoft with

the Microsoft .NET framework. It was first created in the late 1990's as part of Microsoft’s.NET
strategy. It is a new language free of backward compatibility and a bunch of new, exciting and
promising features. 

It is an Object Oriented Programming language, which at its core, and has similarities with Java,
C++ and VB. The main brains behind C# were Anders Hejlsberg and Scott Wiltamuth. However,
many other personalities like Rob Howard, Scott Guthrie were also involved behind C# and
the .NET Framework.

 In fact, C# combines the power & efficiency of C++, simple & clean Object Oriented design of
Java, and code simplification of Visual Basic. Like Java, C# also does not allow multiple
inheritance and use of pointers (in safe and managed code) while it does provide garbage
memory collection at runtime, type and memory access checking.  

But, contrary to java, C# keeps the different useful concepts of C++ like operator overloading,
enumerations, pre-processor directives, pointers (in unmanaged and un-safe code), function
pointers (in the form of delegates), also promises to have template support (with the name of
generics) in next versions. Like VB it also supports the concepts of properties (context sensitive
accessor to fields). 

In addition to this, C# comes up with some new/exciting features like reflections, attributes,
marshalling, remoting, threads, streams, data access with ADO.NET, etc. C# programming
language is designed from the scratch keeping in mind the Microsoft.Net environment. MS.Net
(and thus C#) programs runs on top of the Common Language Runtime (CLR), which provides
the runtime support to them.  

C# has been standardized by ECMA (European Computer Manufactures Association) 

Microsoft originally released beta versions of .NET framework to get feedback about the product
from developers and customers. Based on the feedback, received from them for the first beta,
Microsoft released second beta in early 2001. Finally, they released final versions of C# under
the name, .NET Framework 1.0 in 2002 and that of 1.1 in 2003. 

With each release, the product shipped with improved features for developing secured and
scalable applications along with high quality documentation. Like C++ and Java, C# is an object
oriented programming language. In fact all .NET languages are object oriented since they all
have the .NET Framework built into them.
SQL:

SQL is the acronym for Structured Query Language. This language is used for
developing database related applications. Before developing any application of database it is
necessary to understand what is Database?

Database:

A database can be defined as the collection of tables of relative Application. For example
if you are developing an application for maintaining the information of an university then you
have to create database with name STUDENT after words you can create any number of tables
related to that Student.

Now a table is nothing but the combination of Rows & Columns. The columns are known as the
Attributes or Properties of the table and Columns are known as Tuples, which are the actual
values of the respective column headers.

Attributes

Tuples Structure of a Table

Fig. The structure of a Table

QUERIES:

The queries can be defined as statements, which can be used to develop the database
related applications. There are different queries in SQL some major queries are explained below.

CREATE DATABASE Database_Name

This query will create a database with the name given in place of Database_Name.

Ex: CREATE DATABASE Student

Now you have to enter your database by using the following query.

USE Database_Name

Ex: USE Student

Now developer can create the tables related to university in this database. To create the tables the
following query can be used.

CREATE TABLE Table_Name (Column_Name DATATYPE)

Here Table_Name and Column_Name are any valid variable names and datatype should any of
the following.

Integer-> Represented as int, and can be used if the column is going to hold whole numbers.
Real Numbers-> Represented as float, and can be used if the column is going to hold fractional
numbers.

Characters-> Represented as varchar, and can be used if the column is going to hold characters
or strings. If you are mentioning the datatype of a column as varchar then it also necessary to
mention the space within the bracket, which indicates how many characters a column should
store.

Ex: CREATE TABLE student (STD_No int, Emp_Name varchar (10), marks float)

After the creation of tables we can insert the values in that table by using the following query.

INSERT INTO Table_Name VALUES (Values)

If the datatype of a column is int or float then you can write the Numbers directly but if datatype
is varchar then the values should be enclosed within the single quotations

Ex: INSERT INTO student (1,’R.R. Sharma’, 20)

Apart from above mentioned queries SQL has many more queries as

Mentioned below.

Update -> Used to update the contents of a table

Alter -> To alter the table i.e., You can add the columns or remove the columns

Drop -> to drop tables or databases

Delete -> to delete contents of the table.

Design goals and principal features:

Microsoft .NET Framework was designed with several intentions: 

Interoperability - Because interaction between new and older applications is commonly

required, the .NET Framework provides means to access functionality that is implemented in
programs that execute outside the .NET environment. Access to COM components is provided in
the System.Runtime.InteropServices and System.EnterpriseServices namespaces of the
framework, and access to other functionality is provided using the P/Invoke feature.

Common Runtime Engine - Programming languages on the .NET Framework compile

into an intermediate language known as the Common Intermediate Language, or CIL (formerly
known as Microsoft Intermediate Language, or MSIL). In Microsoft's implementation, this
intermediate language is not interpreted, but rather compiled in a manner known as just-in-time
compilation (JIT) into native code. The combination of these concepts is called the Common
Language Infrastructure (CLI), a specification; Microsoft's implementation of the CLI is known
as the Common Language Runtime (CLR). 

Language Independence - The .NET Framework introduces a Common Type System,

or CTS. The CTS specification defines all possible datatypes and programming constructs
supported by the CLR and how they may or may not interact with each other. Because of this
feature, the .NET Framework supports development in multiple programming languages. This is
discussed in more detail in Microsoft .NET Languages. 
 Base Class Library - The Base Class Library (BCL), part of the Framework Class
Library (FCL), is a library of types available to all languages using the .NET Framework. The
BCL provides classes which encapsulate a number of common functions, including file reading
and writing, graphic rendering, database interaction and XML document manipulation. 

Simplified Deployment - Installation of computer software must be carefully managed

to ensure that it does not interfere with previously installed software. The .NET framework
includes design features and tools that help address these requirements. 

Security - .NET allows for code to be run with different trust levels without the use of a
separate sandbox.

A design goal of the .NET Framework was to support platform independence. That is, a
program written to use the framework should run without change on any type of computer for
which the framework is implemented.  

However, Microsoft has only implemented the full .NET framework on the Windows
operating system. Microsoft and others have implemented portions of the framework on non-
Windows systems, but to date these implementations are neither complete nor widely used, so
full cross-platform support has not been achieved.

About C#: C# & other OOP language

 

C# versus C++ 

C++ is the closest relative of C#, although it has some elements derived from Visual Basic and
Java. In an important change from C++, C# code does not require header files. All code is
written inline. 

As touched on above, the .NET runtime in which C# runs performs memory management, taking
care of tasks like garbage collection. Because of this, the use of pointers in C# is much less
important than in C++. Pointers can be used in C#, where the code is marked as 'unsafe' but they
are only really useful in situations where performance gains are at an absolute premium.  

Speaking generally, the 'plumbing' of C# types is different from that of C++ types, with
all C# types being ultimately derived from the 'object' type. There are also specific differences in
the way that certain common types can be used. For instance, C# arrays are bounds checked
unlike in C++, and it is therefore not possible to write past the end of a C# array.  

C# statements are quite similar to C++ statements. To note just one example of a
difference: the 'switch' statement has been changed so that 'fall-through' behavior is disallowed. 

As mentioned above, C# gives up on the idea of multiple class inheritance. Other

differences relating to the use of classes are: there is support for class 'properties' of the kind
found in Visual Basic, and class methods are called using the . (Dot) operator rather than the:
operator.

C# versus Java 

C# and Java are both new-generation languages descended from a line including C and
C++. Each includes advanced features, like garbage collection, which remove some of the low
level maintenance tasks from the programmer. In a lot of areas they are syntactically similar. 
 Both C# and Java compile initially to an intermediate language: C# to Microsoft
Intermediate Language (MSIL), and Java to Java bytecode. In each case the intermediate
language can be run - by interpretation or just-in-time compilation - on an appropriate 'virtual
machine'. In C#, however, more support is given for the further compilation of the intermediate
language code into native code.

C# contains more primitive data types than Java, and also allows more extension to the
value types. For example, C# supports 'enumerations', type-safe value types which are limited to
a defined set of constant variables, and 'structs', which are user-defined value types.  

Note: Java doesn't have enumerations, but there is a standard way of emulating them. 

Unlike Java, C# has the useful feature that we can overload various operators. Like Java,
C# gives up on multiple class inheritance in favour of a single inheritance model extended by the
multiple inheritances of interfaces. However, polymorphism is handled in a more complicated
fashion; with derived class methods either 'overriding' or 'hiding' super class methods 

C# also uses 'delegates' - type-safe method pointers. These are used to implement event-
handling. In Java, multi-dimensional arrays are implemented solely with single-dimensional
arrays (where arrays can be members of other arrays. In addition to jagged arrays, however, C#
also implements genuine rectangular arrays.)

   C# is simple because it is based on C and C++. If you are familiar with C and C++, or
even Java, you will find C# very familiar in many aspects. Statements, expressions, operators,
and other functions are taken directly from C and C++, but improvements make the language
simpler.  

Some of the improvements include eliminating redundancies. Other areas of

improvement include additional syntax changes. For example, C++ has three operators for
working with members:::,., and ->.  

Knowing when to use each of these three symbols can be very confusing in C++. In C#,
these are all replaced with a single symbol--the "dot" operator. For newer programmers, this and
many other features eliminate a lot of confusion.  
Note: If you have used Java and you believe it is simple, you will find C# to be simple. Most
people don't believe that Java is simple. C# is, however, easier than Java and C++.

 C# Will Be Popular 

C# is one of the newest programming languages but it will become a very popular
language for a number of reasons. One of the key reasons is Microsoft and the promises of .NET.

Microsoft wants C# to be popular. Although a company cannot make a product be

popular, it can help. Not long ago, Microsoft suffered the abysmal failure of the Microsoft Bob
operating system. Although Microsoft wanted Bob to be popular, it failed.

C# stands a better chance of success than Microsoft Bob. I don’t know whether people at
Microsoft actually used Bob in their daily jobs. C#, however, is being used by Microsoft. Many
of its products have already had portions rewritten in C#. By using it, Microsoft helps validate
the capabilities of C# to meet the needs of programmers.  

Microsoft .NET is another reason why C# stands a chance to succeed. .NET is a change
in the way the creation and implementation of applications is done. Although virtually any
programming language can be used with .NET, C# is proving to be the language of choice.
Tomorrow's lesson includes a section that explains the high points of .NET.

Why you should choose C# 

The migration to the .NET platform offers many development options. If you are moving
to .NET and you already know about C++ or Java, C# is a logical choice for you. However, if
you are undecided about .NET, you might wonder why you’d want to choose to C# rather than
your COM-based C++.  

Often the decision to move to .NET is based on factors other than learning C#, but C# does offer
many advantages over any COM-based language. Here, we explain why C# is an important
language and why you should consider moving to C#.

 
1. Modernized language 

C# is a modern version of C++. Originally you had the language C, which was widely
used. C++ came about to add object-oriented concept with C, and C++ became the language of
building “real” applications for Windows (according to the C++ developers.) C++ was used for
writing the infrastructure and low-level applications, while Visual Basic developers wrote
business applications.

C# brings the rapid development paradigm of VB to the world of C++ developers, with some
noticeable changes. C# takes advantage of the .NET Framework, which means you have access
to a powerful forms engine, just like VB developers. New data types have been added, such as
the decimal data type for performing financial calculations.

2. Type-safety 

C# is type-safe, which means several things. For example, you cannot use uninitialised
variables. In C++ it is easy to declare a variable and then check its value; whatever was in the
memory address given to that variable would then be shown, and this could inflict confusion on
an application. The C# complier will notify you if you try to use a variable before you have
initialized it to some valid value. 

With C#, you can no longer just walk past the end of an array, as you have been able to do in C
and C++. In C++ you could declare an array of three elements and then happily examine the
fourth element of that array and get the next portion of memory.

3. Object-oriented 

Many people would argue that C++ is object-oriented, C# goes to another level. Even
simple data types can be treated as objects, meaning that an int has methods associated with it.
For example, you can use the ToString method to get a string value for an int, as shown below. 
Int Counter=14;
Console.Write (Counter.ToString ()); 

In addition, literal strings can be treated as objects and support a variety of methods, such as
Trim, ToUpper, ToLower, and many others, as shown here: 

Console.Write ("hello, world".ToUpper ());

4. Simplified syntax 

C++ is an extremely powerful language, it has not typically been considered easy. C#
attempts to simplify the syntax to be more consistent and more logical while also removing some
of the more complex features of C++. For example, C# does away with pointers. As a type-safe
language, C# doesn't allow direct memory manipulation, so pointers are no longer needed in C#. 

Header files have also been removed from C#. The namespace and reference operators,
and -> respectively, have been replaced with a single operator, the period dot (.). 

Perhaps one of the biggest changes is that the int and bool data types are now completely
different. This means that you will finally have an end to the assignment vs. comparison problem
in if statements. In other words, the following code will not even compile under C#: 

int Counter=14;
if (Counter=14) {//do something}

Attempting to compile this code will return an error stating: Cannot implicitly convert type ‘int’
to ‘bool’. 
C# also removes memory management issues from the developer by using .NET’s garbage
collection scheme. Items no longer referenced are marked for garbage collection, and the
Framework can reclaim this memory as needed.

5. XML comments 

C# supports the introduction of XML comments. Far from being just another way to add
comments to code, XML comments can actually turn into your documentation. The comments
are placed into XML format and can then be used as needed to document your code.

 This documentation can include example code, parameters, and references to other
topics. It finally makes sense for a developer to document his or her code, because those
comments can actually become documentation independent of the source code.

6. Not just Microsoft 

C# is not just about Microsoft anymore. Microsoft released C# to ECMA (European

Computer Manufacturer Association) and it has been published as a standard. In addition, the
Mono project is an effort to make an open source version of the .NET Framework (a subset of it
called the CLI) and an open source version of C#, all for Linux.

7. All about components 

Creating components is straightforward, as is referencing those components in code.

Namespaces in C# replace a lot of the headaches from the COM world in which you had to
perform registry lookups and instantiate objects and worry about such things as IUnknown and
IDispatch. Using C#, you simply import a namespace and then begin using the classes in that
component—no registry lookups or COM plumbing required.

8. The power to be unsafe 

Much is made about C#’s type-safety, but if you want to drive without a seatbelt, you are
free to do so. If you really need to use pointers, for example, you can use the unsafe keyword to
mark a block of code. This allows that code to bypass the Framework’s type-safety checking and
means that you can directly manipulate memory. This makes C# incredibly powerful and is one
of the advantages of C# over VB.NET.

9. Cross-language capabilities 

C# has the ability to allow you to interoperate with any other language on the .NET
platform. Much has been said about how you can create a component in one language and inherit
and extend that component in another language, which is something that was difficult, if not
impossible, with COM. 

C# also supports the concept of error handling across different languages. Gone are the
unfriendly HResults; instead, you have access to .NET exceptions, which are consistent across
any .NET language.

10. It might be worth more 

When it comes to creating applications for .NET, the choice between VB.NET and C# is
typically not important. However, it is quite possible that companies are willing to pay more for
C# developers; C++ developers have typically been harder to find than VB developers and have
been better compensated. It's likely there will be more VB.NET developers than C# developers,
so this trend may well continue into the future.
Fundamentals of SQL Server Architecture

Microsoft® SQL Server™ is a Structured Query Language (SQL) based, client/server

relational database. Each of these terms describes a fundamental part of the architecture of SQL
Server.

Database

A database is similar to a data file in that it is a storage place for data. Like a data file, a
database does not present information directly to a user; the user runs an application that
accesses data from the database and presents it to the user in an understandable format.

Database systems are more powerful than data files. The data is more highly organized. In a
well-designed database, there are no duplicate pieces of data that the user or application has to
update at the same time. Related pieces of data are grouped together in a single structure or
record, and relationships can be defined between these structures and records. When working
with data files, an application must be coded to work with the specific structure of each data file.
In contrast, a database contains a catalog that applications use to determine how data is
organized. Generic database applications can use the catalog to present users with data from
different databases dynamically, without being tied to a specific data format. A database
typically has two components: the files holding the physical database and the database
management system (DBMS) software that applications use to access data. The DBMS is
responsible for enforcing the database structure, including:

Maintaining the relationships between data in the database. Ensuring that data is stored correctly,
and that the rules defining data relationships are not violated.

Recovering all data to a point of known consistency in case of system failures.

4.SYSTEM ANALYSIS
 4.1 FEASIBILITY STUDY.

Analysis and evaluation of a proposed project to determine if it is technically feasible, is

feasible within the estimated cost, and will be profitable. Feasibility studies are almost always
conducted where large sums are at stake. Also called feasibility analysis.

The main difficulty with this You have probably noticed that the same web page may
look different depending on what browser you are using and even what version of the browser.
In some cases a web page will not work properly unless you upgrade to the latest version of a
particular browser. Likewise a web page may work fine with an older browser but not a newer
one.

Now consider the company that deploys several browser-based applications. And then
suddenly one of those applications comes out with an upgrade that requires an upgrade to the
current standard company browser. If the company decides to upgrade the browser, there is a
likely consequence that some features of at lease one of the browser-based applications will
not work with the new browser. This leaves the company paralyzed. Do they upgrade the
browser and risk breaking some of the other browser-based applications? Do they allocate
extensive resources to testing the deployed browser-based applications to see if they will still
work with the new browser before deploying it? Or do they stay entrenched on old technology?

Feasibility

Operational Technical Economical

 4.1.1 TECHNICAL FEASIBILITY:

Also the developers of browser-based applications have to make sure their user interface
works with multiple browsers and versions of those browsers. This means it takes more time to
develop and test each new feature, and every time a new version of a browser comes out this
problem becomes worse. It also means that it takes more time and is more expensive
to implement new features in browser-based systems. Consequently, web client systems will
eventually overtake browser-based competitors with either lower price or better functionality or
both.

The time slot could be 100 milliseconds. If job1 takes a total time of 250ms to
complete, the Round-Robin scheduler will suspend the job after 100ms and give other jobs
their time on the CPU. Once the other jobs have had their equal share (100ms
each), job1 will get another allocation of CPU time and the cycle will repeat. This process
continues until the job finishes and needs no more time on the CPU.

Modelling of actual finish time, while feasible, is computationally intensive. The

model needs to be substantially recomputed every time a packet is selected for transmission
and every time a new packet arrives into any queue.

4.1.2 OPERATIONAL FEASIBILITY:

Lastly there is the issue of performance. Web-based applications work by sending data
over the internet or intranet. This mode of communication is relatively slow compared to
network speeds and when the database becomes large there will be performance problems
with many web-based applications. However, it is easy for a web-client application to
 solve performance problems caused by data transmission simply by caching data on the
client computers. Browser based applications can do some caching too, however, the
cached data is generally stored in RAM and lost when the browser is closed. PR-Tracker
on the other hand uses a cached database to improve performance. When PR-Tracker is
closed the cache remains intact. Consequently, there are many actions PR-Tracker Web
Client can do in a split second that may take minutes with a browser-based application or
may even be impossible.

4.1.2 ECONOMICAL FEASIBILITY:

The proposed system won’t be that much economically costly as this application does not require
any hardware part and interfacing with that. Only one web server you need which you will get
very easily and economically.

STEPS IN FEASIBILITY ANALYSIS

FEASIBILITY ANALYSIS INVOLVES EIGHT STEPS

 From a project team and appoint a project leader.

 Prepare system flowcharts.

 Enumerate potential candidate system.

 Describe and identify characteristics of candidate.

 Weight system performance and cost data.

 Select the best candidate system.

 Prepare and report final project directive to management.

 Determine and evaluate performance and cost effectiveness of each candidate system
4.2 DATA FLOW DIAGRAM

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. 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 DFD’S 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.

DFD SYMBOLS:

In the DFD, there are four symbols

1. A square defines a source(originator) or destination of system data

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 DFD’S:

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.
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 DFD’S

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.
4.3 STATE DIAGRAM

 Queue
Input Exit
Running State

Start Time

I/O Interrupt (Time Slice)

Waiting State

Data Dictionary
 Data dictionary consists of description of all the data used in the system. It consists of
logical characteristics of current systems data stores including name, description, aliases,
contents and organization. Data dictionary serves as the basis for identifying database
requirements during system design. Data dictionary is a catalog, a depositary of the elements in
the system.

The data dictionary is used to manage the details in the large system, to communicate a
common meaning for all system elements, to document the future of the system, to locate errors
and omission in the system. Data dictionary contains two types of descriptions for the data
flowing through the system attributes and tables. Attributes are grouped together to make up the
tables. The most fundamental data level is attributes tables are a Set of data items, data related
to one another and that collectively describes a component in the system. The description of the
attributes consists of data names, data descriptions, aliases, and length and data values. The
description of data structures consists sequence relationship, selection relationship, iteration
relationship and operational relationship.

Date Base:
CODING:

Login Page:

<%@ Page Language="C#" AutoEventWireup="true" CodeFile="login.aspx.cs"

Inherits="login" %>

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"

"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head runat="server">
<title></title>
</head>
<body>
<form id="form1" runat="server">
<div>
<table cellpadding="10" border="2" width="100%" bgcolor="#e79ace"
border="2" bordercolor="Maroon">
<tr>
<td align="center" style="font-size: 25px; font-family:
Algerian; color: DarkCyan;
font-weight: bold">
WELCOME TO LOGIN PAGE
</td>
</tr>
</table>
<br />
<br />
<table cellpadding="10" align="right">
<td>
 <asp:Login ID="Login1" runat="server" Height="184px"
Width="216px" BackColor="#EFF3FB"
BorderColor="#B5C7DE" BorderPadding="4"
BorderStyle="Solid" BorderWidth="1px"
Font-Names="Verdana" Font-Size="0.8em" ForeColor="#333333"
CreateUserUrl="~/reg.aspx"
DestinationPageUrl="Home.aspx" CreateUserText="are u new
user?">
<TextBoxStyle Font-Size="0.8em" />
<LoginButtonStyle BackColor="White" BorderColor="#507CD1"
BorderStyle="Solid" BorderWidth="1px"
Font-Names="Verdana" Font-Size="0.8em"
ForeColor="#284E98" />
<InstructionTextStyle Font-Italic="True" ForeColor="Black"
/>
<TitleTextStyle BackColor="#507CD1" Font-Bold="True" Font-
Size="0.9em" ForeColor="White" />
</asp:Login>
</td>
</table>
<table cellpadding="10" width="35%" border="2" cellspacing="5"
bordercolor="#b95c00">
<tr bgcolor="#ffcccc" style="font-size: 20px; color: BlueViolet;
font-weight: bold;">
<td align="center">
ADVANTAGES OF ON-LINE VOTING
</td>
</tr>
<tr style="font-weight: bold;">
<td colspan="5" align="left">
* Increased voter turnout
</td>
</tr>
<tr style="font-weight: bold;">
<td>
* Greater youth involvement
</td>
</tr>
<tr style="font-weight: bold;">
<td>
* Faster voting counts
</td>
</tr>
<tr style="font-weight: bold;">
<td>
* Shorter lines at voting places and fewer assistants
needed
</td>
</tr>
<img src="image/u17398093.jpg" width="50%" />
</table>
</div>
</form>
</body>
</html>
Memebers Info:

<%@ Page Language="C#" AutoEventWireup="true" CodeFile="MemberDetails.aspx.cs"

Inherits="MemberDetails" %>

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"

"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head runat="server">
<title></title>
</head>
<body>
<form id="form1" runat="server">
<div>
<table cellpadding="10" width="100%" border="2" bordercolor="#993333"
bgcolor="#ff99ff"
style="font-size: 25px; font-family: Algerian;">
<tr>
<td align="center">
ON LINE VOTING SOFTWARE
</td>
</tr>
</table>
<table cellpadding="10" style="font-size: 25px; font-family: Algerian;
color: Crimson;
font-weight: bolder;">
<tr>
<td>
WELCOME
</td>
</tr>
</table>
<table cellpadding="10">
<tr>
<td>
<b>Enter Member Name: </b>
</td>
<td>
<asp:TextBox ID="TextBox1" runat="server"></asp:TextBox>
</td>
</tr>
<tr>
<td colspan="2">
<asp:DetailsView ID="DetailsView1" runat="server"
Height="48px" Width="454px"
AutoGenerateRows="False" BackColor="White"
BorderColor="#CC9966"
BorderStyle="None" BorderWidth="1px" CellPadding="4"
DataKeyNames="CandidateID"
DataSourceID="SqlDataSource1">
<FooterStyle BackColor="#FFFFCC" ForeColor="#330099"
/>
<RowStyle BackColor="White" ForeColor="#330099" />
 <PagerStyle BackColor="#FFFFCC" ForeColor="#330099"
HorizontalAlign="Center" />
<Fields>
<asp:BoundField DataField="CandidateID"
HeaderText="CandidateID"
ReadOnly="True" SortExpression="CandidateID"
/>
<asp:BoundField DataField="FName"
HeaderText="FName" SortExpression="FName" />
<asp:BoundField DataField="LName"
HeaderText="LName" SortExpression="LName" />
<asp:BoundField DataField="Gender"
HeaderText="Gender"
SortExpression="Gender" />
<asp:BoundField DataField="DOB" HeaderText="DOB"
SortExpression="DOB" />
<asp:BoundField DataField="VotingNo"
HeaderText="VotingNo"
SortExpression="VotingNo" />
<asp:BoundField DataField="Taluka"
HeaderText="Taluka"
SortExpression="Taluka" />
<asp:BoundField DataField="district"
HeaderText="district"
SortExpression="district" />
<asp:BoundField DataField="Area" HeaderText="Area"
SortExpression="Area" />
<asp:BoundField DataField="AreaCode"
HeaderText="AreaCode"
SortExpression="AreaCode" />
<asp:BoundField DataField="BlockNumber"
HeaderText="BlockNumber"
SortExpression="BlockNumber" />
<asp:BoundField DataField="PartyName"
HeaderText="PartyName"
SortExpression="PartyName" />
</Fields>
<HeaderStyle BackColor="#990000" Font-Bold="True"
ForeColor="#FFFFCC" />
<EditRowStyle BackColor="#FFCC66" Font-Bold="True"
ForeColor="#663399" />
</asp:DetailsView>
<asp:SqlDataSource ID="SqlDataSource1" runat="server"
ConnectionString="<%$
ConnectionStrings:ConnectionString %>"
SelectCommand="SELECT * FROM [CandidateInfo] WHERE
([FName] = @FName)">
<SelectParameters>
<asp:ControlParameter ControlID="TextBox1"
Name="FName" PropertyName="Text"
Type="String" />
</SelectParameters>
</asp:SqlDataSource>
</td>
</tr>
</table>
 <p style="position:absolute; top:20%; left:90%;"> <a
href="Home.aspx"> HOME</a>
</div>
</form>
</body>
</html>

Performance:

<%@ Page Language="C#" AutoEventWireup="true" CodeFile="Performace.aspx.cs"

Inherits="Performace" %>

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"

"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head runat="server">
<title></title>
</head>
<body>
<form id="form1" runat="server">
<div>

<table cellpadding="10">
<tr>
<td>
<font style="font-size: 20px; font-weight: bolder; color:
blue; border-style: double;
border-width: 3px; width: 20%; text-align: center;">
<asp:LoginName ID="LoginName1" runat="server" />
</font>
</td>
</tr>
</table>
<table cellpadding="10" width="100%" style="border-color: Red; border-
width: 3px;
border-style: solid; font-size: 29px;">
<tr>
<td>
PERFORMANC DETAILS
</td>
</tr>
</table>
<p align="right"><a href= "Home.aspx"> HOME</a></p>
<br />
<br />
<br />
<table cellpadding="10" border="1" bordercolor="black"
bgcolor="#ffb0b0">
<tr>
 <td align="left" style="text-align: justify; font-weight:
bold">
<td>
<b>Enter member's ID</b>
</td>
<td>
<asp:TextBox ID="TextBox1" runat="server"></asp:TextBox>
</td>
</tr>
<tr>
<td colspan="2" align="center">
<asp:DetailsView ID="DetailsView1" runat="server"
Height="66px" Width="368px" AutoGenerateRows="False"
BackColor="#CCCCCC" BorderColor="#999999"
BorderStyle="Solid" BorderWidth="3px"
CellPadding="4" CellSpacing="2" DataKeyNames="sno"
DataSourceID="SqlDataSource1"
ForeColor="Black">
<FooterStyle BackColor="#CCCCCC" />
<RowStyle BackColor="White" />
<PagerStyle BackColor="#CCCCCC" ForeColor="Black"
HorizontalAlign="Left" />
<Fields>
<asp:BoundField DataField="sno" HeaderText="sno"
InsertVisible="False" ReadOnly="True"
SortExpression="sno" />
<asp:BoundField DataField="candidateid"
HeaderText="candidateid" SortExpression="candidateid" />
<asp:BoundField DataField="candidatename"
HeaderText="candidatename" SortExpression="candidatename" />
<asp:BoundField DataField="performance"
HeaderText="performance" SortExpression="performance" />
<asp:BoundField DataField="year" HeaderText="year"
SortExpression="year" />
<asp:BoundField DataField="description"
HeaderText="description" SortExpression="description" />
</Fields>
<HeaderStyle BackColor="Black" Font-Bold="True"
ForeColor="White" />
<EditRowStyle BackColor="#000099" Font-Bold="True"
ForeColor="White" />
</asp:DetailsView>
<asp:SqlDataSource ID="SqlDataSource1" runat="server"
ConnectionString="<%$ ConnectionStrings:ConnectionString %>"
DeleteCommand="DELETE FROM [performance] WHERE [sno] =
@sno" InsertCommand="INSERT INTO [performance] ([candidateid],
[candidatename], [performance], [year], [description]) VALUES (@candidateid,
@candidatename, @performance, @year, @description)"
SelectCommand="SELECT * FROM [performance] WHERE
([candidateid] = @candidateid)"
UpdateCommand="UPDATE [performance] SET [candidateid]
= @candidateid, [candidatename] = @candidatename, [performance] =
@performance, [year] = @year, [description] = @description WHERE [sno] =
@sno">
<SelectParameters>
<asp:ControlParameter ControlID="TextBox1"
Name="candidateid" PropertyName="Text"
 Type="Int32" />
</SelectParameters>
<DeleteParameters>
<asp:Parameter Name="sno" Type="Int32" />
</DeleteParameters>
<UpdateParameters>
<asp:Parameter Name="candidateid" Type="Int32" />
<asp:Parameter Name="candidatename" Type="String"
/>
<asp:Parameter Name="performance" Type="String" />
<asp:Parameter DbType="Date" Name="year" />
<asp:Parameter Name="description" Type="String" />
<asp:Parameter Name="sno" Type="Int32" />
</UpdateParameters>
<InsertParameters>
<asp:Parameter Name="candidateid" Type="Int32" />
<asp:Parameter Name="candidatename" Type="String"
/>
<asp:Parameter Name="performance" Type="String" />
<asp:Parameter DbType="Date" Name="year" />
<asp:Parameter Name="description" Type="String" />
</InsertParameters>
</asp:SqlDataSource>
</td>
</tr>
</table>
</div>
</form>
</div>
</body>
</html>

Voting System:

using System;
using System.Collections.Generic;
using System.Linq;
using System.Web;
using System.Web.UI;
using System.Web.UI.WebControls;
using System.Data.SqlClient;
using System.Configuration;
using System.Web.Configuration;

public partial class Voting : System.Web.UI.Page

{
SqlConnection con = new
SqlConnection(WebConfigurationManager.ConnectionStrings["ConnectionString"].Co
nnectionString);
 SqlCommand cmd = new SqlCommand();
protected void Page_Load(object sender, EventArgs e)
{
con.Open();
cmd.Connection = con;
}
protected void Button1_Click(object sender, EventArgs e)
{
cmd.CommandText = "INSERT INTO Voting VALUES ('" + TextBox1.Text +
"','" + TextBox2.Text +
"','" + TextBox4.Text + "')";
cmd.ExecuteNonQuery();
Label1.Text = "VOTING DONE SUCCESSFULLY";
}
}

DESIGN OF SCREEN:

Login Page:
Home Page:
Voting:
Memebers Info:
Citizen Information:
CONCLUSION:

In our application system voting and counting is done with the help of computer. It
saves time, avoid error in counting and there will be no invalid votes. It makes the election
process easy.

BIBLOGRAPHY:

http://www.asp.net
http://www.c-sharp.com

http://www.wikipedia.com