A PRACTICAL TRAINING SEMINAR REPORT

ON

“UNIVERSITY WEBSITE”

JAIPUR NATIONAL UNIVERSITY, JAIPUR

(A Venture of Seedling Group of Institutions)

SUBMITTED IN PARTIAL FULFILLMENT OF THE REQUIREMENT FOR THE

AWARD OF THE DEGREEE OF

BACHELOR OF TECHNOLOGY

Session-2010-2011

SUBMITTED TO:- SUBMITTED BY:-

Mr. PRASHANT SAHAY ABHINEET KUMAR

H.O.D (COMPUTER SCIENCE DEPT.) BRANCH-C S

Mrs. ANJU GAUTAM ROLL NO:5CS-01

LECTURER (C S DEPT.)
 JAIPUR NATIONAL UNIVERSITY, JAIPUR

(A Venture of Seedling Group of Institutions)

CANDIDATE’S DECLARATION

I hereby certify that the work which is being presented in the report entitled “ UNIVERSITY
WEBSITE ” by “ABHINEET KUMAR” in partial fulfilment of requirements for the award of
degree of B.Tech. (3rd year & CS) submitted in the Department of Computer Science Engg. at
Jaipur National University, Jaipur is an authentic record of my own work carried out during a
period from 06 – 06 – 2010 to 07 – 07 – 2010 under the supervision of “MR. RAJAT
GOYAL”.

Signature of the Student

The B.Tech (3rd year CS) seminar presentation of (ABHINEET KUMAR) has been held on –
10 – 2010 and accepted.

Signature of Internal Examiner1 Signature of Internal Examiner2

 ACKNOWLEDGEMENT

I would like to thanks Mr. Prashant SahaI Saxena, H.O.D Computer Science Department,
Mrs. Amju Gautam , Lecturer , Computer Department and all the faculty members of
Computer Science department for their efforts and constant co-operation which is the most
significant factor in the accomplishment of my industrial training.

I do extend my heartfull thanks to Mr. Rajat Goyal for providing me this opportunity to be
a part of this esteemed organization.

I am extremely grateful to all the technical staff for their co-operation and guidance that
helped me a lot during the course of training. I have learned a lot under working them
and I will always be indebted of them for this value addition in me.
 ABSTRACT
This project relates to the designing of a universities website that is “JAIPUR NATIONAL
UNIVERSITY” by working on ASP.NET and C# in visual studio 2008.The website contains all
the required information’s and features usually provided by a universities website.

It gives the detailed overview of the university which includes the glimpses of the campus,
details of academic collaboration with various universities , placements and training
information’s including the list of all successfully placed students so far and all the necessary
messages and announcements including the message from the CHANCEELLOR.

Home page of the website contains all the necessary and relevant links to the various sections of
the website such as ADMISSIONS which contains the latest announcements regarding the
admission procedures and entrance exam results, whereas COURSES OFFERED tells you about
the various courses being run by the university. Similarly ACADEMICS section makes you
familiar with the universities way of teaching. Apart from all there a separate link for
REGISTRATION is provided for the students to get enrolled to the websites and further use the
LOGIN option to access their personal profiles which would includes their personal and
academic information’s. Online Examinations for the university will also be held on this website
only. Finally the link CONTACT US can be used to contact, ask and give their suggestions and
opinions to the university.

The REGISTRATION and LOGIN facility the main features of the website. Students fill in the
required information’s in online form in order to get registered and once registered they would
be provided with a USERNAME and PASSWORD in the LOGIN section which they utilize to
view their personal academic records. While those eligible for the ONLINE
EXAMINATION’S , have to attempt ten objective type questions related to their course and the
scores of the examination would be declared instantly whereas admission information can
checked later on in the ADMISSION’S section.

Thus the above abstract summarizes all the features being provided by the universities website.
 CERTIFICATE

This is to certify that the mini project entitled ‘UNIVERSITY WEBSITE’ being submitted by
Mr. ABHINEET KUMAR (5 CS 01) in partial fulfillment of the requirement for the award of
degree of B Tech of the JAIPUR NATIONAL UNIVERSITY, is a record of bona fide work
carried out by him under my supervision.

Place : JAIPUR

Date : / /2010

Project Guide: Mr. Raj Pratap Singh

Project Coordinator: Mr. Rajat Goyal

Director: Mr. Prashant Sahai Saxena

 1. INTRODUCTION

1.1 PROJECT OVERVIEW

This project relates to the designing of a universities website that is “JAIPUR NATIONAL
UNIVERSITY” by working on ASP.NET and C# in visual studio 2008.The website contains all
the required information’s and features usually provided by a universities website.

