1

DECLARATION

We hereby declare that this submission is our own work and that, to the best of our
knowledge and belief, it contains no material previously published or written by another
person nor material which to a substantial extent has been accepted for the award of any
other degree or diploma of the university or other institute of higher learning, except
where due acknowledgment has been made in the text.

Yash Bansal
Reema Jain
Sonam
Rahul
Bipul
Akshay
Amisha









2

ACKNOWLEDGEMENT

The satisfaction that accompanies that the successful completion of any task would be
incomplete without the mention of people whose ceaseless cooperation made it possible,
whose constant guidance and encouragement crown all efforts with success.
We are grateful and highly indebted to our project mentors, Mrs. Sunita Verma, and Mr.
Y.S. Tanwar, for their guidance, inspiration and constructive suggestions that helped us
in the completion of this project.
Our thanks and appreciations also go to our colleagues in developing the project and
people who have willingly helped us out with their abilities.

Yash Bansal
Reema Jain
Sonam
Rahul
Bipul
Akshay
Amisha








3

Table of Contents

S.No. Contents Page no.
1. Chapter-1:Introduction 4
2. Chapter-2: Technical &
Programming Requirements
6
3. Chapter-3 : Design 18
4. Chapter-4 : Implementation 21
5. Chapter-5 : Problems in existing
system
39
6. Solutions to existing problems 40
7. Chapter-6 : Coding 41
8. References 64









4

CHAPTER -1
INTRODUCTION

The Semiconductor Integrated Circuits Layout Design Act 2000 provides for protection
of Semiconductor Integrated Circuits Layout Design and for matters connected therewith
or incidental thereto. Government of India has established Semiconductor Integrated
Circuits Layout Design Registry (SICLDR) as the office for filings of application for
Semiconductor IC Layout Design Registration.

ABOUT REGISTRY
What is SICLDA?

Semiconductor Integrated Circuits Layout Design Registry (SICLDR) has been
established for registration of original Intellectual Property in Semiconductor Integrated
Circuits Layout Design under Semiconductor Integrated Circuits Layout-Design Act
(SICLDA) 2000.

Vision

Promotion of Semiconductor Integrated Circuits Layout-Design in the country.

Mission

Act as a catalyst for protection of Intellectual Property of Semiconductor Integrated
Circuit i.e. Layout-Designs.

Objectives

Protecting of Intellectual Property of Semiconductor Integrated Circuits and matters
connected therewith and incidental thereto.
5

Create awareness for protection of Intellectual Property of Semiconductor Integrated
Circuits Layout-Designs.

Functions

Protection of original Layout-Designs of Semiconductor Integrated Circuits as per the
provisions of the Semiconductor Integrated Circuits Layout- Design Act 2000.

Promote protection of Intellectual Property of Semiconductor Integrated Circuits
Layout-Designs.

Layout Designs Registration Benefits

Protects Intellectual Property (i.e. layout-design) of Semiconductor Integrated Circuits.
Gives EXCLUSIVE RIGHT to the creator of layout-design for 10 years.
EXCLUSIVE RIGHT enables the owner to commercially exploit the creation and in
case of infringement, get reliefs permitted under the Act.

SICLD Act & Rules

1) Semiconductor Integrated Circuits Layout Design Act 2000.
2) Rules for the Semiconductor Integrated Circuits Layout Design Act 2000.







6

CHAPTER 2
TECHNICAL AND PROGRAMMING
REQUIREMENT

2.1 VISUAL STUDIO
Microsoft Visual Studio is an integrated development environment (IDE) from Microsoft.
It is used to develop console and graphical user interface applications along with
Windows Forms or WPF applications, web sites, web applications, and web services in
both native code together with managed code for all platforms supported by Microsoft
Windows, Windows Mobile, Windows CE, .NET Framework, .NET Compact
Framework and Microsoft Silverlight.
Visual Studio includes a code editor supporting IntelliSense as well as code refactoring.
The integrated debugger works both as a source-level debugger and a machine-level
debugger. Other built-in tools include a forms designer for building GUI applications,
web designer, class designer, and database schema designer. It accepts plug-ins that
enhance the functionality at almost every levelincluding adding support for source-
control systems (like Subversion and Visual SourceSafe) and adding new toolsets like
editors and visual designers for domain-specific languages or toolsets for other aspects of
the software development lifecycle (like the Team Foundation Server client: Team
Explorer).
Visual Studio supports different programming languages by means of language services,
which allow the code editor and debugger to support (to varying degrees) nearly any
programming language, provided a language-specific service exists. Built-in languages
include C/C++[5] (via Visual C++), VB.NET (via Visual Basic .NET), C# (via Visual
C#), and F# (as of Visual Studio 2010[6]). Support for other languages such as M,
Python, and Ruby among others is available via language services installed separately. It
also supports XML/XSLT, HTML/XHTML, JavaScript and CSS. Individual language-
specific versions of Visual Studio also exist which provide more limited language
services to the user: Microsoft Visual Basic, Visual J#, Visual C#, and Visual C++. 5



7

2.1.1 .Net Framework
The .NET Framework (pronounced dot net) is a software framework developed by
Microsoft that runs primarily on Microsoft Windows. It includes a large library and
provides language interoperability (each language can use code written in other
languages) across several programming languages. Programs written for the .NET
Framework execute in a software environment (as contrasted to hardware environment),
known as the Common Language Runtime (CLR), an application virtual machine that
provides services such as security, memory management, and exception handling. The
class library and the CLR together constitute the .NET Framework.
The .NET Framework's Base Class Library provides user interface, data access, database
connectivity, web application development and network communications. Programmers
produce software by combining their own source code with the .NET Framework and
other libraries. The .NET Framework is intended to be used by most new applications
created for the Windows platform. Microsoft also produces an integrated development
environment largely for .NET software called Visual Studio.


