10

CHAPTER 1 INTRODUCTION

1.1 Company Profile

HP Enterprise Services is the global business and technology services division of Hewlett Packard's HP Enterprise Business strategic business unit. It was formed by the combination of HP's legacy services consulting and outsourcing business and the integration of acquired Electronic Data Systems, which had defined the outsourcing business when it was established in 1962 by H. Ross Perot. HP Enterprise Services catalogs its services into three service portfolios which are Infrastructure Technology Outsourcing (ITO), Applications Services, and Industry Services, including Business Process Outsourcing (BPO). Infrastructure Technology Outsourcing services includes maintaining the operation of part or all of a client's computer and communications infrastructure, such as networks, mainframes, "midrange" and Web servers, desktops and laptops, and

printers. Applications Services involves the developing, integrating, modernizing, and/or maintaining of applications software for clients. And, Industry Services addresses the core business challenges of clients in five key industries: healthcare, transportation, communications, government, and financial services, among others. Business Process Outsourcing, which involves performing a business function for a client, like payroll, call centers, insurance claims processing, and so forth, is an integral part of the Industry Services offerings. HP Enterprise Services is a key implementer of the "Instant-On Enterprise." This HP Enterprise Business initiative seeks to highlight the fundamental shifts in the way information technology is being used to meet changing business models and the growing role of technology to drive business decisions and help organizations achieve economic growth, improve efficiency, and to further the development of

11

society through the use of technology. In a larger context, the initiative seeks to help forward-thinking companies and government agencies have a more evolutionary, business-driven approach to how they deliver IT services, including solutions to modernize, transform, secure, and maximize the use of technology.

Figure 1.1 COMPANY TRADEMARK

1.2 Company Locations

HPES operates in 60 countries, centered in the metropolitan areas of DallasFortWorth; Detroit; DesMoines and Clarion,Iowa; SaltLakeCity; Indianapolis;Winch estr,Kentucky; Tulsa,Oklahoma; Boise,Idaho;and NorthernVirginia in the United States.

1.3 Company Services

HP Enterprise Services catalogs its services into three service portfolios Infrastructure Technology Outsourcing (ITO) Applications Services Industry Services, including Business Process Outsourcing (BPO).

12

CHAPTER 2 SOFTWARE TECHNOLOGY

2.1 What is .NET?

The .NET framework created by Microsoft is a software development platform focused on rapid application development, platform independence and network transparency. .NET is Microsoft's strategic initiative for server and desktop development for the next decade. According to Microsoft,.NET includes many technologies that are designed to facilitate rapid development of Internet and intranet applications. .NET is not meant to be used exclusively for Internet development, its innovations were driven by the limitations of current Internet development tools and technology. The basis of this new development platform consists of three primary components or layers: the common language runtime, the .NET Framework base classes, and the user and program interfaces, as demonstrated in Figure 2.1

Figure 2.1 .NET FRAMEWORK

13

2.2 The .NET Framework Component

.NET also includes some more revolutionary components in the form of the .NET Framework. It is shown in figure 2.2 .

Figure 2.2 .NET FRAMEWORK COMPONENT

Common Language Runtime .NET System Class library ASP.NET Web Controls

14

2.2.1 Common Language Runtime (CLR):

The CLR lives at the heart of the .NET Framework. The CLR provides an environment in which our programs can run. This includes concepts such as compilation, registration, and even deployment issues. As the name implies, the CLR is designed to support many programming languages in a common manner. This is exciting because it means that developers don't have to learn a new language syntax to program in the .NET environment. Microsoft will be releasing some core languages with Visual Studio.NET, including: VB C# C++ JSCRIPT

The common language runtime uses just-in-time compilers to compile the IL (intermediate language) code to native binary code before execution. Other significant features of the common language runtime include the following: Version control Memory management Cross-language integration Common data type system

2.2.1.1 Compilation
An important part of the CLR is its compilation process. This process provides a great deal of flexibility and is at the root of many of .NET's capabilities overall. All code in .NET is natively compiled, but that compilation typically occurs just in time to run the code rather than way back before deployment as is typical today. To understand the compilation process we need to realize that .NET introduces not one new language, but two. C# has received a lot of attention from the press and developers, but .NET also introduces MSIL - the Microsoft Intermediate Language. All languages that work with .NET have compilers that generate MSIL rather than machine code. MSIL code (and some metadata we'll discuss later) can be deployed as needed, and will be compiled into machine code on the user's computer,

