Online Old Car Selling

A PROJECT REPORT ON “ONLINE CAR SELLING PORTAL”

INDEX
1 2 3 Candidate Declaration Acknowledgement Preface

1.Objective of the project
1.1 Introduction 1.2 Problem Description 1.3 Technologies 1.4 Front End 1.5 Back End

2.System Design
2.1 introductions 2.2 Existing system with limitation 2.3 Proposed system with objectives

3.Feasibility study
3.1 Introduction 3.2 Economical 3.3 Technical 3.4 Time

4.System Analysis
4.1 Introduction 4.2 Flow Chart 4.3 DFD’s

5.Hardware and software specification

5.1 Specification 5.2 Requirement

6.System Design
6.1 Introduction 6.2 Database design 6.3 Input/output forms design 6.4 Implementation

7.User Requirements 8.System testing
8.1 Introduction

9.Implementation
9.1 Introduction 9.2 Aspect

10.Cost Estimation
10.1 Introduction

11.Conclusion
11.1 Limitations 11.2 Specification

CANDIDATES DECLARATION
I, here by certify that the work which is being presented in the project entitled “Online Car Selling System”, in partial fulfillment of the requirements, in “Chip InfoTech”, is recorded of our own work and was carried out for a period of one month under the guidance of our Guide Mr._________, ____________________ in Chip InfoTech, Dehradun.

Date:

This is to certify that the above statement made by the candidate is correct to the best of our knowledge.

ACKNOWLEDGEMENT
I would also like to give special thanks to our teacher Mr.___________________ who gave us full support in preparing the project. We are highly indebted to our parents and all others, as without their help and moral support, this project could not be complete.

PLACE: DATE:

PREFACE
BSc IT program is one of the most reputed professional courses in the field of computer science. This course includes both theory and its application contents of curriculum. Project is an integral part of the BSc IT program at Chip InfoTech, Dehradun. Each student is required to undergo Project in his or her fifth semester. As complimentary to that, every student has to prepare and submit a report on project work conducted by the student. The report is in the continuation of the Project working. The topic of the project is ”

Online Car Selling System”.

Name: DINESH CHANDRA PANDEY

INTRODUCTION

INTRODUCTION

 The Project “Online Car Selling System” is a user interactive and delivery based website where online selling of cars is done and confirmations can be generated shortly with getting all the required details regarding each user.  Business done by e-commerce is far more efficient, faster and reliable then traditional commerce.  This method of adoption of doing business via e-commerce is user friendly system which will help user to access the test records easily.  The method of getting reports through e-commerce is far more efficient then traditional commerce.

OBJECTIVES TO BE FULFILLED
Online Car Selling System, is involved in maintenance of cars and booking schedules details and payment details of user logged in, for regular member of the site for booking of cars. By using the software we can have the records of the user for future use and track there order status. Here the software has the details of each section in the Online Car Selling System. Whole of the work described above was performed managerially. It was a great overhead for the person in charge to modify the records according to the changing conditions for e.g. one has to maintain various items purchased by person. Thus need emerged for a software which would provide a quick reliable and timely information to the Online Car Selling System. It was designed in such a way that the generated information of the various sections of the Online Car Selling System. To generate the confirmations and records of the user. As a result of these entire requirements the idea about the project evolved..

Assumptions
 Highly developing Online Car Selling System, following assumptions were kept in mind for the administrator.  The user logged in with ID and Password is valid user.  The user id taken from the user is not received to the database, and is redirected directly to the main via SSL.

System analysis
What does system study actually mean?
It is an orderly grouping of interdependent components liked together according to a plan to achieve specific objectives. Its main characteristics are organization in interaction, interdependence, integration and centered objective.

The study of system concepts has three basic implications:
1. A system must be designed to achieve a predetermined objective. 2. Inter relationships and inter dependents must exists among the components. 3. The objectives of organization as a whole have a higher priority their objectives of its subsystems.

CHARACTERISTICS OF THE SYSTEM
Some characteristics are presents in all systems: organization, inter-dependence, integration and central objectives.

ORGANISATION
This implies structures and other is the arrangement of the components that helps to achieve objectives. It starts with the person on top, leading downwards to the organizational structure.

INTERACTION
It refers to the manner in which each module/components functions with other module components of the system.

CATALOGUING
The booking received are given an identification number, which identifies the books as well as given a unique accession number, items also have a serial number last serial number tells the total price. Accession number is given as per the following scheme<tbooking id><item id> . The details of the orders bought are then entered into the catalogue register the register stores the following information date of acquisition, accession number, booking details, user name , Incase multiple Copies are received each copy is given a unique accession number .

EXOSTOMG SUSTEM
In the existing system all the works is being done manually. All the day to day working of the dispatching is managed by a person and all the record are kept manually in the registers.

Drawbacks in the existing system are:
1. It is time consuming because all the information is kept manually. 2. There is a problem of data redundancy. 3. It requires more manpower.

PROPOSED SYSTEM
In the proposed system all the work will be done using computer. The storage of all the data and information will be centralized, which will remove the problem of data redundancy with the use of computers, the speed of work will increase substantially less manpower will be required and customized report can be generate from time to time depending upon requirement.

RECEIVING AND SENDING OF REPORTS
Whenever a user wants to see the order, it is countersigned. When a member wants to check record of order he has order, he has to get user code and then checks whether the order was submitted or not.

The details include date of conduction and another detail regarding the user and items.

HARDWAWRE REQUIREMENT

The decision process to acquire computer hardware must be handled in the same way. As any other business decision. The variety of size and type of computing resources. Available puts a burden on the analyst who must select suitable hardware. Today selecting a System is a serious and time-consuming work. The time spent on the selection process is function of application and whether the system is a basic microcomputer or mainframe.

Minimum requirement:
1. Pentium 2 MHz 2.512MB RAM 3.2 GB hard disk 4. VGA display card

INTRODUCTION
The main purpose of this project to develop software to computerize all the work has done which the concerned administrator is done manually. Previously all the work of allotment of the item ids, keeping the record of all things is been manually. So it is too difficult to maintain all records, generate reports, and fetch information while using manual system.

PROBLEM DESCRIPTION
Manual system suffers from great limitations like time wastage, errors due to work, complications in maintaining and analyzing the records. To start these problems we have designed a computerize system for maintaining the records. That will provide different kind of facilities like1. The main aim is automation of orders. 2. To make the system independent. 3. To make the system flexible. 4. Records are easy to analyze, search, view etc. 5. The system will able to generate Reports.

TECHNOLOGIES

FRONTEND
• ASP DOT NET WITH C#

BACKEND • SQLSERVER 2008 • Internet Information Service

SYSTEM STUDY

EXISTING SYSTEM WITH LIMITATIONS

The existing system is manual. All the records kept a paper & prepared manually. The record kept in registers & files, written manually & different types of records are stored in different files.

Limitations of existing system-: 1. The existing system is manual so it is very difficult to maintain the records properly. 2. In the manual system it is very difficult to analyze the records. 3. Records are not to be maintained for a long time. 4. Problem of record losing, inaccuracy are there. 5. Searching of any particular records take very long time. 6. Report generation and computerized printouts is also a big problem.

PROPOSED SYSTEM WITH OBJECTIVE
Manual system suffers from great limitations like time wastage. Errors due to work complications in maintaining & analyzing the records. To sort these problems we have designed a computerized system for maintaining the records for the record keeper of the concern organization.

• Provide a fully computerized booking system. • Dynamic search engine. • Complete day-to-day booking status. • Complete day-to-day registered record.

FEASIBILITY STUDY

INTRODUCTION
Feasibility study is the test of proposal according to its workability impact on the organization. Ability meets the user needs and effective use of the resources. It depends on the initial investigation. It focuses on the three major questions. 1. What are the user’s demonstrable needs and how does a candidate system meet them? 2. What resources are available for given candidate system? Is the problem worth solving? 3. What are likely impacts of the candidate system? Each of these questions must be answered carefully. It’s main objective is not to solve the problem but to acquire a sense of it’s scope. During the study, the problem definition is crystallize and aspects of the problem to be included in the system are determined. The result of the feasibility study is a formal proposal which summaries what is known and what is going to be done. it consists of the following-: STATEMENT OF THE PROBLEM-: A carefully worded statement of the problem that leads to analysis. Summary of problem and recommendation-: A list of major findings and recommendations of the study. It is ideal for the users require quick access to the analysis of the system understudy. Details of findings-: An outline of the method and procedure undertaken by existing system followed by coverage of the objectives and procedure of the new system. Recommendation and conclusion-: Specific recommendation regarding the candidate system including personnel assignment cost and target dates. This is a crucial decision point in life

cycle, Many projects die here whereas the more promising ones continue through implementation. So to make the best system we also did a feasibility study after collecting all the accurate data, which we known a new system.

The main objective of doing feasibility study is-: • To identify the deficiencies of the current system. • To determine the objective of the purposed system. • To acquire a sense of the system • To identify the responsible user

• To determine whether it is feasible to develop the new system.

We analyze the feasibility to the purposed system through the three types of feasibility studies, which are as below. • Economical feasibility • Technical feasibility • Time feasibility Economical feasibility-: Economical feasibility is the most frequently used method for evaluating the effectiveness of the proposed system. More commonly known as cost/benefit analysis, the procedure is to determine the benefits and saving that are expected from the proposed system. According to the concept of economic feasibility our project is economically feasible for the project development of software for ”ONLINE CAR SELLING SYSTEM”, which will implement this package.

Technical feasibility-: Technical feasibility centers on the system such as hardware, software etc. and to what extent it can support the proposed package. It also needs to be ensuring that the requesting hardware for operating system. Time feasibility-: Time feasibility involves the duration about the project has to complete. Since the existing website take very less time to achieve every task, so to have the time it must be made a system. The existing system was manual form, so to see the dispatch, status report, receiving and sending etc, is very time consuming. The person requires very less time. Steps in feasibility study-: • Feasibility involves the following steps-: • Form a project team and appoint a project leader. • Prepare system flow charts. • Enumerate potential system. • Describe and identify characteristics of system. • Determine and evaluate performance and cost effectiveness of system.

• Select the best system. • Weight system performance and cost data.

SYSTEM ANALYSIS

INTRODUCTION
Now comes the most important phase of the project development, system analysis. We know the accuracy of a system depends on how well the requirement is defined by the user. Analysis also, is responsible for the accuracy of system design. So if we want our design to be a good one the analysis should be of good quality.

Analysis focuses on the study of existing system, data collection and the data flow. There are some tools by which analysis is done. Few of the tools are DFD, Flow chart, ER Diagram, Structure English, data dictionaries, Decision tables, etc.

We have used only two tools to analyze the data flow of the existing system, these three tools are DFD, Flow chart, ER Diagram. A brief explanation on both the tools are given in the next section of this section

1. Flow Chart 2. DFD

3. Entity Relationship Diagram

FLOW CHARTS
A flow chart is a pictorial representation of an algorithm that uses box of different types of instructions. The actual instructions are return within these boxes using clear and concise statement. These boxes are connected by line having arrow marks to indicate the flow of information i.e. the exact sequence in which the instructions are being executed. The symbols and their functions are discussed below: TERMINALS:-The terminal symbol as the name implies is used to indicate the beginning
(start), ending (stop) in the program.

INPUT/OUTPUT:-The input/output symbol is used to denote any function of any
input/output device in the program.

PROCESSING:-A processing symbol is used in a flow chart to represent the arithmetic and data movement functions.

Data Flow Diagram

DFD (DATA FLOW DIAGRAM)

A model is an expensive facsimile of a system model may either be abstract paper model or a working model.(abstract mode print) abstract mode tools are required to develop model new system has to be developed according to the recruitment off its user. It is advisable to build a model of a system capture and requirement of the user. Iteration may be performing on the model till user approves it.

Data Flow Diagram:-

The following aspect of his system can be modeled using a data flow diagram (DFD)

• What function must be system performing? • What are the interactions between these function? • What are transformations carried out by these functions? What are transformed? • What output by function? • From where does the system receive the inputs? • Where does the system deliver its output?

It may be observed that D.F.D. emphasis the function of a system along with the transformation performed by these functions.

D.F.D has two basic type of components: • Process • Data flow

1. Process

Processes are also called by function and are show circle or bubble in the diagram. Function performs input to output.

2. Data flow ___________________

Data flows are shown by curved direction arrow. A data flow presents the data that flows from one system to another.

DATA FLOW DIAGRAM: LEVEL 0:
BOOKING

User

ONLINE CAR BOOKING SYSTEM

Displ ay
CANCELLATI ON

LEVEL 1(a):

User

BOOKING

Accept the details

Reserve in the file

STOCK DATABASE

LEVEL 1(b):

User

Cancellat ion

Accept the details

Cancel in the file

STOCK DATABASE

LEVEL 2:

Use r

Displ ay

READ ORDER DETAILS

Customer database

Display in tabular form

HARDWARE SPECIFICATION

Hardware requirements
Hardware Requirements Processor RAM Monitor Keyboard Mouse : : : Pentium IV 2GHz and Above 2GB RAM 15” Color Monitor

SOFTWARE SPECIFICATIONS

Software Requirements

Operating System. Developing Tool Database Browser

: : : :