2.1.2 IntelliSense Idea
Intelli-sense, in computer programming, generally short for intelligent sense or intelligent
code sense, is a programming environment that speeds up the process of coding
applications by reducing misunderstandings, typos, and other common mistakes.
Attempts to do this are usually done through auto completion popups when typing,
querying parameters of functions, query hints related to syntax errors, etc. Intelli-sense
serves as documentation and disambiguation for variable names, functions and methods
using reflection. Similar to other auto completion systems, Intelli-sense is a convenient
way to access descriptions of functions, particularly their parameter lists. It speeds up
software development by reducing the amount of name memorization needed and
keyboard input required. It also allows for less reference to external documentation as
interactive documentation on many symbols (i.e. variables and functions) in the active
scope appears dynamically in the form of tooltips while programming.



8




Implementation in Visual Studio
Intelli-sense appears in many program environments, including the most popular
implementation being Visual Studio's "IntelliSense". IntelliSense is Microsoft's popular
implementation of "intelligent sense" most notably featured in Visual Studio. IntelliSense
has entered a new phase of development with the unified Visual Studio.NET environment
first released in 2001, augmented by the more powerful introspection and code
documentation capabilities provided by the .NET framework. IntelliSense is now
supported by the Visual Studio editors for C++, C#, J#, Visual Basic, XML, HTML and
XSLT among others. As of Visual Studio 2005, IntelliSense is now activated by default
when the user begins to type, instead of requiring marker characters (though this behavior
can be turned off). The IDE has the capability of inferring a greater amount of context
based on what the developer is typing, to the point that basic language constructs such as
for and while are also included in the choice list.


9

2.1.3 Common Language Runtime (CLR)
The Common Language Runtime (CLR) is the virtual machine component of Microsoft's
.NET framework and is responsible for managing the execution of .NET programs. In a
process known as just-in-time compilation, the compiled code is converted into machine
instructions that, in turn, are executed by the computer's CPU. The CLR provides
additional services including memory management, type safety and exception handling.
All programs written for the .NET framework, regardless of programming language, are
executed by the CLR. It provides exception handling, garbage collection and thread
management. CLR is common to all versions of the .NET framework.


10

The CLR is Microsoft's implementation of the Common Language Infrastructure (CLI)
standard. The purpose of the Common Language Infrastructure (CLI) is to provide a
language-neutral platform for application development and execution, including
functions for exception handling, garbage collection, security, and interoperability. By
implementing the core aspects of the .NET Framework within the scope of the CLI, this
functionality will not be tied to a single language but will be available across the many
languages supported by the framework.
















11

2.2 ASP .NET
What is ASP.NET? ASP.NET stands for Active Server Pages .NET and is developed by
Microsoft. ASP.NET is used to create web pages and web technologies and is an integral
part of Microsofts .NET framework vision. As a member of the .NET framework,
ASP.NET is a very valuable tool for programmers and developers as it allows them to
build dynamic, rich web sites and web applications using compiled languages like VB
and C#.
ASP.NET is a server-side Web application framework designed for Web development to
produce dynamic Web pages. It was developed 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.
ASP.NET is a unified Web development model that includes the services necessary for
you to build enterprise-class Web applications with a minimum of coding. ASP.NET is
part of the .NET Framework, and when coding ASP.NET applications you have access to
classes in the .NET Framework. You can code your applications in any language
compatible with the common language runtime (CLR), including Microsoft Visual Basic
and C#. These languages enable you to develop ASP.NET applications that benefit from
the common language runtime, type safety, inheritance, and so on.
Web Forms are an ASP.NET technology that you use to create programmable Web
pages. Web Forms render themselves as browser-compatible HTML and script, which
allows any browser on any platform to view the pages. Using Web Forms, you create
Web pages by dragging and dropping controls onto the designer and then adding code,
similar to the way that you create Visual Basic forms. These server-side technologies are
important contributions to the development of the Web. Amazon.com, eBay.com, and
many other popular web sites use ASP.NET as the framework for their site; without
ASP.NET it would not be possible. 9




12

2.3 C# (C SHARP)
C# (pronounced "see sharp" or "C Sharp") is one of many .NET programming languages.
It is object-oriented and allows you to build reusable components for a wide variety of
application types. C# is a multi-paradigm programming language encompassing strong
typing, imperative, declarative, functional, procedural, generic, object-oriented (class-
based), and component-oriented programming disciplines. It was developed by Microsoft
within its .NET initiative. Its development team is led by Anders Hejlsberg. The most
recent version is C# 5.0, which was released on August 15, 2012.
C# is an elegant and type-safe object-oriented language that enables developers to build a
variety of secure and robust applications that run on the .NET Framework. You can use
C# to create traditional Windows client applications, XML Web services, distributed
components, client-server applications, database applications, and much, much more.
Visual C# provides an advanced code editor, convenient user interface designers,
integrated debugger, and many other tools to make it easier to develop applications based
on version 4.0 of the C# language and version 4.0 of the .NET Framework.
C# is an evolution of the C and C++ family of languages. However, it borrows features
from other programming languages, such as Delphi and Java. C# is an elegant and type-
safe object-oriented language that enables developers to build a variety of secure and
robust applications that run on the .NET Framework. You can use C# to create traditional
Windows client applications, XML Web services, distributed components, client-server
applications, database applications, and much, much more. Visual C# provides an
advanced code editor, convenient user interface designers, integrated debugger, and many
other tools to make it easier to develop applications based on version 4.0 of the C#
language and version 4.0 of the .NET Framework.
C# syntax is highly expressive, yet it is also simple and easy to learn. The curly-brace
syntax of C# will be instantly recognizable to anyone familiar with C, C++ or Java.
Developers who know any of these languages are typically able to begin to work
productively in C# within a very short time. C# syntax simplifies many of the
complexities of C++ and provides powerful features such as nullable value types,
enumerations, delegates, lambda expressions and direct memory access, which are not
found in Java. C# supports generic methods and types, which provide increased type
safety and performance, and iterators, which enable implementers of collection classes to
define custom iteration behaviors that are simple to use by client code. Language-
Integrated Query (LINQ) expressions make the strongly-typed query a first-class
language construct.