15

2.2.1.2 Metadata
Each language compiler does not always generate IL, it also generates metadata. This metadata is key to .NET as it provides an exact description of the components that were compiled to IL. In the world of COM, components were described by MIDL - the Microsoft Interface Definition Language. MIDL was unable to completely and accurately describe components, which could be a limiting factor in application design, and most definitely caused problems when VB code tried to call a C++ component or visa versa. The metadata scheme used by .NET is far more robust. The data is kept in XML so it is easily accessible and understandable. More importantly, the metadata for the component completely and accurately describes the component's interfaces. The result is that components can be created in and called by any language - avoiding nearly all associated problems with COM. In fact, because the IL and metadata are fully accessible to the .NET runtime we gain a number of key cross-language benefits, including: Seamless cross-language method calls Code can be checked to see if it is "unsafe" before being run .NET can automatically serialize objects Cross-language inheritance

2.2.1.3 Managed vs. Unmanaged Code

A common term that comes up when discussing .NET and the CLR is the concept of managed code. This is a pretty straightforward concept. Any code that runs within the context of the CLR is managed code. Any code that runs within the native environment of the underlying operating system (within the Win32 environment for instance) is unmanaged code. Managed code is just code that is running, and thus is being managed by, the .NET Common Language Runtime.

2.2.1.4 Unsafe Code:

When discussing .NET, the concept of "safe" vs. "unsafe" code will arise. The term "unsafe" can be confusing, because unsafe code isn't necessarily unsafe it just could be unsafe. Unsafe code is code that works with pointers meaning that it could directly alter the call stack, or take other steps that might circumvent predictable behavior. That doesn't mean our code actually does any of these things, just that it could. Essentially, unsafe code is code that the CLR can't ensure will always run properly or safely. Because the CLR compiles the IL code right before it is actually run, it can easily check through the IL as it is being compiled to determine if it is safe. Security settings on a machine can prohibit the

16

running of unsafe code, helping to prevent malicious code from running within the .NET environment.

2.2.2 .NET System Class Library

The CLR is an important part of .NET. However, merely having the ability to run code on many different hardware or operating systems is just a part of the overall puzzle. To be useful, applications need to interact with their environment - its files, data, processes, fonts, graphical components, etc. Without a consistent way to interact with the environment across various operating systems, there's no way to create a complex business application. The CLR ensures that our code will compile in many places - but it is the .NET system class library that provides our code with a consistent way to interact with the environment. The system class library is quite comprehensive. It has to be. We are used to programming within the Win32 environment - which is a pretty comprehensive "runtime'. To be successful,.NET has to provide a runtime with comparable features and functionality, essentially providing operating system capabilities while being operating system neutral. The CLR and system class library compose the environment in which all .NET applications will run. A comprehensive understanding of the system class library and its features is critical for success regardless of the specific programming language being used by the developer.

2.2.3 ASP.NET 2.2.3.1 What is ASP.NET?

ASP.NET Is A Key Part of The Wider Microsoft .NET Initiative , Microsofts New Application Development Platform. .NET is Both An Application Architecture To Replace The Windows DNA Model And A Set of Tools , Services , Applications and Servers Based Around The .NET Framework and Common Language Runtime (CLR). Rather Than Just Being ASP 4.0 or an Incremental Upgrade , ASP.NET is Acomplete Rewrite From The Ground Up, Using all The Advanced Features .NET Makes Available. .With the .NET Framework and ASP.NET , Microsoft Has Not Just Shown itself to Be a Contender in Web Development Technologies , But many Commentators Also Believe Microsoft Has Taken The Lead

17

