College Website Creation

CSE PROJECT 2011-2012

A PROJECT REPORT ON COLLEGE WEBSITE DESIGN Submitted for the partial fulfillment of Computer Science & Engineering, B.E. Final Year

Submitted by:-

Guide:-

TARACHAND MAURYA E. No: - 08/1460 SANTOSH KR. BILONIYA E. No. - 08/1436 RAKESH GAHANOLIA E. No. – 08/1528 PULKIT SAINI E. No. – 08/

Shri SHARWAN RAM SIR Assistant Professor M.B.M. Engg. College Jodhpur.

Department of Computer Science and Engineering MBM Engineering College, Faculty of Engineering, Jai Narain Narain Vyas Vyas Unive University rsity Jodhpur Jodhpur (Raja (Rajastha sthan) n) Session:-2012-13

College Web Site Design

Page 1


ACKNOWLEDGEMENT

It is great happiness and privilege for us to represent this Project report. we have completed the development of college website as final year project under the supervision of Shri Sharwan Ram Sir. We would like to express our gratitude towards all those people who have in various ways, help us in successful completion of our project. We’d We’d like like to be than thankf kful ul to our our colle colleag ague ues s and and team team memb member ers s for for thei their r valuable support and corporation during our project.

SANTOSH KUMAR BILONIYA E. NO. – 08/1436 TARACHAND MAURYA E. NO. - 08/1460 RAKESH GAHANOLIA E. NO. – 08/ PULKIT SAINI E. NO. -08/1607


Page 2


ACKNOWLEDGEMENT

It is great happiness and privilege for us to represent this Project report. we have completed the development of college website as final year project under the supervision of Shri Sharwan Ram Sir. We would like to express our gratitude towards all those people who have in various ways, help us in successful completion of our project. We’d We’d like like to be than thankf kful ul to our our colle colleag ague ues s and and team team memb member ers s for for thei their r valuable support and corporation during our project.

SANTOSH KUMAR BILONIYA E. NO. – 08/1436 TARACHAND MAURYA E. NO. - 08/1460 RAKESH GAHANOLIA E. NO. – 08/ PULKIT SAINI E. NO. -08/1607


Page 2


PREFACE A website is a collection of Web pages, images, videos and other digital assets that is hosted on one or several Web server, usually accessible via the Internet. The pages of websites can usually be accessed from a common root URL, called the homepage, and usually reside on the same physical server. The URLs of the pages organize them into a hierarchy, although the hyperlinks between them control how the reader perceives the overall structure and how the traffic flows between the different parts of the sites. The college website has been developed using ASP.Net as the Front End and SQL Server as the Back End. It follows the three tier architecture with C# for coding and ADO.Net providing the classes classes for database connectivity.


Page 3


Table of Contents 1. Introduction………………………………………………………… 5 1.1 About About the Topic…… Topic………………… …………………………… ……………………………… ……………… 5 1.2 About About the Project Project ……………………………… ……………………………………………… ……………… 5

2. System Analysis…………………………………………………… Analysis…………………………………………………… 6 2.1 Introdu Introductio ction………… n………………………… ……………………………… …………………………… …………… 6 2.2 Existing Existing System… System……………… …………………………… ……………………………… ………………… …6 2.3 Propos Proposed ed System System……………… …………………………… …………………………… ……………………6 ……6 2.4 Feature Featuress of Softwa Software…… re…………………… ……………………………… ……………………… ……… 7 2.4. 2.4.1 1

ASP. ASP.Ne Net-F t-Fro ront nt End End ……………… ……………………… ……………… …………… ……

7

2.4. 2.4.2 2

C#.N C#.Netet-Mi Midd ddle le End End ……………… ……………………… ……………… …………… …… 9

2.4. 2.4.3 3

SQL SQL Serv Server er 2005 2005-Ba -Back ck End End ……………… ……………………… …………. …. 9

2.4. 2.4.4 4