13

2.4 MICROSOFT SQL SERVER 2012 EXPRESS
LOCALDB
As a database, it is a software product whose primary function is to store and retrieve
data as requested by other software applications, be it those on the same computer or
those running on another computer across a network. Microsoft Visual Studio includes
native support for data programming with Microsoft SQL Server. It can be used to write
and debug code to be executed by SQL CLR. It also includes a data designer that can be
used to graphically create, view or edit database schemas. Queries can be created either
visually or using code. From visual studio 2008 onwards, provides intellisense for SQL
queries as well. It is basically a relational database system management developed by
Microsoft. Its primary query languages are T-SQL and ANSI SQL.


Microsoft SQL Server 2012 Express LocalDB is an execution mode of SQL Server
Express targeted to program developers. LocalDB installation copies a minimal set of
files necessary to start the SQL Server Database Engine. Once LocalDB is installed,
developers initiate a connection by using a special connection string. When connecting,
the necessary SQL Server infrastructure is automatically created and started, enabling the
application to use the database without complex or time consuming configuration tasks.
Developer Tools can provide developers with a SQL Server Database Engine that lets
them write and test Transact-SQL code without having to manage a full server instance of
SQL Server. An instance of SQL Server Express LocalDB is managed by using the
14

SqlLocalDB.exe utility. SQL ServerExpress LocalDB should be used in place of the SQL
Server Express user instance feature which is deprecated.
LocalDB is created specifically for developers. It is very easy to install and requires no
management, yet it offers the same T-SQL language, programming surface and client-
side providers as the regular SQL Server Express. In effect the developers that target
SQL Server no longer have to install and manage a full instance of SQL Server Express
on their laptops and other development machines. Moreover, if the simplicity (and
limitations) of LocalDB fit the needs of the target application environment, developers
can continue using it in production, as LocalDB makes a pretty good embedded database
too.

GRAPHICAL TABLE DSIGNER
Before this version of the visual studio, SQL has many limitations in terms of its
navigation and data displaying capabilities. The new Visual Studio 2012 Table Designer
lets you define a table graphically, making it easier to understand its related objects. The
new Table Designer is bi-directional: Changing the table definition through a graphical
interface updates the Script pane. Likewise, changes to the Script pane update the
graphical designer. The new Table Designer is available only for databases in the SQL
Server 2012 format which is available in visual 2012.



15

2.5 HTML
HyperText Markup Language (HTML) is the main markup language for creating web
pages and other information that can be displayed in a web browser.
HTML is written in the form of HTML elements consisting of tags enclosed in angle
brackets (like <html>), within the web page content. HTML tags most commonly come
in pairs like <h1> and </h1>, although some tags represent empty elements and so are
unpaired, for example <img>. The first tag in a pair is the start tag, and the second tag is
the end tag (they are also called opening tags and closing tags). In between these tags
web designers can add text, further tags, comments and other types of text-based content.
The purpose of a web browser is to read HTML documents and compose them into
visible or audible web pages. The browser does not display the HTML tags, but uses the
tags to interpret the content of the page.
HTML elements form the building blocks of all websites. HTML allows images and
objects to be embedded and can be used to create interactive forms. It provides a means
to create structured documents by denoting structural semantics for text such as headings,
paragraphs, lists, links, quotes and other items. It can embed scripts written in languages
such as JavaScript which affect the behaviour of HTML web pages.
Web browsers can also refer to Cascading Style Sheets (CSS) to define the appearance
and layout of text and other material. The W3C, maintainer of both the HTML and the
CSS standards, encourages the use of CSS over explicit presentational HTML.








16

2.6 CSS (CASCADING STYLE SHEETS)
Cascading Style Sheets (CSS) is a style sheet language used for describing the
presentation semantics (the look and formatting) of a document written in a markup
language. Its most common application is to style web pages written in HTML and
XHTML, but the language can also be applied to any kind of XML document, including
plain XML, SVG and XUL.
CSS is designed primarily to enable the separation of document content (written in
HTML or a similar markup language) from document presentation, including elements
such as the layout, colors, and fonts.[1] This separation can improve content accessibility,
provide more flexibility and control in the specification of presentation characteristics,
enable multiple pages to share formatting, and reduce complexity and repetition in the
structural content (such as by allowing for tableless web design). CSS can also allow the
same markup page to be presented in different styles for different rendering methods,
such as on-screen, in print, by voice (when read out by a speech-based browser or screen
reader) and on Braille-based, tactile devices. It can also be used to allow the web page to
display differently depending on the screen size or device on which it is being viewed.
While the author of a document typically links that document to a CSS file, readers can
use a different style sheet, perhaps one on their own computer, to override the one the
author has specified.
CSS specifies a priority scheme to determine which style rules apply if more than one
rule matches against a particular element. In this so-called cascade, priorities or weights
are calculated and assigned to rules, so that the results are predictable.
The CSS specifications are maintained by the World Wide Web Consortium (W3C).
Internet media type (MIME type) text/css is registered for use with CSS by RFC 2318
(March 1998), and they also operate a free CSS validation service.