The REGISTRATION and ONLINE EXAMINATIONS are the main features of the website.
Students fill in the required information’s in online form in order to get registered and once
registered they would be provided with a USERNAME and PASSWORD in the LOGIN section
which they utilize to view their personal academic records. While those eligible for the ONLINE
EXAMINATION’S , have to attempt ten objective type questions related to their course and the
scores of the examination would be declared instantly whereas admission information can
checked later on in the ADMISSION’S section.

1.2 PURPOSE OF PROJECT

a) For publishing the current events and all the happenings of the University.

b) For the Promotion of University.

c) Can generate various reports almost instantly when and where required.

d) For Admission notifications, faculty details, University involvements.

1.3 SCOPE Of PROJECT

This project would be very useful for educational institutes where regular updation of
University events is required. Further it can also be useful for those who wants to be aware of
all details of University and happenings of the University. This Website is needed to be updated
and can be made more attractive and rich of effects according to the need of the Institution.
1.4 DIFFERENT FROM EXISTING SYSTEM

a) It includes the LOGIN feature for students, faculties, HOD and other staff members of
the University.

b) Apart from login it has included SIGN UP feature for the instant registration of the
above mentioned users.

c) It has included the SEARCH feature for the students while viewing their results.

d) The GUI of the project is user friendly considering the needs of users.

1.5 LOGINS

a) STUDENT:-

1. Can see the RESULTS of their respective course examination.

2. Can know about the current events of the University.

3. Can fill the Online Admission Form.

4. Can know about the faculties, placements and other details of college.

b) FACULTIES:-

1. Can put their creative work for the students.

2. Can publish about the Events the wish to organize.

3. Can put the results of various courses.

c) ADMINISTRATOR:-

1. Can update the website to make it more attractive.

2. Can update the University event details on the website to make the students and others
aware.

3. Can do further changes in the website.

4. Update the results of different courses.

5. Update the details of faculties and other staff members.

 1.6 SOFTWARE INTERFACE
Server side software

• Web server software, Microsoft Visual Studio 2008

• Server side scripting tools: ASP.NET

• Database tools: Microsoft SQL Server 2005.

• Compatible operating system: Windows

Client side software

• Web browser supporting JavaScript like Internet Explorer, Mozilla Firefox etc.

1.7 SECURITY
• Administrator has the highest authority to edit/delete/create database

• Faculty have the authority to add results and events.

• Students can only view their results and the events happening in the University.

• Faculty can view all the results of every student.

• Critical information like passwords should be transferred in encrypted form

• Passwords should be stored in encrypted form

• Password will not be mailed to the user in case user forgets password, instead
either temporary password or a password reset link will be sent.

2. INTRODUCTION TO ASP.NET
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.

2.1 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 parts 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 uses 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.
 2.2 CHARACTERISTIC

2.2.1 PAGES

.NET pages, known officially as "web forms", are the main building block for application
development. 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>

2.2.2 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#" CodeFile="SampleCodeBehind.aspx.cs"
Inherits="Website.SampleCodeBehind"
AutoEventWireup="true" %>
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.

2.2.3 USER CONTROL

User controls are encapsulations of sections of pages which are registered and used as controls in
ASP.NET. User controls are created as ASCX markup files. These files usually contain static
(X)HTML markup, as well as markup defining server-side web controls where the developers
place all the required static and dynamic content. A user control is compiled when its containing
page is requested and is stored in memory for subsequent requests. User controls have their own
events which are handled during the life of ASP.NET requests. An event bubbling mechanism
provides the ability to pass an event fired by a user control up to its containing page. Unlike an
ASP.NET page, a user control cannot be requested independently; one of its containing pages is
requested instead.
 2.2.4 CUSTOM CONTROL

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.

2.2.5 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 a source of confusion among novice ASP.NET programmers who rely
on class instance members that are lost with every page request/response cycle.
 2.2.6 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.

2.2.7 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
application and are available until 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.

2.2.8 SESSION STATE

Server-side session state is held by a collection of user-defined session variables that are
persisted during a user session. These variables, accessed using the Session collection, are
unique to each session instance. The 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.

2.3 ASP.NET supports three modes of persistence for server-side session

variables:

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

ASP.NET runs a separate Windows service that maintains the state variables. Because
state management happens outside the ASP.NET process, and because the ASP.NET
engine accesses data using .NET Remoting, ASPState is slower than In-Process. This
mode allows an ASP.NET application to be load-balanced and scaled across multiple
servers. 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 for session state.
The session-state service cannot be load-balanced, and there are restrictions on types that
can be stored in a session variable.

SqlServer Mode

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 de-serialized. 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.

3. ASP.NET MASTER 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. The master
page is identified by a special @ Master directive that replaces the @ Page directive that is used
for ordinary .aspx pages. The directive looks like the following.