Windows XP DOT NET (C#) SQL SERVER Internet Explorer

ABOUT ASP.NET INTRODUCTION ASP.NET is a web application framework developed and marketed by Microsoft to allow programmers to build dynamic web sites, web applications and web services. It was first released in January 2002 with version 1.0 of the .NET Framework, and is the successor to Microsoft's Active Server Pages (ASP) technology. ASP.NET is built on the Common Language Runtime (CLR), allowing programmers to write ASP.NET code using any supported .NET language. The ASP.NET SOAP extension framework allows ASP.NET components to process SOAP messages. History After the release of Internet Information Services 4.0 in 1997, Microsoft began researching possibilities for a new web application model that would solve common complaints about ASP, especially with regard to separation of presentation and content and being able to write "clean" code. Mark Anders, a manager on the IIS team, and Scott Guthrie, who had joined Microsoft in 1997 after graduating from Duke University, were tasked with determining what that model would look like. The initial design was developed over the course of two months by Anders and Guthrie, and Guthrie coded the initial prototypes during the Christmas holidays in 1997. The initial prototype was called "XSP"; Guthrie explained in a 2007 interview that, "People would always ask what the X stood for. At the time it really didn't stand for anything. XML started with that; XSLT started with that. Everything cool seemed to start with an X, so that's what we originally named it." The initial prototype of XSP was done using Java, but it was soon decided to build the new platform on top of the Common Language Runtime (CLR), as it offered an object-oriented programming environment, garbage collection and other features that were seen as desirable features that Microsoft's Component Object Model platform didn't support. Guthrie described this decision as a "huge risk", as the success of their new web development platform would be tied to the success of the CLR, which, like XSP, was still in the early stages of development, so much so that the XSP team was the first team at Microsoft to target the CLR. With the move to the Common Language Runtime, XSP was re-implemented in C# (known internally as "Project Cool" but kept secret from the public), and the name changed to ASP+, as by this point the new platform was seen as being the successor to Active Server Pages, and the intention was to provide an easy migration path for ASP developers. Mark Anders first demonstrated ASP+ at the ASP Connections conference in Phoenix, Arizona on May 2, 2000. Demonstrations to the wide public and initial beta release of ASP+ (and the rest of the .NET Framework) came at the 2000 Professional Developers Conference on July 11, 2000 in Orlando, Florida. During Bill Gates' keynote presentation, Fujitsu demonstrated ASP+ being used in conjunction with COBOL,[5] and support for a variety of other languages was

announced, including Microsoft's new Visual Basic .NET and C# languages, as well as Python and Perl support by way of interoperability tools created by Active State. Once the ".NET" branding was decided on in the second half of 2000, it was decided to rename ASP+ to ASP.NET. Mark Anders explained on an appearance on The MSDN Show that year that, "The .NET initiative is really about a number of factors, it's about delivering software as a service, it's about XML and web services and really enhancing the Internet in terms of what it can do ... we really wanted to bring its name more in line with the rest of the platform pieces that make up the .NET framework." After four years of development, and a series of beta releases in 2000 and 2001, ASP.NET 1.0 was released on January 5, 2002 as part of version 1.0 of the .NET Framework. Even prior to the release, dozens of books had been written about ASP.NET, [7] and Microsoft promoted it heavily as part of their platform for web services. Guthrie became the product unit manager for ASP.NET, and development continued apace, with version 1.1 being released on April 24, 2003 as a part of Windows Server 2003. This release focused on improving ASP.NET's support for mobiledevices. Characteristics Pages .NET pages, known officially as "web forms", are the main building block for application development.[8] Web forms are contained in files with an ".aspx" extension; these files typically contain static (X)HTML markup, as well as markup defining server-side Web Controls and User Controls where the developers place all the required static and dynamic content for the web page. Additionally, dynamic code which runs on the server can be placed in a page within a block <% -- dynamic code -- %> which is similar to other web development technologies such as PHP, JSP, and ASP, but this practice is generally discouraged except for the purposes of data binding since it requires more calls when rendering the page. Note that this sample uses code "inline", as opposed to code-behind. <%@ Page Language="C#" %> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <script runat="server"> protected void Page_Load(object sender, EventArgs e) { Label1.Text = DateTime.Now.ToLongTimeString(); }

</script> <html xmlns="http://www.w3.org/1999/xhtml"> <head runat="server"> <title>Sample page</title> </head> <body> <form id="form1" runat="server"> <div> The current time is: <asp:Label runat="server" id="Label1" /> </div> </form> </body> </html> Code-behind model Microsoft recommends dealing with dynamic program code by using the code-behind model, which places this code in a separate file or in a specially designated script tag. Code-behind files typically have names like MyPage.aspx.cs or MyPage.aspx.vb while the page file is MyPage.aspx (same filename as the page file (ASPX), but with the final extension denoting the page language). This practice is automatic in Microsoft Visual Studio and other IDEs. When using this style of programming, the developer writes code to respond to different events, like the page being loaded, or a control being clicked, rather than a procedural walk through the document. ASP.NET's code-behind model marks a departure from Classic ASP in that it encourages developers to build applications with separation of presentation and content in mind. In theory, this would allow a web designer, for example, to focus on the design markup with less potential for disturbing the programming code that drives it. This is similar to the separation of the controller from the view in model-view-controller frameworks. Example <%@ Page Language="C#" Inherits="Website.SampleCodeBehind" AutoEventWireup="true" %> CodeFile="SampleCodeBehind.aspx.cs"

The above tag is placed at the beginning of the ASPX file. The CodeFile property of the @ Page directive specifies the file (.cs or .vb) acting as the code-behind while the Inherits property specifies the Class the Page derives from. In this example, the @ Page directive is included in SampleCodeBehind.aspx, then SampleCodeBehind.aspx.cs acts as the code-behind for this page:

using System; namespace Website { public partial class SampleCodeBehind : System.Web.UI.Page { protected void Page_Load(object sender, EventArgs e) { Response.Write("Hello, world"); } } } In this case, the Page_Load() method is called every time the ASPX page is requested. The programmer can implement event handlers at several stages of the page execution process to perform processing.

User controls An event bubbling mechanism provides the ability to pass an event fired by a user control up to its containing page. Custom Controls Programmers can also build Custom controls for ASP.NET applications. Unlike User controls, these controls don't have an ASCX markup-file, having all their code compiled into a DLL-file. Such Custom controls can be used across multiple web-applications and Visual Studio projects (which is not allowed with User controls). By using a Register directive, the control is loaded from the DLL. Rendering technique ASP.NET uses a visited composites rendering technique. During compilation, the template (.aspx) file is compiled into initialization code which builds a control tree (the composite) representing the original template. Literal text goes into instances of the Literal control class, and server controls are represented by instances of a specific control class. The initialization code is combined with user-written code (usually by the assembly of multiple partial classes) and results in a class specific for the page. The page doubles as the root of the control tree. Actual requests for the page are processed through a number of steps. First, during the initialization steps, an instance of the page class is created and the initialization code is executed. This produces the initial control tree which is now typically manipulated by the methods of the page in the following steps. As each node in the tree is a control represented as

an instance of a class, the code may change the tree structure as well as manipulate the properties/methods of the individual nodes. Finally, during the rendering step a visitor is used to visit every node in the tree, asking each node to render itself using the methods of the visitor. The resulting HTML output is sent to the client. After the request has been processed, the instance of the page class is discarded and with it the entire control tree. This is usually a source of confusion among novice ASP.NET programmers that rely on class instance members that are lost with every page request/response cycle. State management ASP.NET applications are hosted by a web server and are accessed using the stateless HTTP protocol. As such, if an application uses stateful interaction, it has to implement state management on its own. ASP.NET provides various functions for state management. Conceptually, Microsoft treats "state" as GUI state; problems may arise if an application needs to keep track of "data state", for example, a finite state machine which may be in a transient state between requests (lazy evaluation) or which takes a long time to initialize. Application state Application state is held by a collection of shared user-defined variables. These are set and initialized when the Application_OnStart event fires on the loading of the first instance of the applications and are available till the last instance exits. Application state variables are accessed using the Applications collection, which provides a wrapper for the application state variables. Application state variables are identified by name. Session state Server-side session state is held by a collection of user-defined session variables, which are persisted during a user session. These variables, accessed using the Session collection, are unique to each session instance. Then variables can be set to be automatically destroyed after a defined time of inactivity, even if the session does not end. Client-side user session is maintained by either a cookie or by encoding the session ID in the URL itself. ASP.NET supports three modes of persistence for session variables: In Process Mode

When using In Process Mode, the session variables are maintained within the ASP.NET process. This is the fastest way; however, in this mode the variables are destroyed when the ASP.NET process is recycled or shut down.

ASPState Mode

In this mode, ASP.NET runs a separate Windows service that maintains the state variables. As state management happens outside the ASP.NET process and .NET Remoting must be utilized by the ASP.NET engine to access the data there is a negative impact on performance compared to the In Process mode. This mode allows an ASP.NET application to be load-balanced and scaled across multiple servers and because the state management service runs independently of ASP.NET, the session variables can persist across ASP.NET process shutdowns. However, since session state server runs as a single instance it is still a single point of failure so far as session state is concerned. The sessionstate service cannot be load balanced and there are restrictions on types that can be stored in a session variable. , In this mode, the state variables are stored in a database allowing session variables to be persisted across ASP.NET process shutdowns. The main advantage of this mode is that it allows the application to balance load on a server cluster, sharing sessions between servers. This is the slowest method of session state management in ASP.NET. View state View state refers to the page-level state management mechanism, utilized by the HTML pages emitted by ASP.NET applications to maintain the state of the web form controls and widgets. The state of the controls is encoded and sent to the server at every form submission in a hidden field known as __VIEWSTATE. The server sends back the variable so that when the page is re-rendered, the controls render at their last state. At the server side, the application may change the viewstate, if the processing requires a change of state of any control. The states of individual controls are decoded at the server, and are available for use in ASP.NET pages using the ViewState collection. The main use for this is to preserve form information across postbacks. View state is turned on by default and normally serializes the data in every control on the page regardless of whether it is actually used during a postback. This behavior can (and should be) modified, however, as View state can be disabled on a per-control, per-page, or server-wide basis. Developers need to be wary of storing sensitive or private information in the View state of a page or control, as the base64 string containing the view state data can easily be deserialized. By default, View state does not encrypt the __VIEWSTATE value. Encryption can be enabled on a server-wide (and server-specific) basis, allowing for a certain level of security to be maintained.

Server-side caching ASP.NET offers a "Cache" object that is shared across the application and can also be used to store various objects. The "Cache" object holds the data only for a specified amount of time and is automatically cleaned after the session time-limit elapses. Other Other means of state management that are supported by ASP.NET are cookies, caching, and using the query string. Template engine When first released, ASP.NET lacked a template engine. Because the .NET framework is object-oriented and allows for inheritance, many developers would define a new base class that inherits from "System.Web.UI.Page", write methods here that render HTML, and then make the pages in their application inherit from this new class. While this allows for common elements to be reused across a site, it adds complexity and mixes source code with markup. Furthermore, this method can only be visually tested by running the application - not while designing it. Other developers have used include files and other tricks to avoid having to implement the same navigation and other elements in every page. ASP.NET 2.0 introduced the concept of "master pages", which allow for template-based page development. A web application can have one or more master pages, which, beginning with ASP.NET 3.5, can be nested. Master templates have place-holder controls, called ContentPlaceHolders to denote where the dynamic content goes, as well as HTML and JavaScript shared across child pages. Child pages use those ContentPlaceHolder controls, which must be mapped to the place-holder of the master page that the content page is populating. The rest of the page is defined by the shared parts of the master page, much like a mail merge in a word processor. All markup and server controls in the content page must be placed within the ContentPlaceHolder control. When a request is made for a content page, ASP.NET merges the output of the content page with the output of the master page, and sends the output to the user. The master page remains fully accessible to the content page. This means that the content page may still manipulate headers, change title, configure caching etc. If the master page exposes public properties or methods (e.g. for setting copyright notices) the content page can use these as well. Other files Other file extensions associated with different versions of ASP.NET include:

Extension

Required Description version

asax ascx ashx asmx

1.0 1.0 1.0 1.0

Global.asax, used for application-level logic [14] Web UserControls: custom controls to be placed onto web pages. custom HTTP handlers. web service pages. From version 2.0 a Code behind page of an asmx file is placed into the app_code folder. when enabled in web.config requesting trace.axd outputs applicationlevel tracing. Also used for the special webresource.axd handler which allows control/component developers to package a component/control complete with images, script, css etc. for deployment in a single file (an 'assembly') browser capabilities files stored in XML format; introduced in version 2.0. ASP.NET 2 includes many of these by default, to support common web browsers. These specify which browsers have which capabilities, so that ASP.NET 2 can automatically customize and optimize its output accordingly. Special .browser files are available for free download to handle, for instance, the W3C Validator, so that it properly shows standards-compliant pages as being standards-compliant. Replaces the harder-to-use BrowserCaps section that was in machine.config and could be overridden in web.config in ASP.NET 1.x. web.config is the only file in a specific Web application to use this extension by default (machine.config similarly affects the entire Web server and all applications on it), however ASP.NET provides facilities to create and consume other config files. These are stored in XML format. Code files (cs indicates C#, vb indicates Visual Basic). Code behind files (see above) predominantly have the extension ".aspx.cs" or ".aspx.vb" for the two most common languages. Other code files (often containing common "library" classes) can also exist in the web folders with the cs/vb extension. In ASP.NET 2 these should be placed inside the App_Code folder where they are dynamically compiled and available to the whole application. LINQ to SQL data classes file master page file. Default file name is Master1.master resource files for internationalization and localization. Resource files can

axd

1.0

browser

2.0

config

1.0

cs/vb

1.0

dbml master resx

3.5 2.0 1.0

be global (e.g. messages) or "local" which means specific for a single aspx or ascx file. sitemap skin svc edmx 2.0 2.0 3.0 3.5 sitemap configuration files. Default file name is web.sitemap theme skin files. Windows Communication Foundation service file ADO.NET Entity Framework model

Directory structure In general, the ASP.NET directory structure can be determined by the developer's preferences. Apart from a few reserved directory names, the site can span any number of directories. The structure is typically reflected directly in the urls. Although ASP.NET provides means for intercepting the request at any point during processing, the developer is not forced to funnel requests through a central application or front controller. The special directory names (from ASP.NET 2.0 on) are]: App_Browsers

holds site-specific browser definition files.

App_Code

This is the "raw code" directory. The ASP.NET server automatically compiles files (and subdirectories) in this folder into an assembly which is accessible in the code of every page of the site. App_Code will typically be used for data access abstraction code, model code and business code. Also any site-specific http handlers and modules and web service implementation go in this directory. As an alternative to using App_Code the developer may opt to provide a separate assembly with precompiled code.

App_Data

default directory for databases, such as Access mdb files and SQL Server mdf files. This directory is usually the only one with write access for the application.

App_LocalResources

Contains localized resource files for individual pages of the site. E.g. a file called CheckOut.aspx.fr-FR.resx holds localized resources for the French version of the CheckOut.aspx page. When the UI culture is set to french, ASP.NET will automatically find and use this file for localization.

App_GlobalResources

Holds resx files with localized resources available to every page of the site. This is where the ASP.NET developer will typically store localized messages etc. which are used on more than one page.

App_Themes

holds alternative themes of the site.

App_WebReferences

holds discovery files and WSDL files for references to web services to be consumed in the site. Bin Contains compiled code (.dll files) for controls, components, or other code that you want to reference in your application. Any classes represented by code in the Bin folder are automatically referenced in your application.

Performance ASP.NET aims for performance benefits over other script-based technologies (including Classic ASP) by compiling the server-side code to one or more DLL files on the web server. This compilation happens automatically the first time a page is requested (which means the developer need not perform a separate compilation step for pages). This feature provides the ease of development offered by scripting languages with the performance benefits of a compiled binary. However, the compilation might cause a noticeable but short delay to the web user when the newly-edited page is first requested from the web server, but won't again unless the page requested is updated further. The ASPX and other resource files are placed in a virtual host on an Internet Information Services server (or other compatible ASP.NET servers; see Other Implementations, below). The first time a client requests a page, the .NET framework parses and compiles the file(s) into a .NET assembly and sends the response; subsequent requests are served from the DLL files. By default ASP.NET will compile the entire site in batches of 1000 files upon first request. If the compilation delay is causing problems, the batch size or the compilation strategy may be tweaked. Developers can also choose to pre-compile their "codebehind" files before deployment, using MS Visual Studio, eliminating the need for just-in-time compilation in a production environment. This also eliminates the need of having the source code on the web server. Extension Microsoft has released some extension frameworks that plug into ASP.NET and extend its functionality. Some of them are: ASP.NET AJAX

An extension with both client-side as well as server-side components for writing ASP.NET pages that incorporate AJAX functionality.

ASP.NET MVC Framework

An extension to author ASP.NET pages using the MVC architecture.

ASP.NET compared with ASP classic ASP.NET simplifies developers' transition from Windows application development to web development by offering the ability to build pages composed of controls similar to a Windows user interface. A web control, such as a button or label, functions in very much the same way as its Windows counterpart: code can assign its properties and respond to its events. Controls know how to render themselves: whereas Windows controls draw themselves to the screen, web controls produce segments of HTML and JavaScript which form part of the resulting page sent to the end-user's browser. ASP.NET encourages the programmer to develop applications using an event-driven GUI model, rather than in conventional web-scripting environments like ASP and PHP. The framework combines existing technologies such as JavaScript with internal components like "ViewState" to bring persistent (inter-request) state to the inherently stateless web environment. Other differences compared to ASP classic are:
• •

Compiled code means applications run faster with more design-time errors trapped at the development stage. Significantly improved run-time error handling, making use of exception handling using try-catch blocks. Similar metaphors to Microsoft Windows applications such as controls and events. An extensive set of controls and class libraries allows the rapid building of applications, plus user-defined controls allow commonly-used web template, such as menus. Layout of these controls on a page is easier because most of it can be done visually in most editors. ASP.NET leverages the multi-language capabilities of the .NET Common Language Runtime, allowing web pages to be coded in VB.NET, C#, J#, Delphi.NET, Chrome etc. Ability to cache the whole page or just parts of it to improve performance. Ability to use the code-behind development model to separate business logic from presentation. Ability to use true object-oriented design for programming both page and controls If an ASP.NET application leaks memory, the ASP.NET runtime unloads the AppDomain hosting the erring application and reloads the application in a new AppDomain. Session state in ASP.NET can be saved in a Microsoft SQL Server database or in a separate process running on the same machine as the web server or on a different machine. That way session values are not lost when the web server is reset or the ASP.NET worker process is recycled.

• •

•

• •

• •

•

•

Versions of ASP.NET prior to 2.0 were criticized for their lack of standards compliance. The generated HTML and JavaScript sent to the client browser would not always validate against W3C/ECMA standards. In addition, the framework's browser detection feature sometimes incorrectly identified web browsers other than Microsoft's own Internet Explorer as "downlevel" and returned HTML/JavaScript to these clients with some of the features removed, or sometimes crippled or broken. However, in version 2.0, all controls generate valid HTML 4.0, XHTML 1.0 (the default) or XHTML 1.1 output, depending on the site configuration. Detection of standards-compliant web browsers is more robust and support for Cascading Style Sheets is more extensive. Web Server Controls: these are controls introduced by ASP.NET for providing the UI for the web form. These controls are state managed controls and are WYSIWYG controls.

•

Criticism On IIS 6.0 and lower, pages written using different versions of the ASP framework cannot share Session State without the use of third-party libraries. This criticism does not apply to ASP.NET and ASP applications running side by side on IIS 7. With IIS 7, modules may be run in an integrated pipeline that allows modules written in any language to be executed for any request. ASP.NET 2.0 Web Forms produces markup that passes W3C validation, but it is debatable as to whether this increases accessibility, one of the benefits of a semantic XHTML page + CSS representation. Several controls, such as the Login controls and the Wizard control, use HTML tables for layout by default. Microsoft has solved this problem by releasing the ASP.NET 2.0 CSS Control Adapters, a free add-on that produces compliant accessible XHTML+CSS markup, as well as adding a property to the login control in ASP.NET 4.0 which enables it to run in div mode instead of table mode. A few of the ASP.NET Web Forms features, such as repositioning of pages and alter browser history, are available only in Internet Explorer. Microsoft positions Web Services and consequently IIS/ASP.NET as their primary application server solution. Big conceptual shortcomings become apparent when implementing complex business applications that use "out-of-the-box" Microsoft approach: ASP.NET lacks solid state management, developers need to hand-code custom state-handling modules that must store state in some external process because ASP.NET worker process restarts automatically. This can be illustrated with a simple example: imagine an ASP.NET website that relies on a server component that must preserve its state and that state was achieved as the result of complex algorithms - e.g. super-imposing route geometry over a map. A route took many CPU cycles to compute and multiple subsequent client requests shall "see" the result while rendering map tiles. Another example: when state is encapsulated in a legacy COM object that can not be marshaled between web/session state servers - the only possible mode is "in-proc" which is unreliable because of application restarts.

Development tools Several available software packages exist for developing ASP.NET applications: Product ASP.NET Intellisense Generator Developer BlueVision LLC Licensing Free Free and Commercial Commercial Notes

Microsoft Visual Microsoft Studio CodeGear Delphi Macromedia HomeSite Embarcadero Technologies

Adobe Systems Commercial Commercial

Microsoft Microsoft Expression Web Microsoft SharePoint Designer MonoDevelop Microsoft

Free

Novell and the Free Mono Source community ICSharpCode Team Free Source

Open

SharpDevelop Eiffel ASP.NET for

Open

Free Open Eiffel Software Source and Commercial Supports important ASP.NET 2.0 features, and produces very inefficient code for ASP.NET 1.x: also, code generation and ASP.NET features support through version 8.0.1 was changed very little from version MX if at all. Version 8.0.2 does improve security against SQL injection attacks

Macromedia Dreamweaver

Adobe Systems Commercial

Frameworks It is not essential to use the standard webforms development model when developing with ASP.NET. Noteworthy frameworks designed for the platform include:
• •

Base One Foundation Component Library (BFC) is a RAD framework for building .NET database and distributed computing applications. DotNetNuke is an open source solution which comprises both a web application framework and a content management system which allows for advanced extensibility through modules, skins, and providers. Castle Monorail, an open-source MVC framework with an execution model similar to Ruby on Rails. The framework is commonly used with Castle ActiveRecord, an ORM layer built on NHibernate. Spring.NET, a port of the Spring framework for Java. Skaffold.NET, A simple framework for .NET applications, used in enterprise applications.

•

• •

Other implementations The Mono Project supports ASP.NET 1.1 and most of ASP.NET 2.0. [18] ASP.Net can be run with mono using one of three options: Apache hosting using the mod_mono module, FastCGI hosting, and XSP.

DATABASE CONNECTIVITY WITH ADO.NET

INTRODUCTION Most applications need data access at one point of time making it a crucial component when working with applications. Data access is making the application interact with a database, where all the data is stored. Different applications have different requirements for database access. VB .NET uses ADO .NET (Active X Data Object) as it's data access and manipulation protocol which also enables us to work with data on the Internet. Let's take a look why ADO .NET came into picture replacing ADO. Evolution of ADO.NET The first data access model, DAO (data access model) was created for local databases with the built-in Jet engine which had performance and functionality issues. Next came RDO (Remote Data Object) and ADO (Active Data Object) which were designed for Client Server architectures but, soon ADO took over RDO. ADO was a good architecture but as the language changes so is the technology. With ADO, all the data is contained in a recordset object which had problems when implemented on the network and penetrating firewalls. ADO was a connected data access, which means that when a connection to the database is established the connection remains open until the application is closed. Leaving the connection open for the lifetime of the application raises concerns about database security and network traffic. Also, as databases are becoming increasingly important and as they are serving more people, a connected data access model makes us think about its productivity. For example, an application with connected data access may do well when connected to two clients, the same may do poorly when connected to 10 and might be unusable when connected to 100 or more. Also, open database connections use system resources to a maximum extent making the system performance less effective. Why ADO.NET? To cope up with some of the problems mentioned above, ADO .NET came into existence. ADO .NET addresses the above mentioned problems by maintaining a disconnected database access model which means, when an application interacts with the database, the connection is opened to serve the request of the application and is closed as soon as the request is completed. Likewise, if a database is Updated, the connection is opened long enough to complete the Update operation and is closed. By keeping connections open for only a minimum period of time, ADO .NET conserves system resources and provides maximum security for databases and also has less impact on system performance. Also, ADO .NET when interacting with the database uses XML and converts all the data into XML format for database related operations making them more efficient.

The ADO.NET Data Architecture Data Access in ADO.NET relies on two components: DataSet and Data Provider. DataSet The dataset is a disconnected, in-memory representation of data. It can be considered as a local copy of the relevant portions of the database. The DataSet is persisted in memory and the data in it can be manipulated and updated independent of the database. When the use of this DataSet is finished, changes can be made back to the central database for updating. The data in DataSet can be loaded from any valid data source like Microsoft SQL server database, an Oracle database or from a Microsoft Access database. Data Provider The Data Provider is responsible for providing and maintaining the connection to the database. A DataProvider is a set of related components that work together to provide data in an efficient and performance driven manner. The .NET Framework currently comes with two DataProviders: the SQL Data Provider which is designed only to work with Microsoft's SQL Server 7.0 or later and the OleDb DataProvider which allows us to connect to other types of databases like Access and Oracle. Each DataProvider consists of the following component classes:  The Connection object which provides a connection to the database  The Command object which is used to execute a command  The DataReader object which provides a forward-only, read only, connected recordset  The DataAdapter object which populates a disconnected DataSet with data and performs update Data access with ADO.NET can be summarized as follows: A connection object establishes the connection for the application with the database. The command object provides direct execution of the command to the database. If the command returns more than a single value, the command object returns a DataReader to provide the data. Alternatively, the DataAdapter can be used to fill the Dataset object. The database can be updated using the command object or the DataAdapter.

Component classes that make up the Data Providers The Connection Object The Connection object creates the connection to the database. Microsoft Visual Studio .NET provides two types of Connection classes: the SqlConnection object, which is designed specifically to connect to Microsoft SQL Server 7.0 or later, and the OleDbConnection object, which can provide connections to a wide range of database types like Microsoft Access and Oracle. The Connection object contains all of the information required to open a connection to the database. The Command Object The Command object is represented by two corresponding classes: SqlCommand and OleDbCommand. Command objects are used to execute commands to a database across a data connection. The Command objects can be used to execute stored procedures on the database,

SQL commands, or return complete tables directly. Command objects provide three methods that are used to execute commands on the database:  ExecuteNonQuery: Executes commands that have no return values such as INSERT, UPDATE or DELETE  ExecuteScalar: Returns a single value from a database query  ExecuteReader: Returns a result set by way of a DataReader object The DataReader Object The DataReader object provides a forward-only, read-only, connected stream recordset from a database. Unlike other components of the Data Provider, DataReader objects cannot be directly instantiated. Rather, the DataReader is returned as the result of the Command object's ExecuteReader method. The SqlCommand.ExecuteReader method returns a SqlDataReader object, and the OleDbCommand.ExecuteReader method returns an OleDbDataReader object. The DataReader can provide rows of data directly to application logic when you do not need to keep the data cached in memory. Because only one row is in memory at a time, the DataReader provides the lowest overhead in terms of system performance but requires the exclusive use of an open Connection object for the lifetime of the DataReader. The DataAdapter Object The DataAdapter is the class at the core of ADO .NET's disconnected data access. It is essentially the middleman facilitating all communication between the database and a DataSet. The DataAdapter is used either to fill a DataTable or DataSet with data from the database with it's Fill method. After the memory-resident data has been manipulated, the DataAdapter can commit the changes to the database by calling the Update method. The DataAdapter provides four properties that represent database commands: 1. SelectCommand 2. InsertCommand 3. DeleteCommand 4. UpdateCommand When the Update method is called, changes in the DataSet are copied back to the database and the appropriate InsertCommand, DeleteCommand, or UpdateCommand is executed.

Content Management System (CMS) Using ADO.NET And SQL A Content Management System (CMS) is used to add, edit, and delete content on a website. For a small website, such as this, adding and deleting a page manually is fairly simple. But for a large website with lots of pages like a news website adding a page manually without a content management system can be a headache. A CMS is meant to ease the process of adding and modifying new content to a webpage. The pages content are stored in database, not in the file server. What is SQL? Structured Query Language is a non-procedural language used to define, manipulate and retrieve data. It was developed by IBM (System/R project) in 1974-1979. The American National Standards Institute (ANSI) published in 1986 the first official standard of the language (later revised in 1989, 1992 and 1999), and since then, the industry has widely adopted SQL as the relational database language. Virtually every database system nowadays is interfaced through SQL. The specific data architecture addressed by SQL is called the relational architecture. The various pieces of data (columns) are grouped into tables contained in databases, and we retrieve data using relations expressed between the tables. SQL SQL, a popular open-source implementation of SQL that is deployed by most Web host providers. USES SQL is used in web applications and acts as the database component of the LAMP software stack. Its popularity for use with web applications is closely tied to the popularity of ADO.NET, which is often combined with SQL. Several high-traffic web sites (including Flickr, Facebook, Wikipedia, Google (though not for searches), Nokia and YouTube) use SQL for its data storage and logging of user data. DISTINGUISHING FEATURES The following features are implemented by MySQL but not by some other RDBMS software:

•

•

Multiple storage engines, allowing one to choose the one that is most effective for each table in the application (in MySQL 5.0, storage engines must be compiled in; in MySQL 5.1, storage engines can be dynamically loaded at run time): Native storage engines (MyISAM, Falcon, Merge, Memory (heap), Federated, Archive, CSV, Blackhole, Cluster, Berkeley DB, EXAMPLE, and Maria) Partner-developed storage engines (InnoDB, solidDB, NitroEDB, Infobright (formerly Brighthouse), Infobright (Open Source)) Community-developed storage engines (memcached, httpd, PBXT, Revision Engine) Custom storage engines Commit grouping, gathering multiple transactions from multiple connections together to increase the number of commits per second.

•

• • •

SERVER COMPILATION TYPE There are 3 types of SQL Server Compilations for Enterprise and Community users:
• •

Standard: The SQL-Standard binaries are recommended for most users, and include the InnoDB storage engine. Max: (not MaxDB, which is a cooperation with SAP AG) is mysqld-max Extended MySQL Server. The SQL-Max binaries include additional features that may not have been as extensively tested or are not required for general usage. The SQL-Debug binaries have been compiled with extra debug information, and are not intended for production use, because the included debugging code may cause reduced performance. Beginning with SQL 5.1, SQL AB has stopped providing these different package variants. There will only be one SQL server package, which includes a mysqld binary with all functionality and storage engines enabled. Instead of providing a separate debug package, a server binary with extended debugging information is also included in the standard package.

•

•

DATABASE DESIGN

INTRODUCTION
The general theme is to handle information as in integrated whole, with a minimum of redundancy and improve performance. Some software languages are used to manipulate, describe and manage data. We have implemented pc shop database in MS access for the accuracy, integrity recovery from failure, privacy and security of data and overall good performance.

 We considered some specific objectives of our database  We control redundancy to avoid the wastage of space, and for improvement in system performance.  Our database is “Tunable” without rewriting programs that is database design  Using storing and modifying data at low cost are important so we use the programming and whose and enhancement is simple to easy to update.  The database should be recovered easily and quickly after it is down with no loss of transaction.  The response suitable to use of data to increase the overall performance of the system.

USERS Table contains the details of the users registered for our services. The fields in this table are as follows: USERID PASSWORD NAME ADDRESS CONTACT

USERID is the PRIMARY KEY of this table. TRANSACTIONS Table contains the details of all the transactions done by the users through our site. The table contains the following fields: TNO USERID TDATE ITEMID

TNO is the PRIMARY KEY of this table. ITEM Table contains the details of the current item. The table contains the following fields: ITEMID NAME PRICE

IMPLEMENTATION

Introduction
Implementation includes all those activities that take place to convert the old system to new. The new system may be totally new; replacing and existing manual or automated system, or its may be major modification is essential to provide a reliable system to meet organizational requirements.

Aspect of Implementation:
The three aspect of Implementation are: • Training personnel • Conversion procedure • Post Implementation review

Training personnel:

Even well designed system can succeed off because of the way they are operated and used, so who are directly or indirectly related with the system development. Work must known in detail what there will be, how they can make efficient use of system and what the system will do.

Proper training was provided to all the operations and users. Data entry operators have been trained so that they are able to carry out their data entry work efficiently. In addition to this training was also provided about How to add to the table? How to update data in the table? How to delete records from the tables?

Conversion procedure
The most secure method, parallel system implementation of converting of old system to the new system. This technique was used so as to gradually withdraw the old system and so letting the user to become familiar with the new system.

Post implementation and review
The fundamental concern during post implementation review was to determine whether the system needs its objectives. It was also review whether the system gives the accuracy of information requires in appropriate formats. It was also checked if the system prevents error in inputs. After a through testing of the different aspects of the system, the live data was actually loaded by the user staff sufficient training. The result indicated a considerable time saving and time very efficient.

DEFAULT.ASPX

CODE
<%@ Page Language="C#" AutoEventWireup="true" Inherits="_Default" %> CodeFile="Default.aspx.cs" <!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>Untitled Page</title> </head> <body> <form id="form1" runat="server"> <div> <table style="width: 100%;"> <tr> <td valign="top"> <asp:Image ID="Image1" runat="server" Height="124px" ImageUrl="~/Banner-AllCars.jpg" Width="100%" /></td> </tr> <tr> <td valign="top" style="text-align: justify"> <span style="font-size: 24pt"><strong>ONLINE CAR SELLING</strong> </span> <br /> <table style="font-size: 12pt; background-color: #cc6600" width="100%"> <tr> <td style="width: 600px; background-color: transparent">

ITC"><strong>

<span style="color: #6600ff; font-family: Bradley Hand

In recent years many companies have emerged promising to offer consumers an efficient, fairer and simpler way to shop for a new car online. These web sites let you point and click your way to the perfect vehicle at a perfect price. What could be better?<br /> While these online car buying web sites do in fact facilitate the sales process for both consumers and dealerships, many of the most frustrating remain, even when the initial place your vehicle inquiry traditional variables of buying a car in-person still inquiry originates online. This is because whether you

online, or walk on to the lot, you still have to negotiate and seal the final deal in person. Let's take a closer look…</strong><br /> </span> </td> <td style="width: 400px" valign="top"> <asp:Image ID="Image2" runat="server" Height="240px" ImageAlign="Right" ImageUrl="~/images/1312131244_chevrolet-beat-diesel.jpg" Width="296px" /></td> </tr> <tr> <td style="width: 600px"> <asp:Image ID="Image3" runat="server" Height="233px" ImageUrl="~/images/chevrolet-captiva-images.jpg" Width="554px" /></td> <td style="width: 400px" valign="top"> <span style="font-size: 14pt; color: #6600ff; fontfamily: Bradley Hand ITC"><strong> The online car buying process typically works like this:<br /> 1. Select car make and model<br /> 2. Select options<br /> 3. Provide your contact information<br /> 4. Wait for dealer rep to contact you with a quote<br /> </strong></span> </td> </tr> <tr> <td colspan="2"> <span style="color: #6600ff; font-family: Bradley Hand ITC"><strong> From one perspective, online car buying sites may be regarded as automated referral services in high-tech packaging. However, this is not say that some consumers do not benefit from the efficiency of online car buying services. Indeed, the Internet has made it much easier to research new cars, compare models and features and locate nearby dealerships. </strong></span> </td> </tr> </table> <br /> <br />

<p> </td> </tr> </table>

&nbsp;</p>

</div> <asp:Button ID="Button1" runat="server" PostBackUrl="~/HM.aspx" Text="Get started" Width="205px" /> </form> </body> </html>

HM.ASPX

CODE
<%@ Page Language="C#" AutoEventWireup="true" CodeFile="HM.aspx.cs" Inherits="HM" %> <!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 id="Head1" runat="server"> <title>Untitled Page</title> </head> <body> <form id="form1" runat="server"> <div> <div style="text-align: left"> <asp:Image ID="Image1" runat="server" Height="128px" ImageUrl="~/Banner-AllCars.jpg" Width="100%" /> <table style="width: 100%"> <tr> <td style="font-weight: bold; width: 132px; color: #ffff66; background-color: #cc3300; text-align: center;"> <asp:LinkButton ID="LinkButton1" runat="server" PostBackUrl="~/HM.aspx">HOME</asp:LinkButton></td>

align: center"

<td rowspan="7" style="width: 657px; background-color: #ff9900; textvalign="top"> <strong style="background-color: #cccc00">HOME<br /> </strong> <br /> The Car industry in India has seen a tremendous growth and seems growing sector in the world. Indian cars have gained acceptance and the demand for cars made in India shows no signs of decline Indian car sector has responded with an exponential progress in

to be the fastest all over the world, whatsoever. The the number of new

models launched in the recent past. <br /> <div class="bodytext"> <br /> The Indian car industry deals with different types of cars. Major Indian cars comprise big cars, <a>small cars</a>, sports cars, luxurious cars, etc. Most of the Indian car models are swank and designed on cutting-edge technology platforms, and each year there is a slew of latest car launches. <br /> <br /> For those, who cannot afford to buy a new car can go for used cars. This Indian car site will provide you a complete database of car dealers who are willing to buy and sell cars. You will get useful car buying tips and used car buying tips along with a complete used car buying guide, apart from the new car buying tips and information on new car buying service. Browse through the extensively researched categories of Indian cars and get the most updated information related to cars in India.</div> </td> <td style="font-weight: bold; width: 100px; color: #ffff66; background-color: #cc3300"> <asp:LinkButton ID="LinkButton7" runat="server" PostBackUrl="~/signin.aspx">Sign In</asp:LinkButton></td> </tr> <tr> <td style="font-weight: bold; width: 132px; color: #ffff66; background-color: #cc3300; text-align: center;"> <asp:LinkButton ID="LinkButton2" runat="server" PostBackUrl="~/contact.aspx">Contact Us</asp:LinkButton></td> <td style="font-weight: bold; width: 100px; color: #ffff66; background-color: #cc3300"> <asp:LinkButton ID="LinkButton8" runat="server" PostBackUrl="~/register.aspx">New User? Register Me</asp:LinkButton></td> </tr> <tr> <td style="font-weight: bold; width: 132px; color: #ffff66; background-color: #cc3300"> Gallery</td> <td style="font-weight: bold; width: 100px; color: #ffff66; background-color: #cc3300">

<asp:LinkButton ID="LinkButton9" runat="server" PostBackUrl="~/order.aspx">Check Your Order</asp:LinkButton></td> </tr> <tr> <td style="font-weight: bold; width: 132px; color: #ffff66; background-color: #cc3300"> <asp:LinkButton ID="LinkButton3" runat="server" PostBackUrl="~/chervolet.aspx">>Chervolet</asp:LinkButton></td> <td rowspan="4" style="font-weight: bold; width: 100px; color: #ffff66; background-color: #cc3300"> <asp:Image ID="Image2" runat="server" Height="150px" ImageUrl="~/Lincoln-Town-Cars.gif" Width="150px" /></td> </tr> <tr> <td style="font-weight: bold; width: 132px; color: #ffff66; background-color: #cc3300"> <asp:LinkButton ID="LinkButton4" runat="server" PostBackUrl="~/honda cars.aspx">>Honda</asp:LinkButton></td> </tr> <tr> <td style="font-weight: bold; width: 132px; color: #ffff66; background-color: #cc3300"> <asp:LinkButton ID="LinkButton5" runat="server" PostBackUrl="~/tata motors.aspx">>Tata Motors</asp:LinkButton></td> </tr> <tr> <td style="font-weight: bold; width: 132px; color: #ffff66; background-color: #cc3300"> <asp:LinkButton ID="LinkButton6" runat="server" PostBackUrl="~/honda.aspx">>Others</asp:LinkButton></td> </tr> </table> </div> </div> </form> </body> </html>

SIGNIN.ASPX

CODE
<%@ Page Language="C#" AutoEventWireup="true" CodeFile="signin.aspx.cs" Inherits="signin" %> <!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 id="Head1" runat="server"> <title>Untitled Page</title> </head> <body> <form id="form1" runat="server"> <div> <div style="text-align: left"> <asp:Image ID="Image1" runat="server" Height="128px" ImageUrl="~/Banner-AllCars.jpg" Width="100%" /> <table style="width: 100%"> <tr> <td style="font-weight: bold; width: 132px; color: #ffff66; background-color: #cc3300; text-align: center;"> <asp:LinkButton ID="LinkButton1" runat="server" PostBackUrl="~/HM.aspx">HOME</asp:LinkButton></td> <td rowspan="7" style="width: 606px; background-color: #ff9900; textalign: center" valign="top"> <strong><span style="font-size: 24pt; background-color: #cccc00">Sign In</span></strong><br /> <br /> <table> <tr> <td style="width: 100px"> Username</td> <td style="width: 100px"> <asp:TextBox ID="TextBox1" runat="server"></asp:TextBox></td> </tr>

<td style="width: 100px"> Password</td> <td style="width: 100px"> <asp:TextBox ID="TextBox2" runat="server"></asp:TextBox></td> </tr> <tr> <td colspan="2"> <asp:Button ID="Button1" runat="server" Text="Login" Width="135px" /></td> </tr> </table> </td> <td style="font-weight: bold; width: 100px; color: #ffff66; background-color: #cc3300"> <asp:LinkButton ID="LinkButton7" runat="server" PostBackUrl="~/signin.aspx">Sign In</asp:LinkButton></td> </tr> <tr> <td style="font-weight: bold; width: 132px; color: #ffff66; background-color: #cc3300; text-align: center;"> <asp:LinkButton ID="LinkButton2" runat="server" PostBackUrl="~/contact.aspx">Contact Us</asp:LinkButton></td> <td style="font-weight: bold; width: 100px; color: #ffff66; background-color: #cc3300"> <asp:LinkButton ID="LinkButton8" runat="server" PostBackUrl="~/register.aspx">New User? Register Me</asp:LinkButton></td> </tr> <tr> <td style="font-weight: bold; width: 132px; color: #ffff66; background-color: #cc3300"> Gallery</td> <td style="font-weight: bold; width: 100px; color: #ffff66; background-color: #cc3300"> <asp:LinkButton ID="LinkButton9" runat="server" PostBackUrl="~/order.aspx">Check Your Order</asp:LinkButton></td> </tr> <tr> <td style="font-weight: bold; width: 132px; color: #ffff66; background-color: #cc3300"> <asp:LinkButton ID="LinkButton3" runat="server" PostBackUrl="~/chervolet.aspx">>Chervolet</asp:LinkButton></td> <td rowspan="4" style="font-weight: bold; width: 100px; color: #ffff66; background-color: #cc3300"> <asp:Image ID="Image2" runat="server" Height="150px" ImageUrl="~/Lincoln-Town-Cars.gif" Width="150px" /></td> </tr> <tr> <td style="font-weight: bold; width: 132px; color: #ffff66; background-color: #cc3300"> <asp:LinkButton ID="LinkButton4" runat="server">>Honda</asp:LinkButton></td> </tr> <tr> <td style="font-weight: bold; width: 132px; color: #ffff66; background-color: #cc3300"> <asp:LinkButton ID="LinkButton5" runat="server" PostBackUrl="~/tata.aspx">>Tata Motors</asp:LinkButton></td> </tr> <tr>

<tr>

<td style="font-weight: bold; width: 132px; color: #ffff66; background-color: #cc3300"> <asp:LinkButton ID="LinkButton6" runat="server" PostBackUrl="~/honda.aspx">>Others</asp:LinkButton></td> </tr> </table> </div> </div> </form> </body> </html>

SIGNIN.ASP.CS
using using using using using using using using using using using System; System.Data; System.Configuration; System.Collections; System.Web; System.Web.Security; System.Web.UI; System.Web.UI.WebControls; System.Web.UI.WebControls.WebParts; System.Web.UI.HtmlControls; System.Data.SqlClient;

public partial class signin : System.Web.UI.Page { protected void Page_Load(object sender, EventArgs e) { } protected void Button1_Click(object sender, EventArgs e) { SqlDataReader d; SqlConnection con1 = new SqlConnection(@"Data Source=.\SQLEXPRESS;AttachDbFilename=|DataDirectory|\carselling.mdf;Integrated Security=True;User Instance=True"); con1.Open(); SqlCommand myCommand = new SqlCommand("SELECT * FROM userdetail WHERE userid = '" + TextBox1.Text + "' AND password='" + TextBox2.Text + "'", con1); d = myCommand.ExecuteReader(); if (d.Read()) { d.Close(); SqlCommand my1 = new SqlCommand("CREATE TABLE cart(carname varchar(50),price varchar(50))", con1); my1.ExecuteNonQuery(); Response.Redirect("HM.aspx"); } else Response.Redirect("register.aspx");

} }

con1.Close();

REGISTER.ASPX

CODE
<%@ Page Language="C#" AutoEventWireup="true" CodeFile="register.aspx.cs" Inherits="register" %> <!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 id="Head1" runat="server"> <title>Untitled Page</title> </head> <body> <form id="form1" runat="server"> <div> <div style="text-align: left"> <asp:Image ID="Image1" runat="server" Height="128px" ImageUrl="~/Banner-AllCars.jpg" Width="100%" /> <table style="width: 100%"> <tr> <td style="font-weight: bold; width: 132px; color: #ffff66; background-color: #cc3300; text-align: center;"> <asp:LinkButton ID="LinkButton1" runat="server" PostBackUrl="~/HM.aspx">HOME</asp:LinkButton></td> <td rowspan="7" style="width: 657px; background-color: #ff9900; textalign: center" valign="top"> <span style="font-size: 24pt"><strong><span style="backgroundcolor: #cccc00">Register Me</span></strong><br /> <br />

<table> <tr> <td style="width: 186px; height: 38px"> <span style="font-size: 14pt">Name</span></td> <td style="width: 100px; height: 38px"> <asp:TextBox ID="TextBox1" runat="server"></asp:TextBox></td> </tr> <tr> <td style="width: 186px"> <span style="font-size: 14pt">E-Mail Address</span></td> <td style="width: 100px"> <asp:TextBox ID="TextBox2" runat="server"></asp:TextBox></td> </tr> <tr> <td style="width: 186px"> <span style="font-size: 14pt">Password</span></td> <td style="width: 100px"> <asp:TextBox ID="TextBox3" runat="server"></asp:TextBox></td> </tr> <tr> <td colspan="2"> <asp:Button ID="Button1" runat="server" Text="Create user" Width="170px" /></td> </tr> </table> </span> </td> <td style="font-weight: bold; width: 100px; color: #ffff66; background-color: #cc3300"> <asp:LinkButton ID="LinkButton7" runat="server" PostBackUrl="~/signin.aspx">Sign In</asp:LinkButton></td> </tr> <tr> <td style="font-weight: bold; width: 132px; color: #ffff66; background-color: #cc3300; text-align: center;"> <asp:LinkButton ID="LinkButton2" runat="server" PostBackUrl="~/contact.aspx">Contact Us</asp:LinkButton></td> <td style="font-weight: bold; width: 100px; color: #ffff66; background-color: #cc3300"> <asp:LinkButton ID="LinkButton8" runat="server" PostBackUrl="~/register.aspx">New User? Register Me</asp:LinkButton></td> </tr> <tr> <td style="font-weight: bold; width: 132px; color: #ffff66; background-color: #cc3300"> Gallery</td> <td style="font-weight: bold; width: 100px; color: #ffff66; background-color: #cc3300"> <asp:LinkButton ID="LinkButton9" runat="server" PostBackUrl="~/order.aspx">Check Your Order</asp:LinkButton></td> </tr> <tr> <td style="font-weight: bold; width: 132px; color: #ffff66; background-color: #cc3300"> <asp:LinkButton ID="LinkButton3" runat="server" PostBackUrl="~/chervolet.aspx">>Chervolet</asp:LinkButton></td> <td rowspan="4" style="font-weight: bold; width: 100px; color: #ffff66; background-color: #cc3300">

<asp:Image ID="Image2" runat="server" Height="150px" ImageUrl="~/Lincoln-Town-Cars.gif" Width="150px" /></td> </tr> <tr> <td style="font-weight: bold; width: 132px; color: #ffff66; background-color: #cc3300"> <asp:LinkButton ID="LinkButton4" runat="server">>Honda</asp:LinkButton></td> </tr> <tr> <td style="font-weight: bold; width: 132px; color: #ffff66; background-color: #cc3300"> <asp:LinkButton ID="LinkButton5" runat="server" PostBackUrl="~/tata.aspx">>Tata Motors</asp:LinkButton></td> </tr> <tr> <td style="font-weight: bold; width: 132px; color: #ffff66; background-color: #cc3300"> <asp:LinkButton ID="LinkButton6" runat="server" PostBackUrl="~/honda.aspx">>Others</asp:LinkButton></td> </tr> </table> </div> </div> </form> </body> </html>

REGISTER.ASPX.CS
using using using using using using using using using using using System; System.Data; System.Configuration; System.Collections; System.Web; System.Web.Security; System.Web.UI; System.Web.UI.WebControls; System.Web.UI.WebControls.WebParts; System.Web.UI.HtmlControls; System.Data.SqlClient;

public partial class register : System.Web.UI.Page { protected void Page_Load(object sender, EventArgs e) { } protected void Button1_Click(object sender, EventArgs e) { SqlConnection con1 = new SqlConnection(@"Data Source=.\SQLEXPRESS;AttachDbFilename=|DataDirectory|\carselling.mdf;Integrated Security=True;User Instance=True"); con1.Open(); SqlCommand myCommand = new SqlCommand("INSERT INTO userdetail(userid,password,name,address,contact,email) VALUES ('" + TextBox5.Text + "','" + TextBox6.Text + "','" + TextBox1.Text + "','" + TextBox2.Text + "','" + TextBox3.Text + "','" + TextBox4.Text + "') ", con1); myCommand.ExecuteNonQuery();

Response.Redirect("Signin.aspx"); con1.Close(); } }

TATA MOTORS.ASPX

CODE
<%@ Page Language="C#" AutoEventWireup="true" CodeFile="tata motors.aspx.cs" Inherits="tata_motors" %> <!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 id="Head1" runat="server"> <title>Untitled Page</title> </head> <body> <form id="form1" runat="server"> <div> <div style="text-align: left"> <asp:Image ID="Image1" runat="server" Height="128px" ImageUrl="~/Banner-AllCars.jpg" Width="100%" /> <table style="width: 100%"> <tr>

<td style="font-weight: bold; width: 30px; color: #ffff66; background-color: #cc3300; height: 21px;"> <asp:LinkButton ID="LinkButton1" runat="server" PostBackUrl="~/HM.aspx">Home</asp:LinkButton></td> <td rowspan="16" style="width: 744px; background-color: #ff9900; text-align: center" valign="top"> <strong style="background-color: #cccc00">Tata Cars<br /> </strong> <table> <tr> <td style="width: 153px"> <asp:Image ID="Image3" runat="server" ImageUrl="~/tata1.jpg" /></td> <td style="width: 355px" valign="top"> <p> Tata Motors Aria </p> <p> Price Range:</p> <p class="r_12_1"> <strong>Rs.11,61,787&nbsp; <asp:Button ID="Button1" runat="server" Text="Add to Cart" OnClick="Button1_Click" /></strong></p> </td> </tr> <tr> <td style="width: 153px; height: 32px;"> <asp:Image ID="Image4" runat="server" Height="80px" ImageUrl="~/tata2.jpg" Width="107px" /></td> <td style="width: 355px; height: 32px;"> <p> Tata Motors Indica </p> <p class="gL_12_1"> Price Range:</p> <p class="r_12_1"> <strong> Rs 3,33,450 <asp:Button ID="Button2" runat="server" Text="Add to Cart" OnClick="Button2_Click" /></strong></p> </td> </tr> <tr> <td style="width: 153px; height: 20px"> <asp:Image ID="Image5" runat="server" ImageUrl="~/tata3.jpg" /></td> <td style="width: 355px; height: 20px"> <span style="color: #0000ff; text-decoration: underline">Tata Motors Indica eV2</span> <p class="gL_12_1"> Price Range:</p> <p class="r_12_1"> <strong> Rs. 2,99,450 <asp:Button ID="Button3" runat="server" Text="Add to Cart" OnClick="Button3_Click" /></strong></p> </td> </tr> <tr> <td style="width: 153px; height: 18px">

ImageUrl="~/tata4.jpg" /></td>

<asp:Image ID="Image6" runat="server"

<td style="width: 355px; height: 18px"> <p> <a class="bl_14 BD PT10"> Tata Motors Indica Vista</a> </p> <p class="gL_12_1"> Price Range:</p> <p class="r_12_1"> <strong> Rs. 3,88,850<asp:Button ID="Button8" runat="server" OnClick="Button8_Click" Text="Add to cart" /></strong></p> </td> </tr> <tr> <td style="width: 153px"> <asp:Image ID="Image7" runat="server" ImageUrl="~/tata5.jpg" /></td> <td style="width: 355px"> <p> <a class="bl_14 BD PT10"> Tata Motors Indigo Manza</a> </p> <p class="gL_12_1"> Price Range:</p> <p class="r_12_1"> <strong> Rs. 5,44,000<asp:Button ID="Button4" runat="server" Text="Add to Cart" OnClick="Button4_Click" /></strong></p> </td> </tr> <tr> <td style="width: 153px"> <asp:Image ID="Image8" runat="server" ImageUrl="~/tata7.jpg" /></td> <td style="width: 355px"> Tata Motors Nano <p> Price Range:</p> <p> <strong> Rs 1,41,450<asp:Button ID="Button5" runat="server" Text="Add to Cart" OnClick="Button5_Click" /></strong></p> </td> </tr> <tr> <td style="width: 153px"> <asp:Image ID="Image9" runat="server" ImageUrl="~/tata8.jpg" /></td> <td style="width: 355px"> <p> <a class="bl_14 BD PT10"> Tata Motors New Indigo eCS</a> </p> <p class="gL_12_1"> Price Range:</p> <p class="r_12_1"> <strong> Rs 4,48,980

<asp:Button ID="Button6" runat="server" Text="Add to Cart" OnClick="Button6_Click" /></strong></p> </td> </tr> </table> <br /> </td> <td style="font-weight: bold; width: 61px; color: #ffff66; background-color: #cc3300; height: 21px;"> <asp:LinkButton ID="LinkButton3" runat="server" PostBackUrl="~/signin.aspx">Sign In</asp:LinkButton></td> </tr> <tr> <td style="font-weight: bold; width: 30px; color: #ffff66; background-color: #cc3300; height: 10px;" valign="top"> <asp:LinkButton ID="LinkButton2" runat="server" PostBackUrl="~/contact.aspx" Width="120px">Contact Us</asp:LinkButton></td> <td style="font-weight: bold; width: 61px; color: #ffff66; background-color: #cc3300; height: 10px;"> <asp:LinkButton ID="LinkButton4" runat="server" PostBackUrl="~/register.aspx" Width="203px">New User? Register Me</asp:LinkButton></td> </tr> <tr> <td style="font-weight: bold; width: 30px; color: #ffff66; background-color: #cc3300; height: 8px;"> Gallery</td> <td style="font-weight: bold; width: 61px; color: #ffff66; background-color: #cc3300; height: 8px;"> <asp:LinkButton ID="LinkButton5" runat="server" PostBackUrl="~/order.aspx" Width="150px">Check Your Order</asp:LinkButton></td> </tr> <tr> <td style="font-weight: bold; width: 30px; color: #ffff66; background-color: #cc3300; height: 10px;" valign="top"> <asp:LinkButton ID="LinkButton6" runat="server" PostBackUrl="~/chervolet.aspx">>Chervolet</asp:LinkButton></td> <td rowspan="13" style="font-weight: bold; width: 61px; color: #ffff66; background-color: #cc3300" valign="top"> <asp:Image ID="Image2" runat="server" Height="172px" ImageUrl="~/Lincoln-Town-Cars.gif" Width="223px" /><asp:Image ID="Image12" runat="server" Height="120px" ImageUrl="~/concept-cars_2-796451-2011_wallpapers_12.jpeg" Width="222px" /><br /> <asp:Image ID="Image13" runat="server" Height="200px" ImageUrl="~/electric-cars.jpg" Width="226px" /><br /> <asp:Image ID="Image14" runat="server" ImageUrl="~/aaa.jpg" Width="227px" /></td> </tr> <tr> <td style="font-weight: bold; width: 30px; color: #ffff66; background-color: #cc3300"> <asp:LinkButton ID="LinkButton7" runat="server" PostBackUrl="~/honda cars.aspx">>Honda</asp:LinkButton></td> </tr> <tr> <td style="font-weight: bold; width: 30px; color: #ffff66; background-color: #cc3300"> <asp:LinkButton ID="LinkButton8" runat="server" PostBackUrl="~/tata motors.aspx" Width="98px">>Tata Motors</asp:LinkButton></td> </tr> <tr>

<td style="font-weight: bold; width: 30px; color: #ffff66; background-color: #cc3300"> <asp:Button ID="Button7" runat="server" Text="Logout" OnClick="Button7_Click" /></td> </tr> <tr> <td rowspan="9" style="font-weight: bold; width: 30px; color: #ffff66; background-color: #cc3300" valign="top"> <asp:Image ID="Image10" runat="server" Height="191px" ImageUrl="~/Bugatti Veyron Car Images.jpg" Width="150px" /><br /> <asp:Image ID="Image11" runat="server" ImageUrl="~/BMW M3 - 2002 - 03.jpg" Width="150px" /></td> </tr> <tr> </tr> <tr> </tr> <tr> </tr> <tr> </tr> <tr> </tr> <tr> </tr> <tr> </tr> <tr> </tr> </table> </div> </div> </form> </body> </html>

TATA MOTORS.ASPX.CS
using System; using System.Data; using System.Configuration; using System.Collections; 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; public partial class tata_motors : System.Web.UI.Page { protected void Page_Load(object sender, EventArgs e) { } protected void Button1_Click(object sender, EventArgs e) { SqlConnection con1 = new SqlConnection(@"Data Source=.\SQLEXPRESS;AttachDbFilename=|DataDirectory|\carselling.mdf;Integrated Security=True;User Instance=True");

string a, b; a = "Tata Motors Aria "; b = "1161787"; con1.Open(); SqlCommand myCommand = new SqlCommand("INSERT INTO cart(carname,price) VALUES (@cn,@pr) ", con1); myCommand.Parameters.AddWithValue("@cn", a); myCommand.Parameters.AddWithValue("@pr", b); myCommand.ExecuteNonQuery(); con1.Close(); } protected void Button2_Click(object sender, EventArgs e) { SqlConnection con1 = new SqlConnection(@"Data Source=.\SQLEXPRESS;AttachDbFilename=|DataDirectory|\carselling.mdf;Integrated Security=True;User Instance=True"); string a, b; a = "Tata Motors Indica"; b = "333450"; con1.Open(); SqlCommand myCommand = new SqlCommand("INSERT INTO cart(carname,price) VALUES (@cn,@pr) ", con1); myCommand.Parameters.AddWithValue("@cn", a); myCommand.Parameters.AddWithValue("@pr", b); myCommand.ExecuteNonQuery(); con1.Close(); } protected void Button3_Click(object sender, EventArgs e) { SqlConnection con1 = new SqlConnection(@"Data Source=.\SQLEXPRESS;AttachDbFilename=|DataDirectory|\carselling.mdf;Integrated Security=True;User Instance=True"); string a, b; a = "Tata Motors Indica eV2 "; b = "299450"; con1.Open(); SqlCommand myCommand = new SqlCommand("INSERT INTO cart(carname,price) VALUES (@cn,@pr) ", con1); myCommand.Parameters.AddWithValue("@cn", a); myCommand.Parameters.AddWithValue("@pr", b); myCommand.ExecuteNonQuery(); con1.Close(); } protected void Button8_Click(object sender, EventArgs e) { SqlConnection con1 = new SqlConnection(@"Data Source=.\SQLEXPRESS;AttachDbFilename=|DataDirectory|\carselling.mdf;Integrated Security=True;User Instance=True"); string a, b; a = "Tata Motors Indica Vista"; b = "388853"; con1.Open(); SqlCommand myCommand = new SqlCommand("INSERT INTO cart(carname,price) VALUES (@cn,@pr) ", con1); myCommand.Parameters.AddWithValue("@cn", a); myCommand.Parameters.AddWithValue("@pr", b); myCommand.ExecuteNonQuery(); con1.Close(); }

protected void Button4_Click(object sender, EventArgs e) { SqlConnection con1 = new SqlConnection(@"Data Source=.\SQLEXPRESS;AttachDbFilename=|DataDirectory|\carselling.mdf;Integrated Security=True;User Instance=True"); string a, b; a = "Tata Motors Indigo Manza"; b = "514000"; con1.Open(); SqlCommand myCommand = new SqlCommand("INSERT INTO cart(carname,price) VALUES (@cn,@pr) ", con1); myCommand.Parameters.AddWithValue("@cn", a); myCommand.Parameters.AddWithValue("@pr", b); myCommand.ExecuteNonQuery(); con1.Close(); } protected void Button5_Click(object sender, EventArgs e) { SqlConnection con1 = new SqlConnection(@"Data Source=.\SQLEXPRESS;AttachDbFilename=|DataDirectory|\carselling.mdf;Integrated Security=True;User Instance=True"); string a, b; a = "Tata Motors Nano "; b = "141450"; con1.Open(); SqlCommand myCommand = new SqlCommand("INSERT INTO cart(carname,price) VALUES (@cn,@pr) ", con1); myCommand.Parameters.AddWithValue("@cn", a); myCommand.Parameters.AddWithValue("@pr", b); myCommand.ExecuteNonQuery(); con1.Close(); } protected void Button6_Click(object sender, EventArgs e) { SqlConnection con1 = new SqlConnection(@"Data Source=.\SQLEXPRESS;AttachDbFilename=|DataDirectory|\carselling.mdf;Integrated Security=True;User Instance=True"); string a, b; a = "Tata Motors New Indigo eCS"; b = "448900"; con1.Open(); SqlCommand myCommand = new SqlCommand("INSERT INTO cart(carname,price) VALUES (@cn,@pr) ", con1); myCommand.Parameters.AddWithValue("@cn", a); myCommand.Parameters.AddWithValue("@pr", b); myCommand.ExecuteNonQuery(); con1.Close(); } protected void Button7_Click(object sender, EventArgs e) { SqlConnection con1 = new SqlConnection(@"Data Source=.\SQLEXPRESS;AttachDbFilename=|DataDirectory|\carselling.mdf;Integrated Security=True;User Instance=True"); con1.Open(); SqlCommand myCommand = new SqlCommand("DROP TABLE cart)", con1); myCommand.ExecuteNonQuery(); con1.Close(); }

}

HONDA.ASPX

CODE
<%@ Page Language="C#" AutoEventWireup="true" CodeFile="honda cars.aspx.cs" Inherits="honda_cars" %> <!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 id="Head1" runat="server"> <title>Untitled Page</title> </head> <body> <form id="form1" runat="server"> <div> <div style="text-align: left"> <asp:Image ID="Image1" Width ="100%" runat="server" Height="128px" ImageUrl="~/Banner-AllCars.jpg" /> <table style="width: 100%"> <tr> <td style="font-weight: bold; width: 132px; color: #ffff66; background-color: #cc3300"> <asp:LinkButton ID="LinkButton1" runat="server" PostBackUrl="~/HM.aspx">Home</asp:LinkButton></td> <td rowspan="8" style="width: 657px; background-color: #ff9900; textalign: center" valign="top">

<strong style="background-color: #cccc00">HondaCars<br /> </strong> <table> <tr> <td style="width: 153px"> <asp:Image ID="Image3" runat="server" ImageUrl="~/city_100x75.jpg" /></td> <td style="width: 285px" valign="top"> <p> <a class="bl_14 BD PT10" href="http://www.zigwheels.com/newcars/Honda/City">Honda City</a> </p> <p class="gL_12_1"> Price Range:</p> <p class="r_12_1"> <strong>&nbsp;Rs.7,40,999&nbsp; <asp:Button ID="Button1" runat="server" Text="Add to Cart" Width="113px" OnClick="Button1_Click" /></strong></p> </td> </tr> <tr> <td style="width: 153px; height: 32px;"> <asp:Image ID="Image4" runat="server" ImageUrl="~/honda-civic_100x75.jpg" /></td> <td style="width: 285px; height: 32px;"> <p> <a class="bl_14 BD PT10" href="http://www.zigwheels.com/newcars/Honda/Civic">Honda Civic</a> </p> <p class="gL_12_1"> Price Range:</p> <p class="r_12_1"> <strong>&nbsp; Rs.12,22,000<asp:Button ID="Button2" runat="server" Text="Add to Cart" OnClick="Button2_Click" /></strong></p> </td> </tr> <tr> <td style="width: 153px; height: 20px"> <asp:Image ID="Image5" runat="server" ImageUrl="~/hondabrioslide320_240_100x75.jpg" /></td> <td style="width: 285px; height: 20px"> <p> <a class="bl_14 BD PT10" href="http://www.zigwheels.com/newcars/Honda/Brio">Honda Brio</a> </p> <p class="gL_12_1"> Price Range:</p> <p class="r_12_1"> <strong>&nbsp; Rs.3,95 ,989<asp:Button ID="Button3" runat="server" Text="Add to Cart" OnClick="Button3_Click" /></strong></p> </td> </tr> <tr> <td style="width: 153px"> <asp:Image ID="Image6" runat="server" ImageUrl="~/hondacrv2_9_100x75.jpg" /></td> <td style="width: 285px"> <p> <a class="bl_14 BD PT10" href="http://www.zigwheels.com/newcars/Honda/CR-V">Honda CR V</a> </p> <p class="gL_12_1">

Price Range:</p> <p class="r_12_1"> <strong>&nbsp; Rs.22,64,009<asp:Button ID="Button4" runat="server" Text="Add to Cart" OnClick="Button4_Click" /></strong></p> </td> </tr> <tr> <td style="width: 153px"> <asp:Image ID="Image7" runat="server" ImageUrl="~/newhondaaccord_3_100x75.jpg" /></td> <td style="width: 285px"> <span style="color: #0000ff; text-decoration: underline">Honda Accord</span> <p class="gL_12_1"> Price Range:</p> <p class="r_12_1"> <strong>&nbsp; Rs.19,61,260 <asp:Button ID="Button5" runat="server" Text="Add to Cart" OnClick="Button5_Click" /></strong></p> </td> </tr> <tr> <td style="width: 153px"> <asp:Image ID="Image8" runat="server" ImageUrl="~/newhondajazzface_320x240_100x75.jpg" /></td> <td style="width: 285px"> <p> <a class="bl_14 BD PT10" href="http://www.zigwheels.com/newcars/Honda/Jazz">Honda Jazz</a> </p> <p class="gL_12_1"> Price Range:</p> <p class="r_12_1"> <strong>&nbsp; Rs.5,50,000 <asp:Button ID="Button6" runat="server" Text="Add to Cart" OnClick="Button6_Click" /></strong></p> </td> </tr> <tr> <td style="width: 153px"> </td> <td style="width: 285px"> </td> </tr> </table> <br /> </td> <td style="font-weight: bold; width: 100px; color: #ffff66; background-color: #cc3300"> <asp:LinkButton ID="LinkButton3" runat="server" PostBackUrl="~/signin.aspx">Sign In</asp:LinkButton></td> </tr> <tr> <td style="font-weight: bold; width: 132px; color: #ffff66; background-color: #cc3300"> <asp:LinkButton ID="LinkButton2" runat="server" PostBackUrl="~/contact.aspx">Contact Us</asp:LinkButton></td> <td style="font-weight: bold; width: 100px; color: #ffff66; background-color: #cc3300"> <asp:LinkButton ID="LinkButton4" runat="server" PostBackUrl="~/register.aspx" Width="181px">New User? Register Me</asp:LinkButton></td> </tr> <tr>

<td style="font-weight: bold; width: 132px; color: #ffff66; background-color: #cc3300"> Gallery</td> <td style="font-weight: bold; width: 100px; color: #ffff66; background-color: #cc3300"> <asp:LinkButton ID="LinkButton5" runat="server" PostBackUrl="~/order.aspx" Width="151px">Check Your Order</asp:LinkButton></td> </tr> <tr> <td style="font-weight: bold; width: 132px; color: #ffff66; background-color: #cc3300"> <asp:LinkButton ID="LinkButton6" runat="server" PostBackUrl="~/chervolet.aspx">>Chervolet</asp:LinkButton></td> <td rowspan="5" style="font-weight: bold; width: 100px; color: #ffff66; background-color: #cc3300" valign="top"> <asp:Image ID="Image2" runat="server" Height="150px" ImageUrl="~/Lincoln-Town-Cars.gif" Width="229px" /><br /> <asp:Image ID="Image12" runat="server" Height="120px" ImageUrl="~/concept-cars_2-796451-2011_wallpapers_12.jpeg" Width="227px" /><br /> <asp:Image ID="Image13" runat="server" Height="200px" ImageUrl="~/electric-cars.jpg" Width="226px" /></td> </tr> <tr> <td style="font-weight: bold; width: 132px; color: #ffff66; background-color: #cc3300"> <asp:LinkButton ID="LinkButton7" runat="server" PostBackUrl="~/honda cars.aspx">>Honda</asp:LinkButton></td> </tr> <tr> <td style="font-weight: bold; width: 132px; color: #ffff66; background-color: #cc3300"> <asp:LinkButton ID="LinkButton8" runat="server" PostBackUrl="~/tata motors.aspx">>Tata Motors</asp:LinkButton></td> </tr> <tr> <td style="font-weight: bold; width: 132px; color: #ffff66; background-color: #cc3300" rowspan="2" valign="top"> <asp:Button ID="Button7" runat="server" Text="Logout" Width="139px" OnClick="Button7_Click" /><br /> <asp:Image ID="Image10" runat="server" Height="191px" ImageUrl="~/Bugatti Veyron Car Images.jpg" Width="150px" /><br /> <asp:Image ID="Image11" runat="server" Height="153px" ImageUrl="~/BMW M3 - 2002 - 03.jpg" Width="150px" /></td> </tr> <tr> </tr> </table> </div> </div> </form> </body> </html>

HONDA.ASPX.CS
using System;

using System.Data; using System.Configuration; using System.Collections; 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; public partial class honda_cars : System.Web.UI.Page { protected void Page_Load(object sender, EventArgs e) { } protected void Button1_Click(object sender, EventArgs e) { SqlConnection con1 = new SqlConnection(@"Data Source=.\SQLEXPRESS;AttachDbFilename=|DataDirectory|\carselling.mdf;Integrated Security=True;User Instance=True"); string a, b; a = "Honda City"; b = "740999"; con1.Open(); SqlCommand myCommand = new SqlCommand("INSERT INTO cart(carname,price) VALUES (@cn,@pr) ", con1); myCommand.Parameters.AddWithValue("@cn", a); myCommand.Parameters.AddWithValue("@pr", b); myCommand.ExecuteNonQuery(); con1.Close(); } protected void Button2_Click(object sender, EventArgs e) { SqlConnection con1 = new SqlConnection(@"Data Source=.\SQLEXPRESS;AttachDbFilename=|DataDirectory|\carselling.mdf;Integrated Security=True;User Instance=True"); string a, b; a = "Honda Civic"; b = "1222000"; con1.Open(); SqlCommand myCommand = new SqlCommand("INSERT INTO cart(carname,price) VALUES (@cn,@pr) ", con1); myCommand.Parameters.AddWithValue("@cn", a); myCommand.Parameters.AddWithValue("@pr", b); myCommand.ExecuteNonQuery(); con1.Close(); } protected void Button3_Click(object sender, EventArgs e) { SqlConnection con1 = new SqlConnection(@"Data Source=.\SQLEXPRESS;AttachDbFilename=|DataDirectory|\carselling.mdf;Integrated Security=True;User Instance=True"); string a, b; a = "Honda Brio "; b = "395989"; con1.Open(); SqlCommand myCommand = new SqlCommand("INSERT INTO cart(carname,price) VALUES (@cn,@pr) ", con1); myCommand.Parameters.AddWithValue("@cn", a); myCommand.Parameters.AddWithValue("@pr", b);

myCommand.ExecuteNonQuery(); con1.Close(); } protected void Button4_Click(object sender, EventArgs e) { SqlConnection con1 = new SqlConnection(@"Data Source=.\SQLEXPRESS;AttachDbFilename=|DataDirectory|\carselling.mdf;Integrated Security=True;User Instance=True"); string a, b; a = "Honda CR V "; b = "2264009"; con1.Open(); SqlCommand myCommand = new SqlCommand("INSERT INTO cart(carname,price) VALUES (@cn,@pr) ", con1); myCommand.Parameters.AddWithValue("@cn", a); myCommand.Parameters.AddWithValue("@pr", b); myCommand.ExecuteNonQuery(); con1.Close(); } protected void Button5_Click(object sender, EventArgs e) { SqlConnection con1 = new SqlConnection(@"Data Source=.\SQLEXPRESS;AttachDbFilename=|DataDirectory|\carselling.mdf;Integrated Security=True;User Instance=True"); string a, b; a = "Honda Acord"; b = "1961220"; con1.Open(); SqlCommand myCommand = new SqlCommand("INSERT INTO cart(carname,price) VALUES (@cn,@pr) ", con1); myCommand.Parameters.AddWithValue("@cn", a); myCommand.Parameters.AddWithValue("@pr", b); myCommand.ExecuteNonQuery(); con1.Close(); } protected void Button6_Click(object sender, EventArgs e) { SqlConnection con1 = new SqlConnection(@"Data Source=.\SQLEXPRESS;AttachDbFilename=|DataDirectory|\carselling.mdf;Integrated Security=True;User Instance=True"); string a, b; a = "Honda Jazz "; b = "550000"; con1.Open(); SqlCommand myCommand = new SqlCommand("INSERT INTO cart(carname,price) VALUES (@cn,@pr) ", con1); myCommand.Parameters.AddWithValue("@cn", a); myCommand.Parameters.AddWithValue("@pr", b); myCommand.ExecuteNonQuery(); con1.Close(); } protected void Button7_Click(object sender, EventArgs e) { SqlConnection con1 = new SqlConnection(@"Data Source=.\SQLEXPRESS;AttachDbFilename=|DataDirectory|\carselling.mdf;Integrated Security=True;User Instance=True"); con1.Open(); SqlCommand myCommand = new SqlCommand("DROP TABLE cart)", con1);

myCommand.ExecuteNonQuery(); } } con1.Close();

CHREVOLET.ASPX

CODE
<%@ Page Language="C#" AutoEventWireup="true" CodeFile="chervolet.aspx.cs" Inherits="chervolet" %> <!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 id="Head1" runat="server"> <title>Untitled Page</title> </head> <body> <form id="form1" runat="server"> <div> <div style="text-align: left"> <asp:Image ID="Image1" runat="server" Height="128px" ImageUrl="~/Banner-AllCars.jpg" Width="100%" /> <table style="width: 100%"> <tr> <td style="font-weight: bold; width: 132px; color: #ffff66; background-color: #cc3300">

<asp:LinkButton ID="LinkButton1" runat="server" PostBackUrl="~/HM.aspx">Home</asp:LinkButton></td> <td rowspan="7" style="width: 657px; background-color: #ff9900; textalign: center" valign="top"> <strong style="background-color: #cccc00">Chervolet Cars<br /> </strong> <table> <tr> <td style="width: 153px"> <asp:Image ID="Image3" runat="server" ImageUrl="~/1254s.jpg" /></td> <td style="width: 382px"> <a class="href-title">Chevrolet Spark</a> <br /> <strong>Rs. 3,27,553</strong> <br /> <asp:Button ID="Button1" runat="server" Text="ADD TO CART" OnClick="Button1_Click" /></td> </tr> <tr> <td style="width: 153px"> <asp:Image ID="Image4" runat="server" ImageUrl="~/1546s.jpg" /></td> <td style="width: 382px"> <span style="color: #0000ff; text-decoration: underline">Chevrolet Beat<br /> </span><strong>Rs. 3,63,450</strong> <br /> <asp:Button ID="Button2" runat="server" Text="ADD TO CART" OnClick="Button2_Click" /></td> </tr> <tr> <td style="width: 153px; height: 20px"> <asp:Image ID="Image5" runat="server" ImageUrl="~/1548s.jpg" /></td> <td style="width: 382px; height: 20px"> <a class="href-title" href="http://www.carwale.com/research/chevrolet-cars/aveouva/"> Chevrolet Aveo U-VA</a> <br /> <strong>Rs. 4,20,158</strong><br /> <asp:Button ID="Button3" runat="server" Text="ADD TO CART" OnClick="Button3_Click" /></td> </tr> <tr> <td style="width: 153px"> <asp:Image ID="Image6" runat="server" ImageUrl="~/1621s.jpg" /></td> <td style="width: 382px"> <a class="href-title" href="http://www.carwale.com/research/chevrolet-cars/aveo/">Chevrolet Aveo</a> <br /> <strong>Rs. 5,97,745</strong> <br /> <asp:Button ID="Button4" runat="server" Text="ADD TO CART" OnClick="Button4_Click" /></td> </tr> <tr> <td style="width: 153px"> <asp:Image ID="Image7" runat="server" ImageUrl="~/1669s.jpg" /></td>

<td style="width: 382px"> <a class="href-title" href="http://www.carwale.com/research/chevrolet-cars/tavera/"> Chevrolet Tavera</a><br /> <strong>Rs. 6,47,974<br /> <asp:Button ID="Button5" runat="server" Text="ADD TO CART" OnClick="Button5_Click" /></strong></td> </tr> <tr> <td style="width: 153px; height: 73px;"> <asp:Image ID="Image8" runat="server" ImageUrl="~/1680s.jpg" /></td> <td style="width: 382px; height: 73px;"> <a class="href-title" href="http://www.carwale.com/research/chevrolet-cars/optramagnum/"> Chevrolet Optra Magnum</a><br /> <strong>Rs. 7,50,122<br /> <asp:Button ID="Button6" runat="server" Text="ADD TO CART" OnClick="Button6_Click" /></strong></td> </tr> <tr> <td style="width: 153px"> <asp:Image ID="Image9" runat="server" ImageUrl="~/1810s.jpg" /></td> <td style="width: 382px"> <a class="href-title" href="http://www.carwale.com/research/chevrolet-cars/cruze/">Chevrolet Cruze</a><br /> <strong>Rs. 12,19,648</strong> <br /> <asp:Button ID="Button7" runat="server" Text="ADD TO CART" OnClick="Button7_Click" /></td> </tr> </table> <br /> </td> <td style="font-weight: bold; width: 100px; color: #ffff66; background-color: #cc3300"> <asp:LinkButton ID="LinkButton6" runat="server" PostBackUrl="~/signin.aspx">Sign In</asp:LinkButton></td> </tr> <tr> <td style="font-weight: bold; width: 132px; color: #ffff66; background-color: #cc3300"> <asp:LinkButton ID="LinkButton2" runat="server" PostBackUrl="~/contact.aspx">Contact Us</asp:LinkButton></td> <td style="font-weight: bold; width: 100px; color: #ffff66; background-color: #cc3300"> <asp:LinkButton ID="LinkButton7" runat="server" PostBackUrl="~/register.aspx" Width="128px">New User? Register Me</asp:LinkButton></td> </tr> <tr> <td style="font-weight: bold; width: 132px; color: #ffff66; background-color: #cc3300"> Gallery</td> <td style="font-weight: bold; width: 100px; color: #ffff66; background-color: #cc3300"> <asp:LinkButton ID="LinkButton8" runat="server" PostBackUrl="~/order.aspx" Width="132px">Check Your Order</asp:LinkButton></td> </tr> <tr> <td style="font-weight: bold; width: 132px; color: #ffff66; background-color: #cc3300">

<asp:LinkButton ID="LinkButton3" runat="server" PostBackUrl="~/chervolet.aspx">>Chervolet</asp:LinkButton></td> <td rowspan="4" style="font-weight: bold; width: 100px; color: #ffff66; background-color: #cc3300"> <asp:Image ID="Image2" runat="server" Height="150px" ImageUrl="~/Lincoln-Town-Cars.gif" Width="150px" /></td> </tr> <tr> <td style="font-weight: bold; width: 132px; color: #ffff66; background-color: #cc3300"> <asp:LinkButton ID="LinkButton4" runat="server" PostBackUrl="~/honda cars.aspx">>Honda</asp:LinkButton></td> </tr> <tr> <td style="font-weight: bold; width: 132px; color: #ffff66; background-color: #cc3300"> <asp:LinkButton ID="LinkButton5" runat="server" PostBackUrl="~/tata motors.aspx">>Tata Motors</asp:LinkButton></td> </tr> <tr> <td style="font-weight: bold; width: 132px; color: #ffff66; background-color: #cc3300" valign="top"> <asp:Button ID="Button8" runat="server" Text="LOGOUT" OnClick="Button8_Click" /></td> </tr> </table> </div> </div> </form> </body> </html>

CHERVOLET.ASPX.CS
using using using using using using using using using using using System; System.Data; System.Configuration; System.Collections; System.Web; System.Web.Security; System.Web.UI; System.Web.UI.WebControls; System.Web.UI.WebControls.WebParts; System.Web.UI.HtmlControls; System.Data.SqlClient;

public partial class chervolet : System.Web.UI.Page { protected void Page_Load(object sender, EventArgs e) { } protected void Button1_Click(object sender, EventArgs e) { SqlConnection con1 = new SqlConnection(@"Data Source=.\SQLEXPRESS;AttachDbFilename=|DataDirectory|\carselling.mdf;Integrated Security=True;User Instance=True"); string a, b;

a = "Chevrolet Spark"; b = "327553"; con1.Open(); SqlCommand myCommand = new SqlCommand("INSERT INTO cart(carname,price) VALUES (@cn,@pr) ", con1); myCommand.Parameters.AddWithValue("@cn", a); myCommand.Parameters.AddWithValue("@pr", b); myCommand.ExecuteNonQuery(); con1.Close(); } protected void Button2_Click(object sender, EventArgs e) { SqlConnection con1 = new SqlConnection(@"Data Source=.\SQLEXPRESS;AttachDbFilename=|DataDirectory|\carselling.mdf;Integrated Security=True;User Instance=True"); string a, b; a = "Chevrolet Beat"; b = "363450"; con1.Open(); SqlCommand myCommand = new SqlCommand("INSERT INTO cart(carname,price) VALUES (@cn,@pr) ", con1); myCommand.Parameters.AddWithValue("@cn", a); myCommand.Parameters.AddWithValue("@pr", b); myCommand.ExecuteNonQuery(); con1.Close(); } protected void Button3_Click(object sender, EventArgs e) { SqlConnection con1 = new SqlConnection(@"Data Source=.\SQLEXPRESS;AttachDbFilename=|DataDirectory|\carselling.mdf;Integrated Security=True;User Instance=True"); string a, b; a = "Chevrolet Aveo U-VA "; b = "420158"; con1.Open(); SqlCommand myCommand = new SqlCommand("INSERT INTO cart(carname,price) VALUES (@cn,@pr) ", con1); myCommand.Parameters.AddWithValue("@cn", a); myCommand.Parameters.AddWithValue("@pr", b); myCommand.ExecuteNonQuery(); con1.Close(); } protected void Button4_Click(object sender, EventArgs e) { SqlConnection con1 = new SqlConnection(@"Data Source=.\SQLEXPRESS;AttachDbFilename=|DataDirectory|\carselling.mdf;Integrated Security=True;User Instance=True"); string a, b; a = "Chevrolet Aveo"; b = "597745"; con1.Open(); SqlCommand myCommand = new SqlCommand("INSERT INTO cart(carname,price) VALUES (@cn,@pr) ", con1); myCommand.Parameters.AddWithValue("@cn", a); myCommand.Parameters.AddWithValue("@pr", b); myCommand.ExecuteNonQuery(); con1.Close(); } protected void Button5_Click(object sender, EventArgs e)

SqlConnection con1 = new SqlConnection(@"Data Source=.\SQLEXPRESS;AttachDbFilename=|DataDirectory|\carselling.mdf;Integrated Security=True;User Instance=True"); string a, b; a = "Chevrolet Tavera"; b = "647947"; con1.Open(); SqlCommand myCommand = new SqlCommand("INSERT INTO cart(carname,price) VALUES (@cn,@pr) ", con1); myCommand.Parameters.AddWithValue("@cn", a); myCommand.Parameters.AddWithValue("@pr", b); myCommand.ExecuteNonQuery(); con1.Close(); } protected void Button6_Click(object sender, EventArgs e) { SqlConnection con1 = new SqlConnection(@"Data Source=.\SQLEXPRESS;AttachDbFilename=|DataDirectory|\carselling.mdf;Integrated Security=True;User Instance=True"); string a, b; a = "Chevrolet Optra Magnum"; b = "750112"; con1.Open(); SqlCommand myCommand = new SqlCommand("INSERT INTO cart(carname,price) VALUES (@cn,@pr) ", con1); myCommand.Parameters.AddWithValue("@cn", a); myCommand.Parameters.AddWithValue("@pr", b); myCommand.ExecuteNonQuery(); con1.Close(); } protected void Button7_Click(object sender, EventArgs e) { SqlConnection con1 = new SqlConnection(@"Data Source=.\SQLEXPRESS;AttachDbFilename=|DataDirectory|\carselling.mdf;Integrated Security=True;User Instance=True"); string a, b; a = "Chevrolet Cruze"; b = "1219640"; con1.Open(); SqlCommand myCommand = new SqlCommand("INSERT INTO cart(carname,price) VALUES (@cn,@pr) ", con1); myCommand.Parameters.AddWithValue("@cn", a); myCommand.Parameters.AddWithValue("@pr", b); myCommand.ExecuteNonQuery(); con1.Close(); } protected void Button8_Click(object sender, EventArgs e) { SqlConnection con1 = new SqlConnection(@"Data Source=.\SQLEXPRESS;AttachDbFilename=|DataDirectory|\carselling.mdf;Integrated Security=True;User Instance=True"); con1.Open(); SqlCommand myCommand = new SqlCommand("DROP TABLE cart)", con1); myCommand.ExecuteNonQuery(); } } con1.Close();

{

ORDER.ASPX

CODE
<%@ Page Language="C#" AutoEventWireup="true" CodeFile="order.aspx.cs" Inherits="order" %> <!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 id="Head1" runat="server"> <title>Untitled Page</title> </head> <body> <form id="form1" runat="server"> <div> <div style="text-align: left"> <table width="100%"> <tr> <td colspan="3" style="height: 181px"> <asp:Image ID="Image1" runat="server" Height="128px" ImageUrl="~/Banner-AllCars.jpg" Width="100%" /></td> </tr> <tr> <td style="font-weight: bold; width: 132px; color: #ffff66; background-color: #cc3300; text-align: center;"> <asp:LinkButton ID="LinkButton1" runat="server" PostBackUrl="~/HM.aspx">HOME</asp:LinkButton></td> <td rowspan="7" style="width: 657px; background-color: #ff9900; textalign: center" valign="top"> <span style="font-size: 24pt"><span></span><strong><span style="background-color: #cccc00">

WHAT YOU HAVE ORDERED</span></strong><br /> <asp:Button ID="Button1" runat="server" OnClick="Button1_Click1" Text="Display Order" Width="150px" /><br /> &nbsp;<br /> <table> <tr> <td style="width: 158px; height: 18px" valign="top"> <asp:Label ID="Label1" runat="server" FontSize="X-Large" Text="Product Name" Width="159px"></asp:Label></td> <td style="width: 100px; height: 18px" valign="top"> <asp:TextBox ID="TextBox1" runat="server" Width="174px"></asp:TextBox></td> </tr> <tr> <td style="width: 158px" valign="top"> <asp:Label ID="Label2" runat="server" FontSize="X-Large" Text="Price"></asp:Label></td> <td style="width: 100px" valign="top"> <asp:TextBox ID="TextBox2" runat="server" FontSize="Medium"></asp:TextBox></td> </tr> <tr> <td colspan="2" valign="top"> </td> </tr> </table> </span> </td> <td style="font-weight: bold; width: 100px; color: #ffff66; background-color: #cc3300"> <asp:LinkButton ID="LinkButton9" runat="server" PostBackUrl="~/signin.aspx">Sign In</asp:LinkButton></td> </tr> <tr> <td style="font-weight: bold; width: 132px; color: #ffff66; background-color: #cc3300; text-align: center;"> <asp:LinkButton ID="LinkButton2" runat="server" PostBackUrl="~/contact.aspx">Contact Us</asp:LinkButton></td> <td style="font-weight: bold; width: 100px; color: #ffff66; background-color: #cc3300"> <asp:LinkButton ID="LinkButton8" runat="server" PostBackUrl="~/register.aspx" Width="140px">New User? Register Me</asp:LinkButton></td> </tr> <tr> <td style="font-weight: bold; width: 132px; color: #ffff66; background-color: #cc3300"> Gallery</td> <td style="font-weight: bold; width: 100px; color: #ffff66; background-color: #cc3300"> <asp:LinkButton ID="LinkButton7" runat="server" PostBackUrl="~/order.aspx" Width="141px">Check Your Order</asp:LinkButton></td> </tr> <tr> <td style="font-weight: bold; width: 132px; color: #ffff66; background-color: #cc3300; height: 33px;"> <asp:LinkButton ID="LinkButton3" runat="server" PostBackUrl="~/chervolet.aspx">>Chervolet</asp:LinkButton></td> <td rowspan="4" style="font-weight: bold; width: 100px; color: #ffff66; background-color: #cc3300" valign="top"> <asp:Image ID="Image2" runat="server" Height="150px" ImageUrl="~/Lincoln-Town-Cars.gif" Width="150px" /></td>

</tr> <tr> <td style="font-weight: bold; width: 132px; color: #ffff66; background-color: #cc3300; height: 35px;"> <asp:LinkButton ID="LinkButton4" runat="server" PostBackUrl="~/honda cars.aspx">>Honda</asp:LinkButton></td> </tr> <tr> <td style="font-weight: bold; width: 132px; color: #ffff66; background-color: #cc3300; height: 35px;"> <asp:LinkButton ID="LinkButton5" runat="server" PostBackUrl="~/tata motors.aspx">>Tata Motors</asp:LinkButton></td> </tr> <tr> <td style="font-weight: bold; width: 132px; color: #ffff66; background-color: #cc3300; height: 195px;" valign="top"> <asp:Button ID="Button2" runat="server" OnClick="Button2_Click" Text="Logout" /></td> </tr> </table> </div> </div> </form> </body> </html> using using using using using using using using using using using

ORDER.ASPX.CS
System; System.Data; System.Configuration; System.Collections; System.Web; System.Web.Security; System.Web.UI; System.Web.UI.WebControls; System.Web.UI.WebControls.WebParts; System.Web.UI.HtmlControls; System.Data.SqlClient;

public partial class order : System.Web.UI.Page { protected void Page_Load(object sender, EventArgs e) { } protected void Button1_Click1(object sender, EventArgs e) { SqlDataReader d; SqlConnection con1 = new SqlConnection(@"Data Source=.\SQLEXPRESS;AttachDbFilename=|DataDirectory|\carselling.mdf;Integrated Security=True;User Instance=True"); con1.Open(); SqlCommand myCommand = new SqlCommand("SELECT * FROM cart", con1); d = myCommand.ExecuteReader(); if (d.Read()) { TextBox1.Text = d["carname"].ToString(); TextBox2.Text = d["price"].ToString(); Response.Write("your car has been booked. Please contact our center for deleivery of car");

} else

Response.Write("Sorry! Your cart is empty");

con1.Close(); } protected void Button2_Click(object sender, EventArgs e) { SqlConnection con1 = new SqlConnection(@"Data Source=.\SQLEXPRESS;AttachDbFilename=|DataDirectory|\carselling.mdf;Integrated Security=True;User Instance=True"); con1.Open(); SqlCommand myCommand = new SqlCommand("DROP TABLE cart", con1); myCommand.ExecuteNonQuery(); con1.Close(); } }

COST ESTIMATION

COST ESTIMATION
Software cost comprised a small percentage of overall computer based system cost. An order of magnitude error in estimate of software cost had relatively impact. Today, software is the most expensive element in most computer based system. A large cost estimation error can make the difference between profit and loss. Cost over can be disastrous for the developer. Software cost and effort estimation will never be an exact since. To many variable human, technical, environment, political, can affect the ultimate cost of software and effort applied to develop it. However, software project estimation can be transformed from a mysterious art to series of systematic steps that provides estimates with acceptable risk. The fundamental difficulties in cost estimation involve determining the size and scope of the project during the planning phase, and deciding how to extrapolate past performance to the present project. The two fundamental approaches to cost estimation are the top-down and bottom-up approaches. The top-down approaches focuses on the cost of performing the various fundamental activities associated with a software project such as planning, management, development, quality assurance, configuration management, publication, machine resources and product integration. The bottom-up approaches focuses on estimating the cost of developing each component in the software project and summing those costs to arrive at an overall estimate.

CONCLUSION

CONCLUSION
I have accomplished various goals in developing the purposed system. USER FRIENDLINESS The system is totally user friendly since the user has only to enter the data and all functioning is done by the system. The required messages are displayed at proper time. DUPLICACY As data is entered in different modules so considerations made so the no duplicate entry exist in the system.