17

2.7 JAVASCRIPT
JavaScript (JS) is an interpreted computer programming language. As part of web
browsers, implementations allow client-side scripts to interact with the user, control the
browser, communicate asynchronously, and alter the document content that is displayed.
It has also become common in server-side programming, game development and the
creation of desktop applications.
JavaScript is a prototype-based scripting language with dynamic typing and has first-
class functions. Its syntax was influenced by C. JavaScript copies many names and
naming conventions from Java, but the two languages are otherwise unrelated and have
very different semantics. The key design principles within JavaScript are taken from the
Self and Scheme programming languages. It is a multi-paradigm language, supporting
object-oriented, imperative, and functional programming styles.
The application of JavaScript to uses outside of web pagesfor example, in PDF
documents, site-specific browsers, and desktop widgetsare also significant. Newer and
faster JavaScript VMs and frameworks built upon them (notably Node.js) have also
increased the popularity of JavaScript for server-side web applications.
JavaScript was formalized in the ECMA Script language standard and is primarily used
as part of a web browser (client-side JavaScript). This enables programmatic access to
computational objects within a host environment.











18

CHAPTER 3
DESIGN

This chapter basically explains the how the whole structure of the project was made from
scratch and the major challenges that we faced during the project.

3.1 DESNING OF TEMPLATE
ASP.NET master pages allow you to create a consistent layout for the pages in your
application. A single master page defines the look and feel and standard behavior that
you want for all of the pages (or a group of pages) in your application. You can then
create individual content pages that contain the content you want to display. When users
request the content pages, they merge with the master page to produce output that
combines the layout of the master page with the content from the content page. A master
page is an ASP.NET file with the extension .master (for example, MySite.master) with a
predefined layout that can include static text, HTML elements, and server controls.



19

Master pages provide functionality that developers have traditionally created by copying
existing code, text, and control elements repeatedly; using framesets; using include files
for common elements; using ASP.NET user controls; and so on.

Advantages of master pages include the following:
They allow you to centralize the common functionality of your pages so that you
can make updates in just one place.

They make it easy to create one set of controls and code and apply the results to a
set of pages. For example, you can use controls on the master page to create a
menu that applies to all pages.

They give you fine-grained control over the layout of the final page by allowing
you to control how the placeholder controls are rendered.

They provide an object model that allows you to customize the master page from
individual content pages.










20

3.2 DESIGN OF DATABASE
A government website has lots of data to be maintained about all the submitted forms and
the registered users of the site. Also the database of every user needs to be maintained
ever time a form is submitted. Hence we have used the SQL Database which is integrated
in the Visual Studio 2012. Also with the help of the graphical my SQL database designer,
it becomes fairly easy to maintain, create and update the databases at a later time.

Different fields used in the database by us:-
1) Name: It stores the names of different users who submit the forms on the website.
2) Address: This stores the address of the user who tries submitting a form on the
website.
3) ID: This stores the ID.
4) Location: This stores the location from where the form is being submitted.
5) Title: This stores the title of the form submitted.












21

CHAPTER 4
IMPLEMENTATION

The whole project development has been developed in many phases starting from setting
up of the project to the publishing the website to the server. Hence following phases has
been described in detailed.

PHASE 0: SETTING UP THE ENVIRONMENT
Before start building the project there are many softwares and their hardware
requirements that needs to be met for the visual studio 2012. If any of the requirements is
not met then it might create problems in the future works. So its better to carefully look
at all the needs of the softwares used.
There are many different versions of the visual studio 2012 form which you can choose.
But which is the best for developer for web development. Hence it is very important to
select the best visual studio version which has rich web capabilities.
Visual Studio Ultimate 2012: Visual Studio Ultimate 2012 is the comprehensive
ALM offering for organizations developing and operating highly scalable
software applications and services.

Visual Studio Premium 2012: Visual Studio Premium 2012 offers an integrated
ALM solution to bring together stakeholders, users, and software development
functions to deliver compelling applications as a unified team.

Visual Studio Professional 2012 : Visual Studio Professional 2012 is a unified
development experience that enables developers to create multi-tier applications
across the web, cloud, and devices.

22

Visual Studio Test Professional 2012 90-day trial: Visual Studio Test Professional
2012 is ideal for testers, business analysts, product managers, and other
stakeholders who need team collaboration tools, but not a full development IDE.

Hence from the above versions of the visual studio 2012, we worked upon the visual
studio 2012 ultimate edition since this versions is the full packed version of the Microsoft
visual studio 2012 and has all required capabilities and database integration that was
required for the project to be made. In Microsoft Visual Studio Ultimate 2012, we found
the agile processes, sophisticated management tools, and robust testing infrastructure that
are essential for creating fast results and delighted customers.


















23

HARDWARE REQUIREMENTS FOR VISUAL STUDIO
2012:

1.6 GHz or faster processor

1 GB of RAM (1.5 GB if running on a virtual machine)

10 GB (NTFS) of available hard disk space

5400 RPM hard drive

DirectX 9-capable video card running at 1024 x 768 or higher displays.

SUPPORTED ARCHITECTURES:

32-bit (x86)

64-bit (x64)




24

SUPPORTED OPERATING SYSTEM FOR VISUAL
STUDIO 2012:













25