ADO. ADO.Ne Net…… t…………… ……………… ……………… ……………… ……………… ………….. ….. 10

2.5 Softwar Softwaree require requiremen ments……… ts……………………… ……………………………… ………………… … 14 2.6 Hardwa Hardware re requi requireme rements… nts………………… ……………………………… …………………… …… 14

3. System Design ………………………………………………….. 14 3.1 Table Table desig design n ………………… ……………………………… …………………………… …………………. …. 15 3.2 E-R Diagra Diagram m ……………… ……………………………… ……………………………… ………………… … 21 3.3 Database Database Design Design ……………………………… …………………………………………… …………….. .. 23 3.4 Web page pagess design design ………………………………… ……………………………………………. …………. 23 3.4.1 Component of web pages ……………………………… 23 3.4. 3.4.2 2

Web We b Page Pagess ……………… ……………………. ……... ..……… ……………… …………… ……

24

4. Coding……………………………………..………. Coding……………………………………..………. ………… 42 4.1 Features of of Languages ……………………………… ……………… ……………………… ……… 42

5. Conclusion Conclusion ……………………………………………………… 45 References References ………………………………………………………..45


Page 4


1. INTRODUCTION 1.1 ABOUT THE TOPIC A website is a collection of Web pages, images, videos and other digital assets that is hosted on one or several Web server , usually accessible via Internet. The pages of websites can usually be accessed from a common root URL called the homepage, and usually reside on the same physical server. The URLs of the pages organize them into a hierarchy, although the hyperlinks between them control how the reader perceives the overall structure and how the traffic flows between the different parts of the sites. A website requires attractive design and proper arrangement of links and images, which enables a browser to easily interpret and access the properties of the site. Hence it provides the browser with adequate information and functionality about the organization, community, network etc.

1.2

ABOUT THE PROJECT

The website has been developed for our college (BRAEC) in an effort to make it as attractive and dynamic as possible. Compared to the existing site a database has been added to our project. The working of the project is as follows. The first page provides several links. The Home page contains several information about the site like campus, management, facilities, infrastructure etc. User Login module helps the user to login to the site. For that he must type the username and password correctly. The login provision in this page helps the already registered user to directly access the site and there is a link for registration to a user who is new to this site. Member Registration module helps the new user to register into the site. The information entered by the users is added into the table registration. In the Login link a student can login using the appropriate Username and password, through which he can download lecture videos and ebooks. He can also view the assignment of his subject. The flash news and the events corner display the latest developments, announcements and events associated with the college activities.


Page 5


The administrator has the responsibility for displaying the recruiters form on the notice board, in response to which student can submit his willingness to attend the drive along with his resume.

2. SYSTEM ANALYSIS

2.1 INTRODUCTION System analysis is the process of gathering and interpreting facts, diagnosing problems and using the information to recommend improvements on the system. System analysis is a problem solving activity that requires intensive communication between the system users and system developers. System analysis or study is an important phase of any system development process. The system is studied to the minutest detail and analyzed. The system analyst plays the role of an interrogator and dwells deep into the working of the present system. The system is viewed as a whole and the inputs to the system are identified. The outputs from the organization are traced through the various processing that the inputs phase through in the organization. A detailed study of these processes must be made by various techniques like Interviews, Questionnaires etc. The data collected by these sources must be scrutinized to arrive to a conclusion. The conclusion is an understanding of how the system functions. This system is called the existing system. Now, the existing system is subjected to close study and the problem areas are identified. The designer now functions as a problem solver and tries to sort out the difficulties that the enterprise faces. The solutions are given as a proposal. The proposal is then weighed with the existing system analytically and the best one is selected. The proposal is presented to the user for an endorsement by the user. The proposal is reviewed on user request and suitable changes are made. This loop ends as soon as the user is satisfied with the proposal. 2.2

EXISTING SYSTEM

