Professional Documents
Culture Documents
INTRODUCTION
1.1 Introduction
The growing popularity of Internet and college website through e-learning
introduced new terms to education. May be in the near future students will not go to
anywhere in order to take diploma. The concept college website through e-learning
defines a simulation of the real classroom that enables users to view the details of the
college notes, video class anywhere through Internet and provides a learning experience.
This project is intended to give both teacher and student the ability to do their jobs
effectively and efficiently without even leaving their places. The project is simply
described as modeling a real world object into computer world. As in the real life the
students can see their teacher writing on the board or teacher can see students chatting or
anyone can want permission to ask question.
College website through e-learning has now been adopted and used by various
companies to inform & educate both their employees and customers. E-learning services
have evolved since computers were first used in education. There is a trend to move
towards blended learning services, where computer-based activities are integrated with
practical or classroom-based situations.
1.2 Problem definition and proposed solutions
The advancement in network technology has made it possible for transmission of
media at real time over the network. College website through e-learning allows class
room to get digitized with student at remote place can even attend the lectures.
College website through e-learning allows any number of students to attend the
lecture which is major advantage over conventional classroom which limits number of
students participating for a given lecture. This even allows lecture to be conducted at any
given time not necessarily during the working hours.
The proposed system will serve as a interface between students and teacher.
Students and teacher will be able to communicate with each through this interface as they
communicate in regular classroom. Teacher can start session of particular subject to
which student can join from their respective place itself without coming to a common
place.
Modules Description
Admin Module
Student Module
Admin:
Admin is the master of the system that he/she handles so many events. The admin
like creating Questions, editing existing Questions etc. The jobs of the admin can be
listed and explained as follows:
The admin will create the users. Our system will be working through Internet;
therefore there will be many redundant possible users who want to enter the
student page. In order to prevent redundant people to enter the classroom, the
students must preregister to the system by admin. When the student is accepted to
use the College website through e-learning the admin will create an entry in the
database by giving a username and a password. After that the student will log on
the username and password. And similar conditions will be valid for the
instructor. An instructor account must be created by admin before instructors
entrance to the system.
The admin will create the courses. As stated previously we assumed that the
instructors would not need to have detailed knowledge about the system, therefore
the courses will be created in the database by admin.
The admin will also upload files and video for student reference.
Students:
The user is the student. A student can do the following events in the system:
The student may log on to the system and download available documents related
to his/her enrolled courses.
The student can ask questions to the admin during the lecture.
2. SYSTEM ANALYSIS
A system is simply a set of components that interact to accomplish some purpose.
Systems are of two types.
Open Systems
Closed System
Systems that interact with their environments are open systems. They receive input
and produce output. In contrast; systems that do not interact with their surroundings are
closed systems all ongoing systems are open. Closed systems exist only as a concept.
System development can generally be thought of as having two major components
System Analysis
System Design
3. Query
The students can discuss with the teachers and clarify their doubts.
4. Admin
The students reports are maintain by the admin.
The proposed Virtual system has the following features
Students can view and download all learning materials (notes, ppts, pdf, books).
Admin can view the query of any student and replay to the student.
This involves questions such as whether the technology needed for the system
exists, how difficult it will be to build, and whether the firm has enough experience using
that technology. The assessment is based on an outline design of system requirements in
terms of Input, Processes, Output, Fields, Programs, and Procedures. This can
quantified in terms of volumes of data, trends, frequency of updating, etc in order to
estimate if the new system will perform adequately or not.
2.2.3 Social Feasibility
Determines whether the proposed system conflicts with legal requirements, (e.g. a
data processing system must comply with the local data protection organization has either
internal or external legal counsel, such reviews are typically standard.
3. SYSTEM REQUIREMENTS
In here, the system speciation tells that what the requirements that we used in
here. The speciation tells us about the hardware requirements and the software
requirements that we are used to develop the project.
3.1 Hardware Requirements
The computer with Pentium IV, along with the necessary peripherals devices
which are needed for the successful running of the application are given below,
Processor
: Pentium IV
Ram
Monitor
: 15 color
Hard Disk
: Minimum 40 GB
Keyboard
: Windows XP
Environment
.NET Framework
: Version 2.0
Language
: C#
Front End
: Asp.Net
Back end
development in the highly distributed environment of the Internet. The .NET Framework
is designed to fulfill the following objectives:
applications.
To build all communication on industry standards to ensure that code
based on the .NET Framework can integrate with any other code.
The .NET Framework has two main components: the common language
runtime and the .NET Framework class library. The common language
runtime is the foundation of the .NET Framework. You can think of the
runtime as an agent that manages code at execution time, providing core
services such as memory management, thread management, and remoting,
while also enforcing strict type safety and other forms of code accuracy that
ensure security and robustness. In fact, the concept of code management is a
fundamental principle of the runtime. Code that targets the runtime is known
as managed code, while code that does not target the runtime is known as
unmanaged code. The class library, the other main component of the .NET
Framework, is a comprehensive, object-oriented collection of reusable types
that you can use to develop applications ranging from traditional commandline or graphical user interface (GUI) applications to applications based on the
latest innovations provided by ASP.NET, such as Web Forms and XML Web
services.
The .NET Framework can be hosted by unmanaged components that load
the common language runtime into their processes and initiate the execution
of managed code, thereby creating a software environment that can exploit
8
both managed and unmanaged features. The .NET Framework not to provides
several runtime hosts, but also supports the development of third-party run
time hosts.
For example, ASP.NET hosts the runtime to provide a scalable, server-side
environment for managed code. ASP.NET works directly with the runtime to
enable Web Forms applications and XML Web services, both of which are
discussed later in this topic.
Internet Explorer is an example of an unmanaged application that hosts the
runtime (in the form of a MIME type extension). Using Internet Explorer to
host the runtime enables you to embed managed components or Windows
Forms controls in HTML documents. Hosting the runtime in this way makes
managed mobile code (similar to Microsoft ActiveX controls) possible,
but with significant improvements that only managed code can offer, such as
semi-trusted execution and secure isolated file storage.
3.3.2
execution, code safety verification, compilation, and other system services. These
features are intrinsic to the managed code that runs on the common language run time.
With regards to security, managed components are awarded varying degrees of
trust, depending on a number of factors that include their origin (such as the Internet,
enterprise network, or local computer). This means that a managed component might or
might not be able to perform file-access operations, registry-access operations, or other
sensitive functions, even if it is being used in the same active application.
The runtime enforces code access security. For example, users can trust that an
executable embedded in a Web page can play an animation on screen or sing a song, but
cannot access their personal data, file system, or network. The security features of the
runtime thus enable legitimate Internet-deployed software to be exceptionally feature
rich.
9
The runtime also enforces code robustness by implementing a strict type- and
code-verification infrastructure called the common type system (CTS). The CTS ensures
that all managed code is self-describing. The various Microsoft and third-party language
compilers generate managed code that conforms to the CTS. This means that managed
code can consume other managed types and instances, while strictly enforcing type
fidelity and type safety.
In addition, the managed environment of the runtime eliminates many common
software issues. For example, the runtime automatically handles object layout and
manages references to objects, releasing them when they are no longer being used. This
automatic memory management resolves the two most common application errors,
memory leaks and invalid memory references.
The runtime also accelerates developer productivity. For example, programmers
can write applications in their development language of choice, yet take full advantage of
the runtime, the class library, and components written in other languages by other
developers. Any compiler vendor who chooses to target the runtime can do so. Language
compilers that target the .NET Framework make the features of the .NET Framework
available to existing code written in that language, greatly easing the migration process
for existing applications. While the runtime is designed for the software of the future, it
also supports software of today and yesterday. Interoperability between managed and
unmanaged code enables developers to continue to use necessary COM components and
DLLs.
The runtime is designed to enhance performance. Although the common language
runtime provides many standard runtime services, managed code is never interpreted. A
feature called just-in-time (JIT) compiling enables all managed code to run in the native
machine language of the system on which it is executing. Meanwhile, the memory
manager removes the possibilities of fragmented memory and increases memory localityof-reference to further increase performance.
10
Provides
an
object-oriented
model
that
supports
the
complete
Defines rules that languages must follow, which helps ensure that objects
written in different languages can interact with each other.
Type Definitions
Describes User-Defined Types.
Type members
Describes events, fields, nested types, methods, and properties, and concepts such
as member overloading, overriding, and inheritance.
11
Value Types
Describes built-in and user-defined value types.
Classes
Describes the characteristics of common language run time classes.
Delegates
Describes the delegate object, which is the managed alternative to unmanaged
function pointers.
Arrays
Describes common language run time array types.
Interfaces
Describes characteristics of interfaces and the restrictions on interfaces imposed
by the common language runtime.
Pointers
Describes managed pointers, unmanaged pointers, and unmanaged function
pointers.
3.3.3 .NET Framework Class Library
12
Provides a reference to the classes, interfaces, and value types included in the
Microsoft .NET Framework SDK.
Common Language Runtime
Describes the run-time environment that manages the execution of code and
provides application development services.
Cross-Language Interoperability
The common language runtime provides built-in support for language
interoperability. However, this support does not guarantee that developers using another
programming language can use code you write. To ensure that you can develop managed
code that can be fully used by developers using any programming language, a set of
language features and rules for using them called the Common Language Specification
(CLS) has been defined. Components that follow these rules and expose only CLS
features are considered CLS-compliant.
This section describes the common language runtime's built-in support for
language interoperability and explains the role that the CLS plays in enabling guaranteed
cross-language interoperability. CLS features and rules are identified and CLS
compliance is discussed.
Language Interoperability
Describes built-in support for cross-language interoperability and introduces the
Common Language Specification.
What is the Common Language Specification?
Explains the need for a set of features common to all languages and identifies
CLS rules and features.
13
3.3.4
C# Overview
C# 3.0 introduces several language extensions that build on C# 2.0 to support the
creation and use of higher order, functional style class libraries. The extensions enable
construction of compositional APIs that have equal expressive power of query languages
in domains such as relational databases and XML.
The extensions include:
Implicitly typed local variables, which permit the type of local variables to
be inferred from the expressions used to initialize them.
Extension methods, which make it possible to extend existing types and
constructed types with additional methods.
Lambda expressions, an evolution of anonymous methods that provides
improved type inference and conversions to both delegate types and
expression trees.
Object initializes, which ease construction and initialization of objects.
Expression trees, which permit lambda expressions to be represented as
data (expression trees) instead of as code (delegates).
This document is a technical overview of those features. The document makes reference
to the C# Language.
15
4. SYSTEM DESIGN
4.1 Input Design
Input design is the process of converting user-originated inputs to a computerbased format. Input design is one of the most expensive phases of the operation of
computerized system and is often the major problem of a system.
In the project, the input design is made in various window forms with various methods.
4.2 Output Design
Output design generally refers to the results and information that are generated by
the system for many end-users; output is the main reason for developing the system and
the basis on which they evaluate the usefulness of the application.
4.3 Database Design
Student Sign Up:
Upload Articles:
16
Upload Video:
Query Table:
17
19
The primary actors of the system are administrator, teacher and student.
4.7 Data Flow Model:
DFD is very useful in understanding a system and can be effectively used during
analysis. A DFD shows the flow of data through a system. It views a system as a function
that transforms the inputs into desired outputs. Any complex systems will not perform
this transformation in a single step, and a data will typically undergo a series of
transformations before it becomes the output. The DFD aims to capture the
transformations that take place within a system to the input data so that eventually the
output data is produced. The agent that performs the transformation of data from one state
to another is called a process (or a bubble). So a DFD shows the movement of data
through the different transformations or the processes in the system. Named circles show
the process and named arrows entering or leaving the bubbles represent data flows. A
rectangle represents a source or link and is a net originator or consumer of data. A source
or sink is typically outside the main system of study.
General Rules
A Rectangle represents a source or link and is the net originator or consumer of data. A
source or sink is typically outside the system of study.
The need for multiple data values is represented by a * between the data flows. This
symbol represents the AND relationships. OR relationships is represented by a +.
It should be pointed that DFD is not a flowchart. A DFD represents the flow of
data, while a flowchart shows the flow of control. A DFD does not represent procedural
information. So while drawing a DFD, one must not get involved in procedural details, and
procedural thinking must be consciously avoided. The steps to construct a DFD start by
20
identifying the major inputs and outputs. Then starting from the inputs, work towards the
outputs, identifying the major transforms in the way. An alternative is to work down from
the outputs towards the inputs. Many systems are too large for a single DFD to describe the
data processing clearly. It is necessary that some decomposition and abstraction mechanism
be used for such systems. DFDs can be hierarchically organized, which helps in
progressively partitioning and analyzing large systems. Such DFDs together are called a
leveled DFD set.
Query
Send, receive
Client
Chatting
Send, receive
Upload
Send, receive
Upload
Send, receive
Download
Upload
Request,
Reply
Server
Select File
Download
Select
Server
Request,
Reply
Download
Visual Attendance
Request, Update
Authentication
Update/Fetch
Grouping
Authenticate
Database
Group
21
STUDENT
Overall Design
Question Answering
Main Form
-Question Answering
Video Conferencing
(Listen Broadcast)
-Video Conferencing
-File Download
-Grouping
-Authentication
DATABASE
Main Form
-Attendance
-Question answering
-video conferencing
-file download
- file upload
-Grouping
-Authentication
SERVER
Visual Attendance
Question Answering
ADMIN
22
Video Conferencing
-Session Management
CLIENT
Update Attendance
Request to join
Session Ended
SERVER
Update
Database
Student
Admin
Student Interface
Teacher Interface
Server
5. IMPLEMENTATION
23
24
expensive to solve in the software development process. In this phase, the logical system
of the product is developed.
3) Code Generation
In Code Generation phase, the design must be decoded into a machine-readable
form. If the design of software product is done in a detailed manner, code generation can
be achieved without much complication. For generation of code, Programming tools like
Compilers, Interpreters, and Debuggers are used. For coding purpose different high level
programming languages like C, C++, Pascal and Java are used. The right programming
language is chosen according to the type of application.
4) Testing
After code generation phase the software program testing begins. Different testing
methods are available to detect the bugs that were committed during the previous phases.
A number of testing tools and methods are already available for testing purpose.
5) Maintenance
Software will definitely go through change once when it is delivered to the
customer. There are large numbers of reasons for the change. Change could happen due
to some unpredicted input values into the system. In addition to this the changes in the
system directly have an effect on the software operations. The software should be
implemented to accommodate changes that could be happen during the post development
period.
6. SYSTEM TESTING
26
importance
of software
testing
and
its
implications
cannot
be
27
White box testing is a test case design method that uses the control structure of
the procedural designs to derive test cases. As we are using a non procedural language,
there is very small scope for the white box testing. Whenever it is necessary, there the
control structures are tested and successfully passed all the control structures with a very
minimum errors.
6.1.2 Black Box Testing
It focuses on the functional requirements to the software. It enables to derive sets
of input conditions that will fully exercise all functional requirements for a program. The
Black box testing finds almost all errors. It finds some interface errors and errors in
accessing the database and some performance errors. In Black box testing we use two
techniques equivalence partitioning the boundary volume analyzing technique.
6.1.3 System Testing
It is designated to uncover weakness that was not detected in the earlier tests. The
total system is tested for recovery and fallback after various major failures to ensure that
no data are lost. An acceptance test is done to validity and reliability of the system. The
philosophy behind the testing is to find error in project. There are many test cases
designed with this in mind. The flow of testing is as follows
Code Testing
Specification testing is done to check if the program does with it should do and
how it should behave under various condition or combinations and submitted for
processing in the system and it is checked if any overlaps occur during the processing.
This strategy examines the logic of the program. Here only syntax of the code is tested. In
code testing syntax errors are corrected, to ensure that the code is perfect.
Unit Testing
The first level of testing is called unit testing. Here different modules are tested
against the specification produced running the design of the modules. Unit testing is done
to test the working of individual modules with test oracles. Unit testing comprises a set of
tests performed by an individual programmer prior to integration of the units into a large
28
system. A program unit is usually small enough that the programmer who developed it
can test it in a great detail. Unit testing focuses first on the modules to locate errors.
These errors are verified and corrected so that the unit perfectly fits to the project.
System Testing
The next level of testing is system testing and acceptance testing. This testing is
done to check if the system has met its requirements and to find the external behavior of
the system. System testing involves two kinds of activities.
Acceptance testing
The next level of testing is called the Integration testing. In this many tested
modules are combined into subsystems, which were then tested. Test case data is
prepared to check the control flow of all the modules and to exhaust all possible inputs to
the program. Situations like treating the modules when there is no data entered in the test
box is also tested.
This testing strategy dictates the order in which modules must be available, and
exerts strong influence on the order in which the modules must be written, debugged and
unit tested. In integration testing, all modules on which unit testing is performed are
integrated together and tested.
Acceptance testing
This testing is performed finally by user to demonstrate that the implemented
system satisfies its requirements. The user gives various inputs to get required outputs.
Specification Testing
This is done to check if the program does what it should do and how it should
behave under various conditions or combination and submitted for processing in the
system and it is checked if any overlaps occur during the processing.
29
Test
Case
01
Expected Results
Login successfully
Password
7. CONCLUSION
30
Pass /
Fail
Pass
Actual Results
It should Fill correct
login successfully.
31
8. FUTURE ENHANCEMENT
The
geographically dispersed teams together in one place at the same time to ensure a
consistent learning experience and explore cultural and other barriers to success. It also
provides virtual teams the opportunity to work in the virtual world as well.
Well-designed College website through e-learning experiences rely heavily on
teamwork. Participants are divided into virtual breakout rooms to collaboratively work
through case studies, complete exercises, share ideas and practice new skills. Each group
holds independent discussions and captures their solutions on virtual whiteboards to share
with the class, thereby completing the learning feedback cycle.
We will implement the virtual environment using it to create more interaction than
in many traditional classroom settings. Instructors engage participants through polling
questions, surveys, quizzes and games that spark discussions and reinforce key learning.
Students and instructors use intuitive mark-up tools and whiteboards that facilitate
brainstorming and other idea and experience sharing.
32
9. APPENDIX
APPPENDIX (a) SOURCE CODE
Admin.aspx
using
using
using
using
using
using
using
using
using
using
System;
System.Data;
System.Configuration;
System.Collections;
System.Web;
System.Web.Security;
System.Web.UI;
System.Web.UI.WebControls;
System.Web.UI.WebControls.WebParts;
System.Web.UI.HtmlControls;
e)
}
protected void ImageButton1_Click(object sender, ImageClickEventArgs
{
{
if (TextBox1.Text == "")
{
Label3.Visible = false;
Label1.Visible = true;
Label1.Text = "Enter Your UserName";
}
else
{
Label3.Visible = true;
Label1.Visible = false;
}
if (TextBox2.Text == "")
{
Label3.Visible = false;
Label2.Visible = true;
Label2.Text = "Enter Your Password";
}
else
{
}
Label3.Visible = true;
Label2.Visible = false;
33
}
if (TextBox1.Text == username && TextBox2.Text == password)
{
Response.Redirect("AdminMain.aspx");
}
else
{
Label3.Text = "UserName And Password Not Valid";
Admin Main.aspx
using System;
using System.Data;
using System.Configuration;
using System.Collections;
using System.Web;
using System.Web.Security;
using System.Web.UI;
using System.Web.UI.WebControls;
using System.Web.UI.WebControls.WebParts;
using System.Web.UI.HtmlControls;
using System.Data.SqlClient;
public partial class AdminMain : System.Web.UI.Page
{
SqlConnection con = new SqlConnection("Data Source=MASTER-PC;Initial
Catalog=collegedata;User ID=sa;Password=redhat");
SqlDataAdapter ad;
DataSet ds = new DataSet();
static DataTable dt = new DataTable();
protected void Page_Load(object sender, EventArgs e)
{
ad = new SqlDataAdapter("select * from studsignup ", con);
ad.Fill(ds, "r");
dt = ds.Tables["r"];
GridView1.DataSource = dt;
GridView1.DataBind();
}
protected void GridView1_SelectedIndexChanged(object sender,
EventArgs e)
{
}
34
Signup.aspx
using System;
using System.Data;
using System.Configuration;
using System.Collections;
using System.Web;
using System.Web.Security;
using System.Web.UI;
using System.Web.UI.WebControls;
using System.Web.UI.WebControls.WebParts;
using System.Web.UI.HtmlControls;
using System.Data.SqlClient;
public partial class Signup : System.Web.UI.Page
{
SqlConnection muthu = new SqlConnection(" Data Source=MASTERPC;Initial Catalog=dialerdata;User ID=sa;Password=redhat");
SqlCommand sign;
protected void Page_Load(object sender, EventArgs e)
{
e)
}
protected void ImageButton1_Click(object sender, ImageClickEventArgs
{
muthu.Open();
sign = new SqlCommand("insert into
studsignup(regnum,sname,dept,year,pass)values('" + TextBox1.Text + "','"
+ TextBox2.Text + "','" + TextBox3.Text + "','" + DropDownList1.Text +
"','" + TextBox4.Text + "')", muthu);
sign.ExecuteNonQuery();
Page.ClientScript.RegisterStartupScript(this.GetType(),
"Master", "<script>alert('Signup Successfully...');</script>");
muthu.Close();
TextBox1.Text = "";
TextBox2.Text = "";
TextBox3.Text = "";
TextBox4.Text = "";
}
}
Login.aspx
using System;
using System.Data;
using System.Configuration;
using System.Collections;
using System.Web;
using System.Web.Security;
using System.Web.UI;
using System.Web.UI.WebControls;
using System.Web.UI.WebControls.WebParts;
using System.Web.UI.HtmlControls;
using System.Data.SqlClient;
public partial class studlog : System.Web.UI.Page
{
35
e)
}
protected void ImageButton1_Click(object sender, ImageClickEventArgs
{
log.Open();
Label3.Visible = true;
Label3.Text = "Invalid Password.....!!";
}
else
{
}
e)
}
protected void ImageButton2_Click(object sender, ImageClickEventArgs
{
Label3.Visible = true;
Label3.Text = "Invalid Regnum.....!!";
Response.Redirect("Signup.aspx");
Upload.aspx
36
using System.IO;
using System.Data.SqlClient;
public partial class uploadfile : System.Web.UI.Page
{
SqlConnection con = new SqlConnection("Data Source=MASTER-PC;Initial
Catalog=collegedata;User ID=sa;Password=redhat");
SqlCommand sign;
protected void Page_Load(object sender, EventArgs e)
{
}
protected void ImageButton1_Click(object sender, ImageClickEventArgs
e)
{
string path = Server.MapPath("Files/");
if (FileUpload1.HasFile)
{
string ext = Path.GetExtension(FileUpload1.FileName);
if (ext == ".doc" || ext == ".docx")
{
FileUpload1.SaveAs(path + FileUpload1.FileName);
string rec = "~/Files/" + FileUpload1.FileName;
Page.ClientScript.RegisterStartupScript(this.GetType(),
"Master", "<script>alert('File Uploaded Failure...');</script>");
}
}
}
Query .aspx
using System;
using System.Data;
using System.Configuration;
37
using System.Collections;
using System.Web;
using System.Web.Security;
using System.Web.UI;
using System.Web.UI.WebControls;
using System.Web.UI.WebControls.WebParts;
using System.Web.UI.HtmlControls;
using System.Data.SqlClient;
public partial class query : System.Web.UI.Page
{
SqlConnection con = new SqlConnection(" Data Source=MASTERPC;Initial Catalog=collegedata;User ID=sa;Password=redhat");
SqlCommand sign;
protected void Page_Load(object sender, EventArgs e)
{
}
protected void ImageButton1_Click(object sender, ImageClickEventArgs
e)
con.Open();
sign = new SqlCommand("insert into
dou(doubt,description)values('" + TextBox1.Text + "','" + TextBox2.Text
+ "')", con);
sign.ExecuteNonQuery();
Page.ClientScript.RegisterStartupScript(this.GetType(),
"Master", "<script>alert('Query Ask Updated Wait for
answer...');</script>");
TextBox1.Text = "";
TextBox2.Text = "";
con.Close();
}
}
Response.aspx
using System;
using System.Data;
using System.Configuration;
using System.Collections;
using System.Web;
using System.Web.Security;
using System.Web.UI;
using System.Web.UI.WebControls;
using System.Web.UI.WebControls.WebParts;
using System.Web.UI.HtmlControls;
using System.IO;
using System.Data.SqlClient;
public partial class Respon : System.Web.UI.Page
{
SqlConnection con = new SqlConnection(" Data Source=MASTERPC;Initial Catalog=collegedata;User ID=sa;Password=redhat");
SqlCommand sign;
SqlDataAdapter ad;
DataSet ds = new DataSet();
static DataTable dt = new DataTable();
38
con.Open();
sign = new SqlCommand("update dou Set doubt='" + TextBox1.Text +
"',ans='" + TextBox3.Text + "' where (doubt='" + TextBox1.Text + "')",
con);
sign.ExecuteNonQuery();
Page.ClientScript.RegisterStartupScript(this.GetType(),
"Master", "<script>alert('Query Response Updated...');</script>");
con.Close();
}
}
QueryAnswer.aspx
using System;
using System.Data;
using System.Configuration;
using System.Collections;
using System.Web;
using System.Web.Security;
using System.Web.UI;
using System.Web.UI.WebControls;
using System.Web.UI.WebControls.WebParts;
using System.Web.UI.HtmlControls;
using System.Data.SqlClient;
public partial class stud : System.Web.UI.Page
{
SqlConnection con = new SqlConnection(" Data Source=MASTERPC;Initial Catalog=collegedata;User ID=sa;Password=redhat");
SqlDataAdapter ad;
DataSet ds = new DataSet();
static DataTable dt = new DataTable();
protected void Page_Load(object sender, EventArgs e)
{
39
}
protected void GridView1_RowCommand(object sender,
GridViewCommandEventArgs e)
{
if (e.CommandName == "Select")
{
Uploadfile.aspx
using System;
using System.Data;
using System.Configuration;
using System.Collections;
using System.Web;
using System.Web.Security;
using System.Web.UI;
using System.Web.UI.WebControls;
using System.Web.UI.WebControls.WebParts;
using System.Web.UI.HtmlControls;
using System.IO;
using System.Data.SqlClient;
public partial class uploadfile : System.Web.UI.Page
{
SqlConnection con = new SqlConnection("Data Source=MASTER-PC;Initial
Catalog=collegedata;User ID=sa;Password=redhat");
SqlCommand sign;
protected void Page_Load(object sender, EventArgs e)
{
e)
}
protected void ImageButton1_Click(object sender, ImageClickEventArgs
{
40
FileUpload1.SaveAs(path + FileUpload1.FileName);
string rec = "~/Files/" + FileUpload1.FileName;
Uploadvideo.aspx
using System;
using System.Data;
using System.Configuration;
using System.Collections;
using System.Web;
using System.Web.Security;
using System.Web.UI;
using System.Web.UI.WebControls;
using System.Web.UI.WebControls.WebParts;
using System.Web.UI.HtmlControls;
using System.IO;
using System.Data.SqlClient;
public partial class uploadvideos : System.Web.UI.Page
{
SqlConnection con = new SqlConnection("Data Source=MASTER-PC;Initial
Catalog=collegedata;User ID=sa;Password=redhat");
DataSet ds = new DataSet();
static DataTable dt = new DataTable();
SqlCommand sign;
protected void Page_Load(object sender, EventArgs e)
{
}
41
e)
}
else
{
Page.ClientScript.RegisterStartupScript(this.GetType(),
"Master", "<script>alert('Video Uploaded Failure...');</script>");
}
}
}
42
43
Admin Page
44
45
Student Page
46
47
48
49
10. BIBLIOGRAPHY
50