Microsoft has been very Careful to Include the Functionality and Flexibility Developers will Require , While Maintaining the Easy- to-use Nature of ASP With ASP.NET you Now Have a True Choice of Languages. All the .NET Languages have access to the Same Foundation Class Libraries , The Same Type of Systems , Equal object orientation and inheritance abilities, and full interoperability with existing COM components. You can use the same knowledge and code investment for everything from Web development to component development or enterprise systems, and developers do not have to be concerned about differences in APIs or variable type conversions, or even deployment. Microsoft has included in the .NET Framework an incredibly rich feature set of library classes, from network-handling functions for dealing with Transmission Control Protocol/Internet Protocol (TCP/IP) and Domain Name System (DNS), through to XML data and Web Services, to graphic drawing. In the past, the limitations of ASP scripting meant components were Required for functionality reasons, not just for architectural reasons. ASP.NET has access to the same functionality and uses the same language sin which you would create components, so now components are an architectural choice only. A .NET developer is shielded from changes in the underlying operating system and API, as the .NET technologies deal with how your code is implemented; and with the Common Type System, you dont have to worry whether the component you are building uses a different implementation of a string or integer to the language it will be used in.

2.2.3.2 Why ASP.NET?

ASP.NET isnt simply the next version of ASP its a completely redesigned technology that takes the best aspects of ASP and merges them with the power of pure object-oriented programming (OOP) , a powerful development framework , to give it a vast range of functionality and the advantages of a fully compiled execution environment . You modify your ASP.NET page , you refresh the page in the browser , and the changes are reflected. No where are you required to run a compiler . Compilation actually occurs the first time a page is requested after it has been modified. This compiled copy is then kept until the page is modified and requested again . As Ive already mentioned , this process is totally transparent to the user . Theres naturally a significant performance advantage of ASP.NET over ASP . Now, in addition to the obligatory scalability advantage of a compiled application . Its also important to note that while ASP.NET supports the previously mentioned compile on demand functionality , its also possible to precompiled ASP.NET applications into a .NET DLL , which is the method

18

that Visual Studio .NET uses by default when building Web applications with it.

2.2.3.3 Web Services

When We Use The Internet The Two Things We Use Most Likely Use, It For are Sending (and Receiving) E-Mail and Suffering the Web. These two Application are , by far the Most Popular Uses of the Internet. Building on the Success of the WWW , Web Services Has the Potential to be The Next Big Thing. The Web is a Great Way to Share Information. However the Problem is to be that Web is only to be use by Human . Whereas Web Services are Built to be Read and Interpreted by Computer Programs not by Humans. Web Services are , in effect , Web Sites for Computers to Use . These Web Sites tends to be Dynamic in Nature , so They Dont Contain Static Unchanging Content , But Can React and Adapt to Choices and Sections. Web Services are Based on Completely open Standards that are not tied to any particular Platform or any particular Company. Part of Their Attraction is that doesnt matter whether you deploy your web services on Solaris , Unix , Mac , or Windows- any one will be able to Connect to and Use your Web Services. .Net Implementation of Web Services are entirely based around a programming paradigm that developers have been falling in love with for years . The Principle behind a Web Services is that you build a class that has methods in it.

2.2.4 Web Controls

The ASP.NET Web controls are also known as Web form controls . Microsoft has included a plethora of Web controls in the System.Web.UI.WebControls namespace. For discussion purposes , we will divide these controls into three major categories:

Basic Web Controls

These Web controls are similar to HTML server controls but have additional features . These controls have a richer and more consistent object model.

19

Validation Controls
These controls have been developed exclusively for input validation.

Data bound List Controls

These belong to the new generation of controls that provide additional power and development speed .These are also typically referred to as Template Web Controls. All Web controls are derived from the generic class named Web Control. Thus, the Web controls inherit a common set of class members. Some of the frequently used members include Backdoor , Border Colour , Border Style, Border Width , Data Bind, Enabled , Font , Four-color , Height , Page , Parent , Site , Tab Index , ToolTip , Visible, Init , Load , Unload, Dispose , To String , On nit , On Load , and On Data Binding.

2.2.5 How Web Server Execute Asp.Net Files

When a site visitor requests a Web page address , the browser contacts the Web server specified in the address URL and makes a request for the page by formulating HTTP request , which is sent to the Web server . The Web server on receiving the request determines the file type requested and passes processing to the appropriate handler. ASP.NET files are compiled , if necessary , into .NET Page classes and then executed , with the results sent to the clients browser. Compilation means that on first load ASP.NET applications take longer to display than previous versions of ASP , but once compiled they are noticeably faster.