PHASE 1: DESIGNING THE TEMPLATE
The template designing of the website has been achieved using CSS and HTML. Since
asp.et supports different languages to be used with asp.net hence all the HTML code was
written in .aspx pages and we dont need to have HTML pages for using CSS. In this
website we basically have used external CSS. Using external CSS, it was easy to perform
design in a separate file from the asp.net files. Because of this, code can be maintained
easily and efficiency of the code also increases since it separates the designing from the
logic implementation. Also debugging at a later time can be carried out easily and any
changes in the template of the website can be carried out easily without changing the
whole code. We just need to make the changed in CSS file.





26

To implement the CSS code in the HTML file we need to link the both files together by
pasting the link of the CSS file in the HTML code. Template designing was carried in the
following steps:



Initially the <div> tags are implemented in the HTML code and the web page is divided
in the various categories: header, middle and the footer part. The header part basically
contains the company logo and its name.




Between the header and middle div tag we have a navigation bar which allows user to
navigate through the website and choose among the various products and add them to the
cart.
27



After that the middle content is divided into sidebars and middle content which contains
the information about the product. The sidebar filters the products according to the
different brands and helps user to choose products from the brand which they prefer.
28



After that a footer part is placed at the bottom of the website which contains the
copyrights information of the website name and its logo.



29

The above template has been designed keeping in mind the requirements of a shopping
website and user must be able to navigate the website easily without any problem. The
user can even choose products of its preferable brand and will be presented with the
whole information about the product.
Since there are many pages inside a website and it is very difficult to design a template
for every page of the website. Also at a later time if some changes need to be made in the
design of the website or up gradation needs to be done then it is very difficult to again
make changes in the template design of the every page. Hence some template design is
applied to the every page with the help of master page.



















30

PHASE 2: IMPLEMENTING ASP.NET
Once the template has been made and the design of the website is ready now its the time
for using the asp.net web forms to do the server side scripting and add user interaction to
our web pages. Now its time to implement asp.net in our template so as to add dynamic
response to the website and user can easily navigate through the website and can make its
purchase easily.

1) Using Content Place Holder
Now many content placeholders are implemented in the master page to that part of our
template where we need to change the content specific to a particular page. ASP.NET
master pages allow you to create a consistent layout for the pages in your application. A
single master page defines the look and feel and standard behaviour that you want for all
of the pages (or a group of pages) in your application. We can then create individual
content pages that contain the content you want to display. When users request the
content pages, they merge with the master page to produce output that combines the
layout of the master page with the content from the content page.
In addition to static text and controls that will appear on all pages, the master page also
includes one or more ContentPlaceHolder controls. These placeholder controls define
regions where replaceable content will appear. In turn, the replaceable content is defined
in content pages. After you have defined the ContentPlaceHolder controls, a master page
might look like the following.
31



Here now you can see that two content place holders have been defined and hence both
the area of the master page template now can be changed according to the page
requirements.
One ContentPlaceHolder has been defined inside the right sidebar of our master page
template. This now allows you to have different content in the different sidebar of the
multiple pages. This is helpful since on products page we need to have a sidebar which
filters the products according to multiple brands but on the login page there is no
requirement for this filter and hence the sidebar content can be left empty
Now second ContentPlaceHolder has been placed inside the content tag which is again
very much acceptable. Since the content on every page cant be same as the other one and
hence we need to have a place holder there also.
32

This eases down our work to a great extent and we can very easily edit the every part of
the template as required for different pages.

2) Using Datalist
This indeed is a very helpful control available in asp.net. The DataList Web server
control displays data in a format that you can define using templates and styles. The
DataList control is useful for data in any repeating structure, such as a table. The DataList
control can display rows in different layouts, such as ordering them in columns or rows.
Optionally, you can configure the DataList control to allow users to edit or delete
information. You can also customize the control to support other functionality, such as
selecting rows. You use templates to define the layout of data items by including HTML
text and controls. For example, you might use a Label Web server control in an item to
display a field from the data source.
The DataList Web server control must be bound to a data source. The most common data
source is a data source control, such as a SqlDataSource or ObjectDataSource control.
Alternatively, you can bind a DataList control to any class that implements the
IEnumerable interface, which includes the ADO.NET datasets (the DataSet class), data
readers (the SqlDataReader or OleDbDataReader classes), or most collections. When
binding data, you specify a data source for the DataList control as a whole. When you
add other controls to this control for example, labels or text boxes in list items you
can bind the child controls' properties to fields in the current data item.

DIFFERENT CONTROLS USED IN DATALIST:
ItemTemplate: Conatins the HTML elements and octols to render once for each
row in the database.

AlternateItemTemplate: Contains HTML elements a controls to render once for
each other row inn the data source. Typically, you use this template to create a
different look for the alternating rows such as different background colour than
the color specified in the ItemTemplate property.

33

SelectedItemTemplate: Contains the elements to render when the user selects the
item in the DataList control.

EditItemTemplate: Specifies the layout of an item when it is in edit mode. This
template typically contains editing controls such as TextBox.

HeaderTemplate and FooterTempate: Contains the text and controls to render t
the beginning and the end of the last respectively.

EVENTS:
The DataList control supports several events. One of them, the ItemCreated event, gives
you a way to customize the item-creation process at run time. The ItemDataBound event
also gives you the ability to customize the DataList control, but after the data is available
for inspection. For example, if you were using the DataList control to display a to-do list,
you could display overdue items in red text, completed items in black text, and other
tasks in green text. Either event can be used to override formatting from the template
definition.
The remaining events are raised in response to button clicks in list items. They are
designed to help you respond to the most commonly used functionality of the DataList
control. Four events of this type are supported:
EditCommand
DeleteCommand
UpdateCommand
CancelCommand
To cause these events to be raised, add Button, LinkButton, or ImageButton controls to
the templates in the DataList control and set the buttons' CommandName property to a
keyword, such as edit, delete, update, or cancel. When a user clicks a button in an item,
the event is sent to the button's container the DataList control. The exact event that the
button raises depends on the value of the CommandName property of the button that was
clicked. For example, if the CommandName property of a button is set to edit, the button
raises an EditCommand event when clicked. If the CommandName property is set to
delete, the button raises a DeleteCommand event, and so on.
34