The existing college website is static which makes it less interactive. It doesn't have database connectivity. Moreover students didn't have an access to the details of the college through the site, hence they were not updated about the latest events and placement drives. 2.3

PROPOSED SYSTEM


Page 6


In order to make the site dynamic and more interactive we have tried to include a database link to our college website. Hence the students have been provided with the facility to post their faq’s which are answered by the administrater.. Provision has also been made to display the latest events and announcements associated with the college online. We have developed our project using the three tier architecture which uses the following languages.

FEATURES OF SOFTWARES VISUAL STUDIO .NET EDITIONS 2.4

2.4.1 ASP.NET - FRONT END ASP.NET is not just a simple upgrade or the latest version of ASP. ASP.NET combines unprecedented developer productivity with performance, reliability, and deployment. ASP.NET redesigns the whole process. It's still easy to grasp for new comers but it provides many new ways of managing projects. Below are the features of ASP.NET. •

Easy Programming Model

ASP.NET makes building real world Web applications dramatically easier. ASP.NET server controls enable an HTML-like style of declarative programming that let you build great pages with far less code than with classic ASP. Displaying data, validating user input, and uploading files are all amazingly easy. Best of all, ASP.NET pages work in all browsers including Netscape, Opera, AOL, and Internet Explorer. •

Flexible Language Options