Client-Server Interaction
ASP.NET applications are a mixture of client side markup and code , and server side processing . When an ASP.NET Web form page is downloaded to the visitors Web browser , additional code is included to previous ASP versions . This extra code enables richer form functionality , including server and client side events , validation , and the ability to maintain form value state . The server determines the visitors browser type and sends markup to match the browsers abilities . Some client interactions will be dealt with within the visitors browser , while others will require information to be posted to the server for processing and the altered page returned . As form responses are received , the form values are maintained in a new facility of ASP.NET State Bags and are compressed into a hidden form element containing the page View state. This allows the form elements that the

20

visitor has interacted with to maintain the same values as when the page was submitted . As illustrated in Figure the browser can request information from and send information to the server using two HTTP methods , GET and POST.

Server-Side Processing
When the server receives this request , it will find the page that was requested using the path information specified , and the relevant system will process the page . In the case of Classic ASP , there was not much to this process , although a certain amount of caching happened . As you will see in Figure with ASP.NET the process is a fair amount more involved but provides for much faster processing and delivery.

2.2.6 ASP.NET Execution Model 2.2.6.1 Compilation of ASP .Net Pages

It is a well known fact that ASP .Net pages functional logic can be written in two ways. The ASP .Net code can either be written inside the ASPX page or it can be included as a asp.net code.cs or vb .net file. When the ASPX page is embedded with the code of either C# or VB .Net, the ASP .Net run time automatically compiles the code into an assembly and loads it. If the code is kept in a separate source file either as a VB or C# file, it has to be compiled by the programmer, which will be used by the run time for further execution.

2.2.6.2 Writing ASP .Net Apps with Code Behind Files

The compilation of these Code Behind files is usually done manually either using the csc.exe command line compiler or by using the Build feature in Microsoft Visual Studio .Net, which produces an output as a library with an extension of .DLL. Now the job of aspnet_wp.exe is very simple. It can directly execute the compiled code and return the HTML page to the web server.

2.2.6.3 Execution Flow of ASPX Pages by IIS

The execution of ASP .Net pages are not singly handled by the Internet Information Server or in short hand form IIS. It is taken care by the worker process aspnet_wp.exe. Whenever the IIS receives a request from a web browser or a client requesting for a page, it delegates the job to the aspnet_wp.exe process, which takes care of the subsequent jobs and finally returns the HTML page back to the IIS.

21

When ASP .Net is installed, installation process creates an association for .aspx files with the aspnet_isapi.dll files. When the IIS receives a request from the clients or web browsers for an aspx page, the IIS web server hands this request over to the aspnet_isapi.dll, which in turn instantiates the aspnet_wp.exe job. This aspnet_wp.exe finalizes any unfinished jobs like run time compilation etc., as explained above and then executes the asp .net application in a new application domain. Finally the output page is generated and returned back to the web server, which in-turn sends the file over to the client.

Figure 2.3 ASP.NET EXECUTION

2.2.7 Overview to Sql Server

SQL server is a client/server relational database management system (RDBMS) that uses the transact-SQL to send request between the client and SQL server. SQL server is designed to be a client/server system. Client/server systems

22

are constructed so that the database can reside on central computer known as Server and be shared among several users. When users want to access the data in SQL server, they run an application on their local computer known as client that connects over a network to the server running SQL server. SQL server can work with thousands of client applications simultaneously. The server has features to prevent the logical problems that occur if a user tries to read or modify data currently being used by others. While SQL server is designed to work as a client/server network, it is also capable of working as a stand-alone database directly on the client. The scalability and ease of use features of SQL server allow it to work efficiently on a client without consuming too many resources. SQL server effectively allocates the available resources such as memory, network bandwidth and disk I/O among the multiple

Figure 2.4 SQL SERVER PROCESSING

23

CHAPTER 3 PROJECT DESCRIPTION

3.1 Project Modules 3.1.1 Admin Module 3.1.1.1Control

The administrator has the central control over the whole portal.

3.1.1.2 Access
He can access the students and faculties information directly.

3.1.2 Faculty Module 3.1.2.1 Create a Profile (Registration)

Create a form where the faculty can create an enter the details of academics and extracurricular activities the profile is in editable mode.

3.1.2.2 Student Details

Create a page which will contain a combo box from which the faculties can choose to view the profile of the students of the respective batch.