The DataList control also supports the ItemCommand event that is raised when a user
clicks a button that does not have a predefined command, such as edit or delete. You can
use this event for custom functionality by setting a button's CommandName property to a
value that you need and then testing for it in the ItemCommand event handler.
The datalist has been used mainly on two pages of our project. First on the products page
where the different products along with their images are need to be shown along with
their prices and name. Hence instead of using HTML and yourself putting the images on
the webpage, datalist is a very convenient option that can show all your products along
with the required information and can be customized in the whatever look you want.
Following code shows you the use of datalist for displaying the products directly from the
database:


35

Here as you can see different item template has been defined inside the datalist along
with the events. HeaderTemplate and FooterTemplate have been used to show the logo of
the brand on which the product is displaying. We have also used some html tags inside
the ItemTemplate tag for the required proper format for displaying the products as grids.
Also the use of the datalist has been very much implemented on the product details page.
All the information has been stored inside the database including product specification
and hence it is not every time necessary too design a separate page for every new product
added.


36

4.2 IMPLEMENTATION OF DATAGRID
The GridView is a convenient control for displaying tabular data with ASP.NET. When
used in web applications which target the desktop browser it works very well, however,
the user experience is not always optimal when using these same applications on smaller
screen devices such as tablets and phones. Tables of data are usually quite wide and they
don't scale down very well for small screens. The page layout can get messed up and the
user often has to zoom in and out and scroll around the screen to use the application.
Grid view basically helps in displays the data from the database in the form of tables. It
also provides us with these basic options like delete, cancel, update and edit from the
table. Hence changes can be made in the table at the run time and there is no need to
change in the database every time. Following are the various events that have been used
in the gridview control of as.net.


37

4.3 BASIC ASP.NET CONTROLS USED
While designing login page or register page, there are certain validations need to be
specified which the user must satisfy otherwise he should be informed about the mistake
he has made and no field need to be blank. Hence there are certain defined controls in the
asp.net that helps to achieve that and prompts the user every time he leaves something
blank or fills something in improper format.



The validation server control in the above table is used to check validation.






38

PHASE 3: IMPLEMENTING C# AND CONNECT
TO DATABASE
Whenever a new user tries to submit a form, then the user is required to fill all the
required details meeting the validation. The record of every user must be stored in the
SQL database and record of every user is maintained. Now whenever a user logs in to his
account then its details get stored in the database.



39

CHAPTER-5
PROBLEMS IN EXISTING SYSTEM

Risk of mismanagement and of data when the project is under development.

Less Security.

No proper coordination between different Applications and Users.

Fewer Users - Friendly.

Manual system need man power a lot.

Communication between customer and owner is not directly.

It is limited to a single system.

It is less user-friendly.

It is having lots of manual work (Manual system does not mean that you are working
with pen and paper, it also include working on spread sheets and other simple software's).

The present system is very less secure.

It is unable to generate different kinds of report.

Time Consuming Process for search.

Creating problem to maintain records.

40

SOLUTION OF THESE PROBLEMS:-

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

User friendliness is provided in the application with various controls.

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

Readily upload the latest updates.

There is no risk of data mismanagement at any level while the project development is
under process.

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













41

CHAPTER-6
CODING

Coding of a website in asp.net is done in two phases:
Design phase
Connectivity phase

Design phase:
In a design phase the designing of the website is done so as to improve the way a website
is displayed to the users. In the designing phase :-
1. The components that are to be displayed in a page are decided and arranged on
the page.
This phase involves dragging and dropping buttons and textboxes and all the required
tools from the toolbox and placing them on the web form, keeping space for the images
and advertisements and deciding header and footer, content and place where ads are to be
displayed on all the pages in the website and if required , using the master page to add
same content in background of all the selected pages. Here person is not concerned of
the implementation or working. This is the initial phase where only the layout of the page
is made.

2. Adding working and events to the various tools like: buttons, calenders etc.
In this phase we decide the working of the events at the clicks of various buttons or
loading of the page. Here, in this phase after designing we decide which page is to be
displayed on the click of which button to add link in various pages of the website.
Like:
If we create a button in asp.net web form like:
<asp:button id=button1 runat=server width=56px height=40px
onclick=button1_click>
42

And then we add the definition to the event onclick described at the time of creation of
the button in the codesource file i.e .cs file as:

public void button1_click (object sender, eventargs e)
{
textbox1.text = this is the body of the event on click of button;
}
Like wise we add the definitions to various events.

3. Adding jquery to the website i.e to add animations to the website
jquery is the language used in web forms to add animations to the web site to make it
look more attractive to the users . We can hide or show the selected content on hover of
mouse or animate a <div> tag to expand in size or move on click or hover of a button or
anything. This is used largely to animate the images on the web site that are displayed in
a particular box.
Like:
Consider a tag:
<div id=div1 style=background-
color:green;left:0px;top:100px;height:200px;width:400px>
</div>
Then we can add jquery so that it expands on the hover of mouse like:
$(document).ready(function(){
$(#div1).hover(function(){
$(#div1).animate({height:500px,width:600px},3000);
});
});
43

Now this <div> tag expands on hover of mouse. like this we can add various events in
jquery to make attractive.

Connectivity phase:
In this phase we can add connectivity i.e sql database or any database to the website for
storing content and adding dynamicity to the page and making changes in web.config
file. This phase includes:
1.Adding database to store the information relating login of a user or any other info
that needs to be stored regarding users that visit the website.
There are two classes in asp.net that help implement addition of database in the web site
they are:
system.data
system.data.sqlclient

To add the database in sql we have two options:
use the database provided by asp.net i.e. local database
to add the external database made somewhere else outside

To make changes on the info in the database, we use sql queries and function that
implement those queries are:
sqlcommand(string query, connection);
Here query represents the sql query and the connection parameter takes the name of
connection defined by: sqlconnection()
Like:
sqlconnection con = new sqlconnection(@<connection-string>);
sqlcommand() represents the online mode where on each query to the database the
system checks whether database is available or not.

44

It is followed by:
1. sqldataadapter(string query,connection);
This is also like sqlcommand() but the difference lies in the mode. sqldataadapter() works
in offline mode i.e the system checks only once for availability of the database not every
time the query is made to the database.
2. Make changes in the web.config file
web.config file is the configuration file in asp.net . This file exists for every root directory
and can be added for further sub directories. This file includes changes made concerning
the security of the web site. Some of the changes made include.
adding <authentication>
adding <sessionstate> if implementing sessions in asp.net















45

Code for styling of home page:-
body {
}

#main_container {
height:800px;
width:1000px;
margin-left:150px;
}