ASP.NET lets you leverage your current programming language skills. Unlike classic ASP, which supports only interpreted VBScript and J Script, ASP.NET now supports more than 25 .NET languages (built-in support for VB.NET, C#, and JScript.NET), giving us unprecedented flexibility in the choice of language. •

Great Tool Support

We can harness the full power of ASP.NET using any text editor, even Notepad. But Visual Studio .NET adds the productivity of Visual Basic-style development to the Web. Now we can visually design ASP.NET Web Forms using familiar drag-drop-double click techniques, and enjoy full-fledged code support including statement completion and color-coding. VS.NET also provides integrated support for debugging and deploying ASP.NET Web applications. The Enterprise versions of Visual Studio .NET deliver life-cycle features to help organizations plan, analyze, design, build, test, and coordinate teams that develop ASP.NET Web applications. These include UML class


Page 7


modeling, database modeling (conceptual, logical, and physical models), testing tools (functional, performance and scalability), and enterprise frameworks and templates, all available within the integrated Visual Studio .NET environment.

•

Rich Class Framework

Application features that used to be hard to implement, or required a 3rd-party component, can now be added in just a few lines of code using the .NET Framework. The .NET Framework offers over 4500 classes that encapsulate rich functionality like XML, data access, file upload, regular expressions, image generation, performance monitoring and logging, transactions, message queuing, SMTP mail, and much more. With Improved Performance and Scalability ASP.NET lets we use serve more users with the same hardware. •

Compiled execution

ASP.NET is much faster than classic ASP, while preserving the "just hit save" update model of ASP. However, no explicit compile step is required. ASP.NET will automatically detect any changes, dynamically compile the files if needed, and store the compiled results to reuse for subsequent requests. Dynamic compilation ensures that the application is always up to date, and compiled execution makes it fast. Most applications migrated from classic ASP see a 3x to 5x increase in pages served. •

Rich output caching

ASP.NET output caching can dramatically improve the performance and scalability of the application. When output caching is enabled on a page, ASP.NET executes the page just once, and saves the result in memory in addition to sending it to the user. When another user requests the same page, ASP.NET serves the cached result from memory without re-executing the page. Output caching is configurable, and can be used to cache individual regions or an entire page. Output caching can dramatically improve the performance of data-driven pages by eliminating the need to query the database on every request. •

Enhanced Reliability

ASP.NET ensures that the application is always available to the users. •

Memory Leak, Dead Lock and Crash Protection

ASP.NET automatically detects and recovers from errors like deadlocks and


Page 8


memory leaks to ensure our application is always available to our users. For example, say that our application has a small memory leak, and that after a week the leak has tied up a significant percentage of our server's virtual memory. ASP.NET will detect this condition, automatically start up another copy of the ASP.NET worker process, and direct all new requests to the new process. Once the old process has finished processing its pending requests, it is gracefully disposed and the leaked memory is released. Automatically, without administrator intervention or any interruption of service, ASP.NET has recovered from the error. •

Easy Deployment

ASP.NET takes the pain out of deploying server applications. "No touch" application deployment. ASP.NET dramatically simplifies installation of our application. With ASP.NET, we can deploy an entire application as easily as an HTML page, just copy it to the server. No need to run regsvr32 to register any components, and configuration settings are stored in an XML file within the application. •

Dynamic update of running application

ASP.NET now lets we update compiled components without restarting the web server. In the past with classic COM components, the developer would have to restart the web server each time he deployed an update. With ASP.NET, we simply copy the component over the existing DLL, ASP.NET will automatically detect the change and start using the new code.

2.4.2

C#.NET - MIDDLE END

In brief, C#.NET a next generation of ASP (Active Server Pages) introduced by Microsoft. Similar to previous server-side scripting technologies, C#.NET allows us to build powerful, reliable, and scalable distributed applications. C#.NET is based on the Microsoft .NET framework and uses the .NET features and tools to develop Web applications and Web services. Even though C#.NET sounds like ASP and syntaxes are compatible with ASP but C#.NET is much more than that. It provides many features and tools, which let you develop more reliable and scalable, Web applications and Web services in less time and resources. Since C#.NET is a compiled,. NET-based environment; we can use any .NET supported languages, including VB.NET, C#, JScript.NET, and VBScript.NET to develop C#.NET applications. 2.4.3 SQL SERVER 2005 - BACK END SQL Server 2005 exceeds dependability requirements and provides innovative


Page 9


capabilities that increase employee effectiveness, integrate heterogeneous IT ecosystems, and maximize capital and operating budgets. SQL Server 2005 provides the enterprise data management platform our organization needs to adapt quickly in a fast-changing environment. With the lowest implementation and maintenance costs in the industry, SQL Server 2005 delivers rapid return on the data management investment. SQL Server 2005 supports the rapid development of enterprise-class business applications that can give our company a critical competitive advantage. Benchmarked for scalability, speed, and performance, SQL Server 2005 is a fully enterprise-class database product, providing core support for Extensible Markup Language (XML) and Internet queries.

2.4.4

ADO.NET - DATABASE CONNECTIVITY

Most applications need data access at one point of time making it a crucial component when working with applications. Data access is making the application interact with a database, where all the data is stored. Different applications have different requirements for database access. ASP.NET uses ADO .NET (Active X Data Object) as it's data access and manipulation protocol which also enables us to work with data on the Internet. • ADO.NET Data Architecture Data Access in ADO.NET relies on two components: DataSet and Data Provider.

a. DataSet The dataset is a disconnected, in-memory representation of data. It can be considered as a local copy of the relevant portions of the database. The DataSet is persisted in memory and the data in it can be manipulated and updated independent of the database. When the use of this DataSet is finished, changes can be made back to the central database for updating. The data in DataSet can be loaded from any valid data source like Microsoft SQL server database, an Oracle database or from a Microsoft Access database. b.

Data Provider

The Data Provider is responsible for providing and maintaining the connection to the database. A DataProvider is a set of related components that work together to provide data in an efficient and performance driven manner. The .NET Framework currently comes with two DataProviders: the SQL Data Provider which is designed only to work with Microsoft's SQL Server 7.0 or


Page 10


later and the OleDb DataProvider which allows us to connect to other types of databases like Access and Oracle. Each DataProvider consists of the following component classes: The Connection object which provides a connection to the database. The Command object which is used to execute a command. The DataReader object which provides a forward-only, read only, connected recordset. The DataAdapter object which populates a disconnected DataSet with data and performs update. • Data access with ADO.NET can be summarized as follows: A connection object establishes the connection for the application with the database. The command object provides direct execution of the command to the database. If the command returns more than a single value, the command object returns a DataReader to provide the data. Alternatively, the DataAdapter can be used to fill the Dataset object. The database can be updated using the command object or the DataAdapter.

• Component classes that make up the Data Providers a.

The Connection Object

The Connection object creates the connection to the database. Microsoft Visual Studio .NET provides two types of Connection classes: the SqlConnection object, which is designed specifically to connect to Microsoft SQL Server 7.0 or later, and the OleDbConnection object, which can provide connections to a wide range of database types like Microsoft Access and Oracle. The Connection object contains all of the information required to open a connection to the database.

b. The Command Object The Command object is represented by two corresponding classes: SqlCommand and OleDbCommand. Command objects are used to execute Fig 1 ADO.NET DATA commands to a database across a data connection. The Command objects can ARCHITECTURE be used to execute stored procedures on the database, SQL commands, or return complete tables directly.

c. The DataReader Object The DataReader object provides a forward-only, read-only, connected stream


Page 11


recordset from a database. Unlike other components of the Data Provider, DataReader objects cannot be directly instantiated. Rather, the DataReader is returned as the result of the Command object's ExecuteReader method. The SqlCommand.ExecuteReader method returns a SqlDataReader object, and the OleDbCommand.ExecuteReader method returns an OleDbDataReader object. The DataReader can provide rows of data directly to application logic when we do not need to keep the data cached in memory.

d. The DataAdapter Object The DataAdapter is the class at the core of ADO .NET's disconnected data access. It is essentially the middleman facilitating all communication between the database and a DataSet. The DataAdapter is used either to fill a DataTable or DataSet with data from the database with its Fill method. After the memoryresident data has been manipulated, the DataAdapter can commit the changes to the database by calling the Update method. The DataAdapter provides four properties that represent database commands: SelectCommand, InsertCommand, DeleteCommand and UpdateCommand When the Update method is called, changes in the DataSet are copied back to the database and the appropriate InsertCommand, DeleteCommand, or UpdateCommand is executed. 2.5 THE ARCHITECTURAL MODELS

•

Phase 1: Classic

In the classic model, note how all layers are held within the application itself. This architecture would be very awkward to maintain in a large-scale environment unless extreme care was taken to fully encapsulate or modularize the code. Because Phase 1 of the Duwamish Books sample focuses on a small retail operation, this type of design is perfectly acceptable. It's easy to develop and, in the limited environment of a single retail outlet, easy to maintain. In Phase 1, we deliver the basic functionality and documentation of the code and design issues. • Phase 2: Two-tier Phase 2 moves to a two-tier design, as we break out the data access code into its own layer. By breaking out this layer, we make multiple-user access to the THE SYSTEM ARCHITECTURAL data much easierFig to2.work with. The developer does not have to worry about MODELS record locking, or shared data, because all data access is encapsulated and controlled within the new tier.


Page 12


•

Phase 3 and Phase 3.5: Logical three-tier and physical three-tier

The business rules layer contains not only rules that determine what to do with data, but also how and when to do it. For an application to become scalable, it is often necessary to split the business rules layer into two separate layers: the client-side business logic, which we call workflow, and the server-side business logic. Although we describe these layers as client and server-side, the actual physical implementations can vary. Generally, workflow rules govern user input and other processes on the client, while business logic controls the manipulation and flow of data on the server. Phase 3 of the Duwamish Books sample breaks out the business logic into a COM component to create a logical three-tier application. Our second step in creating a three-tier application is to provide a physical implementation of the architecture. To distribute the application across a number of computers, we implement Microsoft Transaction Server in Phase 3.5. The application becomes easier to maintain and distribute, as a change to the business rules affects a smaller component, not the entire application. This involves some fairly lengthy analysis because the business rules in Phase 1 were deliberately not encapsulated. •

Phase 4: A Windows-based application

Phase 4 of the Duwamish Books sample is the culmination of the migration from a desktop model to a distributed n-tier model implemented as a Web application. In Phase 4, we offer three client types aimed at different browser types. We also break out the workflow logic from the client application. This logic is now implemented through a combination of ASP script, some clientside processing (depending on the client type), and a COM component. The Workflow component converts ADO Recordsets it receives from the Business Logic Layer component into XML data, which is, in turn, converted into HTML for presentation. Phase 4 documents the benefits, architecture, and implementation issues relating to the migration of a three-tier application to a Web-based application Performance has not been tuned for minimum system configuration. Increasing your RAM above the recommended system configuration will increase our performance, specifically when running multiple applications, working with large projects, or doing enterprise-level development.

2.5 SOFTWARE REQUIREMENTS OPERATING SYSTEM : WINDOWS XP/VISTA/7 BROWSER FRONT END : INTERNET EXPLORER OR ANY HTTP BROWSER DATABASE LAYER : ASP.NET


Page 13


WEB SERVER : SQL SERVER 2005 SERVER SIDE SCRIPTING : C#.NET CLIENT SIDE SCRIPTING : C#.NET CONNECTION : TCP / IP PROTOCOL : HTTP, SMTP, POP3, WAP

2.6 HARDWARE REQUIREMENTS PROCESSOR LOCK SPEED SYSTEM BUS RAM HDD MONITOR

: PENTIUM IV : 2 GHZ : 32 BIT : 128 MB : 40GB : SVGA COLOR

3. SYSTEM DESIGN System design is the solution to the creation of a new system. This phase is composed of several systems. This phase focuses on the detailed implementation of the feasible system. It emphasis on translating design specifications to performance specification. System design has two phases of development logical and physical design. During logical design phase the analyst describes inputs (sources), out puts (destinations), databases (data sores) and procedures (data flows) all in a format that meats the uses requirements. The analyst also specifies the user needs and at a level that virtually determines the information flow into and out of the system and the data resources. Here the logical design is done through data flow diagrams and database design. The physical design is followed by physical design or coding. Physical design produces the working system by defining the design specifications, which tell the programmers exactly what the candidate system must do. The


Page 14


programmers write the necessary programs that accept input from the user, perform necessary processing on accepted data through call and produce the required report on a hard copy or display it on the screen.

3.1 TABLE DESIGN Table Definition of Mechanical Result


Page 15


Table Definition of Faculty


Page 16


Table Definition of Registration


Page 17


Table Definition of Students


Page 18


Table Definition of Roll No .


Page 19


Table Definition of Student Login

Table Definition of Subject


Page 20


Table Definition of FAQ

3.2 E-R Diagram Of Database:College Web Site Design

Page 21


Fig. 3 E-R Diagram of Result Of Mechanical relation

Fig. 4 E-R Diagram of Result Of CSE relation


Page 22


Fig. 5 E-R Diagram of Teacher & Department relation

Fig. 5 Foreign Key relation between Login & Students table College Web Site Design

Page 23


3.3 DATABASE DESIGN The overall objective in the development of database technology has been to treat data as an organizational resource and as an integrated whole. DBMS allow data to be protected and organized separately from other resources. Database is an integrated collection of data. The most significant form of data as seen by the programmers is data as stored on the direct access storage devices. This is the difference between logical and physical data. Database files are the key source of information into the system. It is the process of designing database files, which are the key source of information to the system. The files should be properly designed and planned for collection, accumulation, editing and retrieving the required information. The organization of data in database aims to achieve three major objectives: •

Data integration.

•

Data integrity.

•

Data independence.

The proposed system stores the information relevant for processing in the MS SQL SERVER database. This database contains tables, where each table corresponds to one particular type of information. Each piece of information in table is called a field or column. A table also contains records, which is a set of fields. All records in a table have the same set of fields with different information. There are primary key fields that uniquely identify a record in a table. There are also fields that contain primary key from another table called foreign keys.


Page 24

3.4 WEB FORM DESIGN Web Forms are based on ASP.NET. Working with Web Forms is similar to working with Windows Forms. But the difference is that we will create Web pages with Web forms that will be accessible by a Web browser. Web Forms are Web pages that serve as the user interface for a Web application. A Web Forms page presents information to the user in any browser or client device and implements application logic using server-side code. Web Forms are based on the System.Web.UI.Page class. The class hierarchy for the page class is shown below. •

Object

•

Control

•

Template Control

•

Page

3.4.1 COMPONENTS OF WEB FORMS In Web Forms pages, the user interface programming is divided into two parts: the visual component (design page) and the logic (code behind page).The visual element is the Web Forms page. The page consists of a file with static HTML, or ASP.NET server controls, or both simultaneously. The Web Forms page works as a container for the static text and the controls we want to display. Using the Visual Studio Web Forms Designer and ASP.NET server controls, we can design the form just like in any Visual Studio application. The logic for the Web Forms page consists of code that we create to interact with the form. The programming logic is in a separate file from the user interface file. This file is the "code-behind" file and has an ".aspx.vb" (VB) or ".aspx.cs" (C-Sharp) extension. The logic we write in the code-behind file can be written in Visual Basic or Visual C#. The code-behind class files for all Web Forms pages in a project are compiled into the project dynamic-link library (.dll) file. The .aspx page file is also compiled, but differently. The first time a user loads the aspx page, ASP.NET automatically generates a .NET class file that represents the page, and compiles it to a second .dll file. The generated class for the aspx page inherits from the code-behind class that was compiled into the project .dll file. When the user requests the Web page URL, the .dll files run on the server and dynamically produces the HTML output for your page.

College Website Design

Page 25

3.5 HOME PAGE The home page of a website is the first page that a user perceives upon entering the website url at the browser address area. The entire website depends on how the home page is designed which forms the platform for viewing other web forms. In short, a home page forms the abstract of the entire website. The BRAEC website begins with an interactive home page in which there is link for all other pages in the form of menu and hyperlinks which provide quick access to all the pages. The home page appears as given below.


Page 26

FIG. 6 HOMEPAGE


Page 27

Through the home page a number of other web pages can be linked. Each link gives an elaborated detail about itself with adequate lists and photos. Some of them are listed below.


Page 28


Page 29


Page 31


Page 32


Page 33


Page 34


Page 35


Page 36


Page 37


Page 38


Page 39


Page 40


Page 41

4. CODING 4.1 FEATURES OF LANGUAGE •

Microsoft Visual Studio .Net

Visual Studio .NET is a complete set of development tools for building ASP Web applications, XML Web services, desktop applications, and mobile applications. Visual Basic .NET, Visual C++ .NET, and Visual C# .NET all use the same integrated development environment (IDE), which allows them to share tools and facilitates in the creation of mixed-language solutions. In addition, these languages leverage the functionality of the .NET Framework, which provides access to key technologies that simplify the development of ASP Web applications and XML Web services.

•

The .NET Framework

The .NET Framework is a multi-language environment for building, deploying, and running XML Web services and applications. It consists of two main parts:

a.

Common Language Runtime

Despite its name, the runtime actually has a role in both a component's runtime and development time experiences. While the component is running, the runtime is responsible for managing memory allocation, starting up and stopping threads and processes, and enforcing security policy, as well as satisfying any dependencies that the component might have on other components. At development time, the runtime's role changes slightly; because it automates so much (for example, memory management); the runtime makes the developer's experience very simple, especially when compared to COM as it is today. In particular, features such as reflection dramatically reduce the amount of code a developer must write in order to turn business logic into a reusable component.

b.

Unified programming classes

The framework provides developers with a unified, object-oriented, hierarchical, and extensible set of class libraries (APIs). Currently, C++ developers use the Microsoft Foundation Classes and Java developers use the Windows Foundation Classes. The framework unifies these disparate models and gives C#.net and Jscript programmer's access to class libraries as well. By creating a common set of APIs across all programming languages, the common language runtime enables cross-language inheritance, error handling, and debugging. All programming languages, from JScript to C++, have similar access to the


Page 42

framework and developers are free to choose the language that they want to use.

•

Introduction to C#.NET

In brief, C#.NET a next generation of ASP (Active Server Pages) introduced by Microsoft. Similar to previous server-side scripting technologies, C#.NET allows us to build powerful, reliable, and scalable distributed applications. C#.NET is based on the Microsoft .NET framework and uses the .NET features and tools to develop Web applications and Web services. Even though C#.NET sounds like ASP and syntaxes are compatible with ASP but C#.NET is much more than that. It provides many features and tools, which let we develop more reliable and scalable, Web applications and Web services in less time and resources. Since C#.NET is a compiled, .NET-based environment; we can use any .NET supported languages, including VB.NET, C#, JScript.NET, and VBScript.NET to develop C#.NET applications.

• Advantages of C#.NET a. .NET Compatible

.NET compatibility feature of C#.NET provides applications to use the features provides by .NET. Some of these features are multi-language support, compiled code, automatic memory management, and .NET base class library. We have choice to select a programming language. We can write Web applications using any .NET supported language, including C#, VB.NET, JScript.NET and VBScript.NET. All C#.NET code is compiled, rather than interpreted, which allows early binding, strong typing, and just-in-time (JIT) compilation to native code, automatic memory management, and caching. The .NET base class library (BCL) provides hundreds of useful classes. This library can be accessed from any. NET supported language.

b.

Web Forms and Rapid Development

Web Forms allows you to build rapid Web GUI applications. Web Forms provides us web pages and server side controls. We can use web forms and server side controls in VS.NET similar to we write Windows applications. VS.NET provides Windows application similar drag and drop features, which allows us to drag server side controls on a page and set control properties and write event handlers by using wizard property page. The VS.NET framework writes code for us under the hood and our application is ready in no time. In most of the cases, we don't even need to know what wizards write for us under


Page 43

the hood.

c.

Native XML Support and XML Web Services

XML is a vital part of entire .NET framework. . NET uses XML to store and transfer data among applications. The .NET base class library provides highlevel programming model classes, which can be used t o work with XML. An XML Web service provides the means to access server functionality remotely. Web services use SOAP (Simple Object Access Protocol) to provide access to clients. Web services can be used to build different layers of distributed applications and we can use different layers remotely.

d.

Databases and ADO.NET

ADO.NET is a new version of ADO (ActiveX Data Objects). Event though ADO.NET sounds like ADO, but it are a complete redesigned database access technology. ADO.NET allows us to access different kinds of databases using only one programming model. We must be familiar with DAO, ADO, ODBC, RDO and other database access technologies previous to ADO.NET. Each of these technologies had its own pros and cons. ADO.NET combines features of all of these techniques and provides a single higher level-programming model and hides all details for us. It makes our job much simpler and provides a way to write rapid development. See ADO.NET section of C# Corner for ADO.NET source code samples and tutorials.

e. Caching and State Management One of the most important factors in building high-performance, scalable Web applications is the ability to store items, whether data objects, pages, or parts of a page, in memory the initial time they are requested. We can store these objects on the server or on the client machine. Storing data on a server or a client is called caching. C#.NET provides two types of caching - page caching and request caching. We use request caching to improve code efficiency and to share common data across the pages and we use page caching to provide fast access to the Web applications from clients. C#.NET provides easy-to-use application-state and session-state management, which allows managing states of Web applications. C#.NET also provides cookie less state management, means we don't need to use cookies to for state storage.


Page 44

College Website Creation

Recommend Documents