3.1.2.3NoticePage
Create a page with 1 text field for title of the notice and text area for the content of the notice. The page should also contain a combo to choose for whom the notice is for.

3.1.2.4 Upload E-books

In this form user can upload the e-books for the students it will have a combo to decide for whom the e-book is to be uploaded.

24

3.1.2.5Scrap Space
Each faculty should have their own scrap space where the queries is posted.

3.1.3 Student Module 3.1.3.1Create a Profile (Registration)

Create a form where the user can create an enter the details of academics and extra-curricular activites the profile is in editable mode.

3.1.3.2 Resume Builder

Create a page which will generate a resume based on the data entered by the student in the profile.

3.1.3.3 Notice
Create a page which will have a combo box from which the student can choose which notice he wishes to see by the faculty.

3.1.3.4 Faculty Profile

Create a page which will contain the list of the faculties sorted alphabetically and each entry serves as a link to the faculty profile.

3.1.3.5 E-Books
In this form user can download the e-books uploaded by the faculties.

3.1.3.6 Query
Each student should have his own scrap space where the response to their queries is posted.

25

3.2 Project Database Table 3.2.1 Admin Login Database

Field Name UserID Password Description int(10) PK Varchar(30)

Table 3.1 ADMIN LOGIN

3.2.2 Faculty Database

Field Name UserID Department Degree JoiningYear UserName Password Description int(10) primary key Varchar(30) Varchar(20) int(4) Varchar(30) Varchar(30)

Table 3.2 FACULTY DATABASE

3.2.3 Student Database 3.2.3.1 Mandatory Details

Field Name UserID RollNo Batch Branch Degree JoiningYear Description int(10) primary key int(10) int(4) Varchar(30) Varchar(10) int(4)

Table 3.3 STUDENT DATABASE (MANDATORY DETAILS)

26

3.2.3.2 Academic Details

Field Name AcdAchvmt Sports Cultural Others Graduation Inter HighSchool Description Varchar(150) Varchar(150) Varchar(150) Varchar(150) Int (5) Int (5) Int (5)

Table 3.4 STUDENT DATABASE (ACADEMIC DETAILS)

3.2.3.3 Profile
Field Name Name DOB Gender Address MobNumber Email Description Varchar(30) int(10) varchar(6) varchar(50) Int(10) Varchar(20)

Table 3.5 STUDENT DATABASE (PROFILE DETAILS)

3.2.3.4 Technical Skills

Field Name PrgmLanguage Database OS Software OtherSkill IndustryExp AcademicProject Description Varchar(30) Varchar(30) Varchar(30) Varchar(30) Varchar(30) Varchar(150) Varchar(150)

Table 3.6 STUDENT DATABASE (TECHNICAL SKILLS)

27

3.3 Tools And Technology

Server Side : ASP.NET with C# Client Side : HTML Database : SQL Server 2005 Web Server-IIS6.0 Framework: .NET Framework 3.5. IDE :Microsoft Visual Studio 2008

28

CHAPTER 4 PROJECT OVERVIEW

4.1 Home Page

Figure 4.1 HOME PAGE

29

4.2 Login Page

Figure 4.2 LOGIN PAGE

30

4.3 Registration Page 4.3.1 Faculty Registration Page

Figure 4.3 FACULTY REGISTRATION PAGE

31

4.3.2 Student Registration Page

Figure 4.4 STUDENT REGISTRATION PAGE

32

4.4 Profile Home Page 4.4.1 Admin Profile Home Page

Figure 4.5 ADMIN PROFILE HOME PAGE

4.4.2 Faculty Profile Home Page

Figure 4.6 FACULTY PROFILE HOME PAGE

33

4.4.3 Student Profile Home Page

Figure 4.7 STUDENT PROFILE HOME PAGE

4.5 Home Page Code

using System; using System.Collections; using System.Configuration; using System.Data; using System.Linq; using System.Web; using System.Web.Security; using System.Web.UI; using System.Web.UI.HtmlControls; using System.Web.UI.WebControls; using System.Web.UI.WebControls.WebParts; using System.Xml.Linq; public partial class Default3 : System.Web.UI.Page { protected void Page_Load(object sender, EventArgs e) { } }

34

4.6 Login Page Code