The @ Master directive can contain most of the same directives that a @ Control directive can
contain. For example, the following master-page directive includes the name of a code-behind
file, and assigns a class name to the master page.
 4. Advantages of Master Pages

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.
5. ASP.NET SITEMAP

To use ASP.NET site navigation, you must describe the structure of the site so that the site
navigation API and the site navigation controls can expose the site structure properly. By default,
the site navigation system uses an XML file that contains the site hierarchy. However, you can
also configure the site navigation system to use alternative data sources. For more information,
see ASP.NET Site Navigation Providers.

The following code example shows how the site map might look for a simple site that goes three
levels deep. The url attribute can start with the "~/" shortcut which indicates the application root.
<siteMap>

<siteMapNode title="Home" description="Home" url="~/default.aspx">

<siteMapNode title="Products" description="Our products"

url="~/Products.aspx">

<siteMapNode title="Hardware" description="Hardware choices"

url="~/Hardware.aspx" />

<siteMapNode title="Software" description="Software choices"

url="~/Software.aspx" />

</siteMapNode>

<siteMapNode title="Services" description="Services we offer"

url="~/Services.aspx">

<siteMapNode title="Training" description="Training classes"

url="~/Training.aspx" />

<siteMapNode title="Consulting" description="Consulting services"

url="~/Consulting.aspx" />

<siteMapNode title="Support" description="Supports plans"

url="~/Support.aspx" />

</siteMapNode>

</siteMapNode>

</siteMap>
In the Web.sitemap file, add a siteMapNode element for each page in your Web site. Then you
can create the hierarchy by nesting siteMapNode elements. In the preceding example, the pages
for Hardware and Software are child elements of the Products siteMapNode element. The title
attribute defines the text that is usually used as link text, and the description attribute acts both as
documentation and as a tool tip in the SiteMapPath control.

Using XML in ASP.NET

XML is a cross-platform, hardware and software independent, text based markup language,
which enables you to store data in a structured format by using meaningful tags. XML stores
structured data in XML documents that are similar to databases. Notice that unlike Databases,
XML documents store data in the form of plain text, which can be used across platforms.

In an XML document, you specify the structure of the data by creating a DTD or an XML
schema. When you include a DTD in an XML document, the software checks the structure of the
XML document against the DTD. This process of checking the structure of the XML document
is called validating. The software performing the task of validating is called a validating parser.

6. INTRODUCTION TO C#

C# (pronounced "cee sharp") is a multi-paradigm programming language encompassing

imperative, declarative, functional, generic, object-oriented (class-based), and component-
oriented programming disciplines. It was developed by Microsoft within the .NET initiative and
later approved as a standard by Ecma (ECMA-334) and ISO (ISO/IEC 23270).

C# is one of the programming languages designed for the Common Language Infrastructure.

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

language.Its development team is led by Anders Hejlsberg. The most recent version is C# 4.0,
which was released on April 12, 2010.

7.1 DESIGN GOAL

The name "C sharp" was inspired by musical notation where a sharp indicates that the written
note should be made a half-step higher in pitch. This is similar to the language name of C++,
where "++" indicates that a variable should be incremented by 1.

By coincidence, the sharp symbol resembles four conjoined plus signs. This reiterates Rick
Mascitti's tongue-in-cheek use of '++' when naming 'C++': where C was enhanced to create C++,
C++ was enhanced to create C++++ (that is, C#).

Due to technical limitations of display (standard fonts, browsers, etc.) and the fact that the sharp
symbol (♯, U+266F, MUSIC SHARP SIGN) is not present on the standard keyboard, the number
sign (#, U+0023, NUMBER SIGN) was chosen to represent the sharp symbol in the written
name of the programming language. This convention is reflected in the ECMA-334 C# Language
Specification. However, when it is practical to do so (for example, in advertising or in box art),
Microsoft uses the intended musical symbol.

The "sharp" suffix has been used by a number of other .NET languages that are variants of
existing languages, including J# (a .NET language also designed by Microsoft which is derived
from Java 1.1), A# (from Ada), and the functional F#.[11] The original implementation of Eiffel
for .NET was called Eiffel#,[12] a name since retired since the full Eiffel language is now
supported. The suffix has also been used for libraries, such as Gtk# (a .NET wrapper for GTK+
and other GNOME libraries), Cocoa# (a wrapper for Cocoa) and Qt# (a .NET language binding
for the Qt toolkit).

7.2 FEATURES OF C#

By design, C# is the programming language that most directly reflects the underlying Common
Language Infrastructure (CLI). Most of its intrinsic types correspond to value-types implemented
by the CLI framework. However, the language specification does not state the code generation
requirements of the compiler: that is, it does not state that a C# compiler must target a Common
Language Runtime, or generate Common Intermediate Language (CIL), or generate any other
specific format. Theoretically, a C# compiler could generate machine code like traditional
compilers of C++ or FORTRAN.
Some notable distinguishing features of C# are:

• There are no global variables or functions. All methods and members must be declared
within classes. Static members of public classes can substitute for global variables and
functions.
• Local variables cannot shadow variables of the enclosing block, unlike C and C++.
Variable shadowing is often considered confusing by C++ texts.
• C# supports a strict Boolean datatype, bool. Statements that take conditions, such as
while and if, require an expression of a type that implements the true operator, such as the
boolean type. While C++ also has a boolean type, it can be freely converted to and from
integers, and expressions such as if(a) require only that a is convertible to bool, allowing
a to be an int, or a pointer. C# disallows this "integer meaning true or false" approach on
the grounds that forcing programmers to use expressions that return exactly bool can
prevent certain types of common programming mistakes in C or C++ such as if (a = b)
(use of assignment = instead of equality ==).
• In C#, memory address pointers can only be used within blocks specifically marked as
unsafe, and programs with unsafe code need appropriate permissions to run. Most object
access is done through safe object references, which always either point to a "live" object
or have the well-defined null value; it is impossible to obtain a reference to a "dead"
object (one which has been garbage collected), or to a random block of memory. An
unsafe pointer can point to an instance of a value-type, array, string, or a block of
memory allocated on a stack. Code that is not marked as unsafe can still store and
manipulate pointers through the System.IntPtr type, but it cannot dereference them.
• Managed memory cannot be explicitly freed; instead, it is automatically garbage
collected. Garbage collection addresses the problem of memory leaks by freeing the
programmer of responsibility for releasing memory which is no longer needed.
• In addition to the try...catch construct to handle exceptions, C# has a try...finally
construct to guarantee execution of the code in the finally block.
• Multiple inheritance is not supported, although a class can implement any number of
interfaces. This was a design decision by the language's lead architect to avoid
complication and simplify architectural requirements throughout CLI.
 • C# is more type safe than C++. The only implicit conversions by default are those which
are considered safe, such as widening of integers. This is enforced at compile-time,
during JIT, and, in some cases, at runtime. There are no implicit conversions between
booleans and integers, nor between enumeration members and integers (except for literal
0, which can be implicitly converted to any enumerated type). Any user-defined
conversion must be explicitly marked as explicit or implicit, unlike C++ copy
constructors and conversion operators, which are both implicit by default.
• Enumeration members are placed in their own scope.
• C# provides properties as syntactic sugar for a common pattern in which a pair of
methods, accessor (getter) and mutator (setter) encapsulate operations on a single
attribute of a class.
• Full type reflection and discovery is available.
• C# currently (as of version 4.0) has 77 reserved words.
• Checked exceptions are not present in C# (in contrast to Java). This has been a conscious
decision based on the issues of scalability and versionability.

7. LIST OF DIAGRAMS
7.1 USE CASE DIAGRAM OVERVIEW
8.2 ACTIVITY DIAGRAM

8.3 DATA FLOW DIAGRAM

8.4 CLASS DIAGRAM
8. LIST OF TABLE
FIELD NAME DATATYPE CONSTRAINTS
Name VarChar2
Roll Integer Primary Key
Grade Char
Percentage Float

9. LIST OF FIGURES

10.1 LOGIN
10.2 SIGN UP
10.3 CONTACT US
10.4 MESSAGE
10.5 FACULTY
10.6 ABOUT JNU
10.7 LIBRARY
10.8 PHOTO GALLERY
10.9 RESULTS
10.10 SITE MAP
10.11 THE UNIVERSITY
10. SCOPE FOR ENHANCEMENT
 1. Current website has the facility of login but not all the feature are included in it.
2. It doesn’t include the details of students.
3. It doesn’t not include the logout feature.

4. Security logs though not implemented in this system would be well available through the
respective database management system and web server software.

11. REFERENCES
1. WWW.WIKKIPEDIA.COM
2. WWW.KARROX.ORG
3. WWW.JNUJAIPUR.AC.IN
4. REFERNCE BOOK BY KARROX PVT. LTD

TABLE OF CONTENTS
 1. INTRODUCTION ( S R S )
2. INTRODUCTION TO ASP.NET
3. MASTER PAGE
4. ADVANTAGE OF MASTER PAGE
5. SITE MAP
6. XML
7. INTRODUCTION TO C#

7.1 DESIGN GOAL

7.2 FEATURES OF C#

8. LIST OF DIAGRAMS

8.1 USE CASE DIAGRAM

8.2 ACTIVITY DIAGRAM

8.3 DATA FLOW DIAGRAM

8.4 CLASS DIAGRAM

9. LIST OF TABLES

10. LIST OF FIGURES

11. SCOPE FOR ENHANCEMENT

12. REFERENCES