#header {
background-color:brown;
height:100px;
width:inherit
}

#middle {
min-height:500px;
width:inherit;
}

#middle_content {
height:inherit;
width:850px;
padding:5px 10px 5px 40px;
46

margin-left:80px;

}


/*---------------- left sidebar----------------------*/

#left_sidebar
{
min-height:600px;
width:150px;
border: thin;
float:left;
border-style:ridge;
border-color: silver;
background-color: ButtonShadow;
}


ul.left_menu{
width:200px;
padding:0px;
margin:0px;
list-style:none;
}
47

ul.left_menu li{
margin:0px;
list-style:none;
}
ul.left_menu li a{
width:175px;
height:30px;display:block; border-bottom:1px #e4e4e4 dashed; background-color: white;
text-decoration:none;color:#504b4b;padding:5px 0 0 25px; line-height:25px;
}
ul.left_menu li a:hover{
color:#000; background-color: crimson;
}













48

LD1 Code:-
<%@ Page Title="" Language="C#" MasterPageFile="~/master.Master"
AutoEventWireup="true" CodeBehind="ld1.aspx.cs" Inherits="WebApplication1.ld3"
%>

<asp:Content ID="Content1" ContentPlaceHolderID="ContentPlaceHolder1"
runat="server">


<h2 style="padding-left:18em">FORM LD1</h2><br />

<h2 style="padding-left:8em">APPLICATION FOR REGISTRATION OF LAYOUT
DESIGN</h2>

<p>Application is hereby made for the registration of the layout design <asp:TextBox
ID="title" runat="server" Width="500" ></asp:TextBox>
in the name of<asp:TextBox ID="name" runat="server" Width="300"
></asp:TextBox>
whose address is <asp:TextBox ID="address" runat="server" Width="500"
></asp:TextBox>
is claim to be the proprietor theeof in respect of the said layout-design.
<br /><br />Enndorsed herewith is the duly completed statement of particulars
relating to the layout-design.
<br /> <br /> The particulars set forth in the enclosed statement of the paticulars
are true to the best of my/our knowledge, information and beleief.
<br /><br />To
<br />The Registrar Semi-conductor Integrated Circuits layout Deisgn, Office of
the Semi-Conductor Integrated ciruits Layout-Design Resgistery at
<asp:TextBox ID="location" runat="server" Width="500" ></asp:TextBox>
49

</p>

</asp:Content>

BACKENED CONNECTIVITY WITH MYSQL DATABASE USING C#

using System;
using System.Collections.Generic;
using System.Linq;
using System.Web;
using System.Web.UI;
using System.Web.UI.WebControls;

namespace WebApplication1
{
public partial class ld3 : System.Web.UI.Page
{
protected void Page_Load(object sender, EventArgs e)
{

}
}
}

************************************************************************
50

//------------------------------------------------------------------------------
// <auto-generated>
// This code was generated by a tool.
//
// Changes to this file may cause incorrect behavior and will be lost if
// the code is regenerated.
// </auto-generated>
//------------------------------------------------------------------------------

namespace WebApplication1 {


public partial class ld3 {

/// <summary>
/// title control.
/// </summary>
/// <remarks>
/// Auto-generated field.
/// To modify move field declaration from designer file to code-behind file.
/// </remarks>
protected global::System.Web.UI.WebControls.TextBox title;

/// <summary>
/// name control.
51

/// </summary>
/// <remarks>
/// Auto-generated field.
/// To modify move field declaration from designer file to code-behind file.
/// </remarks>
protected global::System.Web.UI.WebControls.TextBox name;

/// <summary>
/// address control.
/// </summary>
/// <remarks>
/// Auto-generated field.
/// To modify move field declaration from designer file to code-behind file.
/// </remarks>
protected global::System.Web.UI.WebControls.TextBox address;

/// <summary>
/// location control.
/// </summary>
/// <remarks>
/// Auto-generated field.
/// To modify move field declaration from designer file to code-behind file.
/// </remarks>
protected global::System.Web.UI.WebControls.TextBox location;
}
52

}
LD2 code:-
<%@ Page Title="" Language="C#" MasterPageFile="~/master.Master"
AutoEventWireup="true" CodeBehind="ld2.aspx.cs" Inherits="WebApplication1.ld2"
%>
<asp:Content ID="Content1" ContentPlaceHolderID="ContentPlaceHolder1"
runat="server">
</asp:Content>