using System; using System.Collections; using System.Configuration; using System.Data; using System.Linq; using System.Web; using System.Web.Security; using System.Web.UI; using System.Web.UI.HtmlControls; using System.Web.UI.WebControls; using System.Web.UI.WebControls.WebParts; using System.Xml.Linq; using System.Data.SqlClient; public partial class Default3 : System.Web.UI.Page { protected void Page_Load(object sender, EventArgs e) { } protected void Button5_Click(object sender, EventArgs e) { if(DropDownList2.Text=="Faculty") { if (bussiness.AuthenticateFact(TextBox8.Text, TextBox9.Text)) { Session["uname"] = TextBox8.Text; Response.Redirect("Faculty_Profile.aspx?uname="); } else { Label7.Text="Invalid User Name Or Password !!!"; } } else if(DropDownList2.Text=="Student") { if (bussiness.Authenticate(TextBox8.Text, TextBox9.Text)) { Session["uname"] = TextBox8.Text; Response.Redirect("StudentProfile.aspx?uname="); } else { Label7.Text = "Invalid User Name Or Password !!!"; }

35

} else if(DropDownList2.Text=="Administrator") { if (bussiness.AuthenticateAdmin(TextBox8.Text, TextBox9.Text)) { Session["uname"] = TextBox8.Text; Response.Redirect("AdminProf.aspx?uname="); } else { Label7.Text = "Invalid User Name Or Password !!!"; } } } }

4.7 Registration Page Code 4.7.1 Faculty Registration Code

using System; using System.Collections; using System.Configuration; using System.Data; using System.Linq; using System.Web; using System.Web.Security; using System.Web.UI; using System.Web.UI.HtmlControls; using System.Web.UI.WebControls; using System.Web.UI.WebControls.WebParts; using System.Xml.Linq; using System.Data.SqlClient; public partial class Default6 : System.Web.UI.Page { protected void Page_Load(object sender, EventArgs e) { } protected void Button3_Click(object sender, EventArgs e) { SqlConnection con = new SqlConnection(); con.ConnectionString = "Data Source=vaio-VAIO;Integrated Security=true;Initial Catalog=csdepart"; con.Open();

36

string insertqr = "Insert into Stu_Login values(" + TextBox1.Text + ",'" + TextBox2.Text + "','" + TextBox3.Text + "'," + DropDownList1.Text + ",'" + TextBox4.Text + "','" + TextBox5.Text + "')"; SqlCommand com = new SqlCommand(insertqr, con); com.ExecuteNonQuery(); con.Close(); } protected void Button4_Click(object sender, EventArgs e) { TextBox1.Text = ""; TextBox2.Text = ""; TextBox3.Text = ""; TextBox4.Text = ""; TextBox5.Text = ""; } }

4.7.2 Student Registration Code

using System; using System.Collections; using System.Configuration; using System.Data; using System.Linq; using System.Web; using System.Web.Security; using System.Web.UI; using System.Web.UI.HtmlControls; using System.Web.UI.WebControls; using System.Web.UI.WebControls.WebParts; using System.Xml.Linq; using System.Data.SqlClient; public partial class Stureg : System.Web.UI.Page { protected void Page_Load(object sender, EventArgs e) { } protected void Button1_Click(object sender, EventArgs e) { SqlConnection con = new SqlConnection(); con.ConnectionString = "Data Source=vaio-VAIO;Integrated Security=true;Initial Catalog=csdepart"; con.Open();

37

string insertqr = "Insert into StudentReg values(" + TextBox2.Text +" ,'" + TextBox24.Text + "'," + TextBox3.Text + "," + DropDownList1.Text + ",'" + TextBox1.Text + "','" + TextBox4.Text + "'," + DropDownList2.Text + ",'" + TextBox5.Text + "','" + TextBox6.Text + "','" + DropDownList3.Text + "','" + TextBox7.Text + "'," + TextBox8.Text + ",'" + TextBox9.Text + "','" + TextBox10.Text + "','" + TextBox11.Text + "','" + TextBox12.Text + "','" + TextBox13.Text + "'," + DropDownList4.Text + "," +DropDownList5.Text + "," + DropDownList6.Text+",'" + TextBox17.Text + "','" + TextBox18.Text + "','" + TextBox19.Text + "','" + TextBox20.Text + "','" + TextBox21.Text + "','" + TextBox22.Text + "','" + TextBox23.Text + "')"; SqlCommand com = new SqlCommand(insertqr, con); com.ExecuteNonQuery(); con.Close(); } protected void Button2_Click(object sender, EventArgs e) {

TextBox2.Text = ""; TextBox3.Text = "";TextBox5.Text = "";TextBox6.Text = "";TextBox7.Text = "";TextBox8.Text = "";TextBox9.Text = "";TextBox10.Text = "";TextBox11.Text = "";TextBox12.Text = "";TextBox13.Text = "";DropDownList4.Text = "";DropDownList5.Text = "";DropDownList6.Text = "";TextBox17.Text = "";TextBox18.Text = "";TextBox19.Text = "";TextBox20.Text = ""; TextBox21.Text = "";TextBox22.Text = "";TextBox23.Text = "";TextBox24.Text = "";DropDownList1.Text = "";DropDownList2.Text = "";DropDownList3.Text = ""; } protected void Calendar1_SelectionChanged(object sender, EventArgs e) { TextBox6.Text = Calendar1.SelectedDate.ToShortDateString(); } }

4.8 Profile Page Code 4.8.1 Admin Profile Page Code

using System; using System.Collections; using System.Configuration; using System.Data; using System.Linq; using System.Web;

38

using System.Web.Security; using System.Web.UI; using System.Web.UI.HtmlControls; using System.Web.UI.WebControls; using System.Web.UI.WebControls.WebParts; using System.Xml.Linq; public partial class AdminProf : System.Web.UI.Page { protected void Page_Load(object sender, EventArgs e) { string userName = Session["uname"].ToString(); Label1.Text = "Admin Id:-"+userName; } protected void LinkButton1_Click(object sender, EventArgs e) { Session.Abandon(); Response.Redirect("Login.aspx"); } }

4.8.2 Faculty Profile Page Code

using System; using System.Collections; using System.Configuration; using System.Data; using System.Linq; using System.Web; using System.Web.Security; using System.Web.UI; using System.Web.UI.HtmlControls; using System.Web.UI.WebControls; using System.Web.UI.WebControls.WebParts; using System.Xml.Linq; public partial class Default3 : System.Web.UI.Page { protected void Page_Load(object sender, EventArgs e) { string userName = Session["uname"].ToString(); Label1.Text = userName; Label3.Text = "You Are Visitor Number :" + Application["HitCount"].ToString(); string UName = Request.QueryString["name2"]; Label4.Text = "<br>Faculty " + UName; } protected void Logout_Click(object sender, EventArgs e)

39

{ Session.Abandon(); Response.Redirect("Login.aspx"); } }

4.8.3 Student Profile Page Code

using System; using System.Collections; using System.Configuration; using System.Data; using System.Linq; using System.Web; using System.Web.Security; using System.Web.UI; using System.Web.UI.HtmlControls; using System.Web.UI.WebControls; using System.Web.UI.WebControls.WebParts; using System.Xml.Linq; public partial class Default5 : System.Web.UI.Page { protected void Page_Load(object sender, EventArgs e) { string userName = Session["uname"].ToString(); Label1.Text = userName; Label2.Text="You Are Visitor Number :"+Application["HitCount"].ToString(); string UName =Request.QueryString["name1"]; Label3.Text = "<br>Student "+UName; } protected void Logout_Click(object sender, EventArgs e) { Session.Abandon(); Response.Redirect("Login.aspx"); } protected void LinkButton6_Click(object sender, EventArgs e) { } }

40

CHAPTER 5 CONCLUSION

As per the departments requirement whole website is designed. We can add additional enhancements to our project. We can also make this project in such a way that users can solve their problems directly through the Internet by querying the faculties of the department and these queries and there replies can be viewed by all other registered users,hence it will save time of both students and faculties,who have the same problem to solve. We can also embed chat option for the users (Students or Faculties) who are online at the time and are registered, so that it can be used as a social networking site such as Facebook, Orkut, and Twitter etc at a small scale or at department level. Furter we can also add an option of sms for the registered users.

41

CHAPTER 6 BIBLIOGRAPHY

Asp.Net Bible. Beginning ASP.NET 2.0 with C# Asp.Net Complete Reference www.google.com