************************************************************************
using System;
using System.Collections.Generic;
using System.Linq;
using System.Web;
using System.Web.UI;
using System.Web.UI.WebControls;

namespace WebApplication1
{
public partial class ld2 : System.Web.UI.Page
{
protected void Page_Load(object sender, EventArgs e)
{

}
}
53

}
************************************************************************
//------------------------------------------------------------------------------
// <auto-generated>
// This code was generated by a tool.
//
// Changes to this file may cause incorrect behavior and will be lost if
// the code is regenerated.
// </auto-generated>
//------------------------------------------------------------------------------

namespace WebApplication1
{


public partial class ld2
{
}
}





54


LD3 Code:-
<%@ Page Title="" Language="C#" MasterPageFile="~/master.Master"
AutoEventWireup="true" CodeBehind="ld3.aspx.cs" Inherits="WebApplication1.ld31"
%>
<asp:Content ID="Content1" ContentPlaceHolderID="ContentPlaceHolder1"
runat="server">
</asp:Content>
************************************************************************
using System;
using System.Collections.Generic;
using System.Linq;
using System.Web;
using System.Web.UI;
using System.Web.UI.WebControls;

namespace WebApplication1
{
public partial class ld31 : System.Web.UI.Page
{
protected void Page_Load(object sender, EventArgs e)
{

}
}
}
55


************************************************************************
//------------------------------------------------------------------------------
// <auto-generated>
// This code was generated by a tool.
//
// Changes to this file may cause incorrect behavior and will be lost if
// the code is regenerated.
// </auto-generated>
//------------------------------------------------------------------------------

namespace WebApplication1
{


public partial class ld31
{
}
}





56


LD4 code:-
<%@ Page Title="" Language="C#" MasterPageFile="~/master.Master"
AutoEventWireup="true" CodeBehind="ld4.aspx.cs" Inherits="WebApplication1.ld4"
%>
<asp:Content ID="Content1" ContentPlaceHolderID="ContentPlaceHolder1"
runat="server">
</asp:Content>
************************************************************************
using System;
using System.Collections.Generic;
using System.Linq;
using System.Web;
using System.Web.UI;
using System.Web.UI.WebControls;

namespace WebApplication1
{
public partial class ld4 : System.Web.UI.Page
{
protected void Page_Load(object sender, EventArgs e)
{

}
}
}
57

************************************************************************
//------------------------------------------------------------------------------
// <auto-generated>
// This code was generated by a tool.
//
// Changes to this file may cause incorrect behavior and will be lost if
// the code is regenerated.
// </auto-generated>
//------------------------------------------------------------------------------

namespace WebApplication1
{


public partial class ld4
{
}
}





58


LD5 code:-
<%@ Page Title="" Language="C#" MasterPageFile="~/master.Master"
AutoEventWireup="true" CodeBehind="ld5.aspx.cs" Inherits="WebApplication1.ld5"
%>
<asp:Content ID="Content1" ContentPlaceHolderID="ContentPlaceHolder1"
runat="server">
</asp:Content>
************************************************************************
using System;
using System.Collections.Generic;
using System.Linq;
using System.Web;
using System.Web.UI;
using System.Web.UI.WebControls;

namespace WebApplication1
{
public partial class ld5 : System.Web.UI.Page
{
protected void Page_Load(object sender, EventArgs e)
{

}
}
}
59

************************************************************************

//------------------------------------------------------------------------------
// <auto-generated>
// This code was generated by a tool.
//
// Changes to this file may cause incorrect behavior and will be lost if
// the code is regenerated.
// </auto-generated>
//------------------------------------------------------------------------------

namespace WebApplication1
{


public partial class ld5
{
}
}





60


Master page(Styling) code:-
using System;
using System.Collections.Generic;
using System.Linq;
using System.Web;
using System.Web.UI;
using System.Web.UI.WebControls;

namespace WebApplication1
{
public partial class master : System.Web.UI.MasterPage
{
protected void Page_Load(object sender, EventArgs e)
{

}
}
}
************************************************************************

//------------------------------------------------------------------------------
// <auto-generated>
// This code was generated by a tool.
61

//
// Changes to this file may cause incorrect behavior and will be lost if
// the code is regenerated.
// </auto-generated>
//------------------------------------------------------------------------------

namespace WebApplication1 {


public partial class master {

/// <summary>
/// form1 control.
/// </summary>
/// <remarks>
/// Auto-generated field.
/// To modify move field declaration from designer file to code-behind file.
/// </remarks>
protected global::System.Web.UI.HtmlControls.HtmlForm form1;

/// <summary>
/// ContentPlaceHolder1 control.
/// </summary>
/// <remarks>
/// Auto-generated field.
62

/// To modify move field declaration from designer file to code-behind file.
/// </remarks>
protected global::System.Web.UI.WebControls.ContentPlaceHolder
ContentPlaceHolder1;
}
}
















63




64

REFERENCES

Alan Simpson, HTML Publishing Bible


ASP.NET 3.5 by CMC Academy


Peter& John Kent, Netscape Java Script


Previous year reports


http://www.microsoft.com/visualstudio/eng#products/

http://www.microsoft.com/visualstudio/eng/visual-studio-2013

http://www.slideshare.net/Thenmurugeshwari/architecture-of-net-framework

http://www.packtpub.com/article/er-diagrams-domain-model-n-layer-architecture-
asp.net3.5-part1

http://en.wikipedia.org/wiki/HTML

http://api.jquery.com/html/

http://www.asp.net/