WEB BASED DOCUMENT VERSION REGULATOR TABLE OF CONTENTS

SNO

TITLE
ABSTRACT

PAGE NO

1.

INTRODUCTION 1.1 ABOUT THE ORGANIZATION 1.2 PROJECT DESCRIPTION

2.

SYSTEM STUDY 2.1 FEASIBILITY STUDY 2.2 EXISTING SYSTEM 2.3 PROPOSED SYSTEM

SYSTEM SPECIFICATION 3.1 HARDWARE CONFIGURATION 3.2 SOFTWARE CONFIGURATION

LANGUAGE SPECIFICATION 4.1 FEATURES OF ASP .NET 4.2 FEATURES OF SQL SERVER 2000

SYSTEM DESIGN 5.1 INPUT DESIGN 5.2 OUTPUT DESIGN 5.3 DATABASE DESIGN

5.4 DATA FLOW DIAGRAM 6 SYSTEM TESTING AND MAINTENANCE 6.1 UNIT TESTING 6.2 INTEGRATION TESTING 6.3 VALIDATION TESTING 6.4 VERIFICATION TESTING 7 SYSTEM IMPLEMENTATION 7.1 SCOPE FOR FUTURE DEVELOPMENT 8 9 CONCLUSION BIBLIOGRAPHY APPENDIX SCREEN SHOTS DATA TABLE STRUCTURE SAMPLE CODINGS

SYNOPSIS This project is aimed at developing a version controller which can be used to control any type of documents. This is typically useful when a group of people are concurrently changing the documents in a repository. First User registration and access privilege to the repository, Administrators privilege to edit user profiles, Stream management. (A stream is a file base which is independent of other file bases. The scope of all version-control actions is restricted to a file-base.) Users have option to select the stream from list-down box.

The User Interface user has option to select stream, User has option to traverse the Folder tree, and the last folder of a tree will have the documents. User can view all versions of a document, User can up-version a document simply by uploading that document again, User can delete only the latest version which he/she has created, and User can create the initial version of the document. The version numbering will happen automatically. Administrator can freeze a file-base.

INTRODUCTION
The DOCUMENT VERSION REGULATOR is required which is being capable of elimination all the problems and become useful to store more than 10MB of files, images, songs, videos. We easily invite the friends and upload their details. We can easily maintain the download details. Report generation is easier. We easily create the folders. Monitor the status of the entire at any time and the verification of reports generated by the admin. It will used to produce less time consuming. The project involves checking for a site and navigating to the specified site and downloads the requested page to our web site. In addition, the links in the requested pages are determined. Then it also navigates to all the links and downloads the pages. So it is easy to get our related web pages without search the links and navigating to the pages individually. In existing system we produce a manual system. Like yahoo or gmail websites we can send only 10MB files .we have to down load the files in the particular websites. We cant invite any friends in this system. We cant easily share our folders. We have to store only limited amount of documents

which is private. The system becomes very slow and not to share the documents easily. We have to store limited documents. Report generation is tedious process. More time consuming. The project also maintains the web sites we search, the links present in the requested sites, the download size, the number of pages downloaded and the related information. When the requested site does not allow the download permission, the information is logged to a file so that we can easily identify the sites that are not downloaded. ABOUT THE ORGANISATION I-WIZ BLUE CHIP TECHNOLOGIES., established in 1999 has been actively involved in the development of customized software for various clients since its inception and also has its presence strongly felt in the areas of Projects Guidance and Consulting. Our concern has three branches in Coimbatore, Trichy, and Madurai. Development: We would like to introduce ourselves as a Projects Guidance & Development specializing in Networking, Application and System side on JAVA, JSP, J2EE, ASP, VB, ADVANCED C & C++, VC+ +, EMBEDDED SYSTEMS, Dot net, Micro controller & Micro Processor & Linux.Our areas of specialization include complete business solutions for commercial environments, application software and productivity tools for different environments.

Our Service Placement assurance to merit students Assistance in placement for all students Free hosting of resume of all students from our own website. Special Features Our wide contacts with IT industry allow us to locate and select merit students to be sent to prospective interviews to leading organization having opening either in India 0r abroad. SYSTEM CONFIGURATION HARDWARE CONFIGURATION HARD DISK MONITOR RAM PROCESSOR EQUIVALENT PROCESSOR SPEED MINIMUM 500 MHZ 20 GB 15 COLOR WITH VGI CARD SUPPORT MINIMUM 256 MB PENTIUM III AND ABOVE (OR)

SOFTWARE CONFIGURATION

OPERATING SYSTEM WINDOWS XP PLATFORM DATABASE LANGUAGES VISUAL STUDIO .NET 2005 SQL SERVER 2000 ASP.NET, C#.

SOFTWARE PROFILE FEATURES OF ASP. NET WHAT IS .NET? Microsoft .NET is a set of Microsoft software technologies for rapidly building and integrating XML Web services, Microsoft Windowsbased applications, and Web solutions. The .NET Framework is a languageneutral platform for writing programs that can easily and securely interoperate. Theres no language barrier with .NET: there are numerous languages available to the developer including Managed C++, C#, Visual Basic and Java Script. The .NET framework provides the foundation for components to interact seamlessly, whether locally or remotely on different platforms. It standardizes common data types and communications protocols so that components created in different languages can easily interoperate. .NET is also the collective name given to various software components built upon the .NET platform. These will be both products (Visual Studio.NET and Windows.NET Server, for instance) and services (like Passport, .NET My Services, and so on). THE .NET FRAMEWORK The .NET Framework has two main parts: 1. The Common Language Runtime (CLR). 2. A hierarchical set of class libraries. The CLR is described as the execution engine of .NET. It provides the environment within which programs run. The most important features are:

 executed on. collection. running code.

Conversion from a low-level assembler-style language,

called Intermediate Language (IL), into code native to the platform being Memory management, notably including garbage

Checking and enforcing security restrictions on the Loading and executing programs, with version control

and other such features. The following features of the .NET framework are also worth description: Managed Code - is code that targets .NET, and which contains certain extra information - metadata - to describe itself. Whilst both managed and unmanaged code can run in the runtime, only managed code contains the information that allows the CLR to guarantee, for instance, safe execution and interoperability. Managed Data - With Managed Code comes Managed Data. CLR provides memory allocation and Deal location facilities, and garbage collection. Some .NET languages use Managed Data by default, such as C#, Visual Basic.NET and JScript.NET, whereas others, namely C++, do not. Targeting CLR can, depending on the language youre using, impose certain constraints on the features available. As with managed and unmanaged code, one can have both managed and unmanaged data in .NET applications - data

that doesnt get garbage collected but instead is looked after by unmanaged code. Common Type System - The CLR uses something called the Common Type System (CTS) to strictly enforce type-safety. This ensures that all classes are compatible with each other, by describing types in a common way. CTS define how types work within the runtime, which enables types in one language to interoperate with types in another language, including crosslanguage exception handling. As well as ensuring that types are only used in appropriate ways, the runtime also ensures that code doesnt attempt to access memory that hasnt been allocated to it. Common Language Specification - The CLR provides built-in support for language interoperability. 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. THE CLASS LIBRARY .NET provides a single-rooted hierarchy of classes, containing over 7000 types. The root of the namespace is called System; this contains basic types like Byte, Double, Boolean, and String, as well as Object. All objects derive from System. Object. As well as objects, there are value types. Value types can be allocated on the stack, which can provide useful

flexibility. There are also efficient means of converting value types to object types if and when necessary. The set of classes is pretty comprehensive, providing collections, file, screen, and network I/O, threading, and so on, as well as XML and database connectivity. The class library is subdivided into a number of sets (or namespaces), each providing distinct areas of functionality, with dependencies between the namespaces kept to a minimum. LANGUAGES SUPPORTED BY .NET The multi-language capability of the .NET Framework and Visual Studio .NET enables developers to use their existing programming skills to build all types of applications and XML Web services. The .NET framework supports new versions of Microsofts old favorites Visual Basic and C++ (as VB.NET and Managed C++), but there are also a number of new additions to the family: Visual Basic .NET has been updated to include many new and improved language features that make it a powerful object-oriented programming language. These features include inheritance, interfaces, and overloading, among others. Visual Basic also now supports structured exception handling, custom attributes and also supports multi-threading. Visual Basic .NET is also CLS compliant, which means that any CLS-compliant language can use the classes, objects, and components you create in Visual Basic .NET.

Managed Extensions for C++ and attributed programming are just some of the enhancements made to the C++ language. Managed Extensions simplify the task of migrating existing C++ applications to the new .NET Framework. C# is Microsofts new language. Its a C-style language that is essentially C++ for Rapid Application Development. Unlike other languages, its specification is just the grammar of the language. It has no standard library of its own, and instead has been designed with the intention of using the .NET libraries as its own. Microsoft Visual J# .NET provides the easiest transition for Java-language developers into the world of XML Web Services and dramatically improves the interoperability of Java-language programs with existing software written in a variety of other programming languages. Active State has created Visual Perl and Visual Python, which enable .NET-aware applications to be built in either Perl or Python. Both products can be integrated into the Visual Studio .NET environment. Visual Perl includes support for Active States Perl Dev Kit. Other languages for which .NET compilers are available include: FORTRAN COBOL Eiffel

Fig1 .Net Framework ASP.NET XML SERVICES Base Class Libraries Common Language Runtime Operating System WEB Forms Windows

INTRODUCTION TO ASP.NET ASP.NET is the .NET framework layer that handles Web requests for specific types of files, namely those with (.aspx or .ascx) extensions. The ASP.NET engine provides a robust object model for creating dynamic content and is loosely integrated into the .NET framework. WHAT IS ASP.NET? ASP.NET is part of the .NET framework. ASP.NET programs are centralized applications hosted on one or more Web servers that respond dynamically to client requests. The responses are dynamic because ASP.NET intercepts requests for pages with a specific extension (.aspx or .ascx) and hands off the responsibility for answering those requests to justin-time (JIT) compiled code files that can build a response on-the-fly.

ASP.NET deals specifically with configuration (web.config and machine.config) files, Web Services (ASMX) files, and Web Forms (ASPX) files. The server doesnt serve any of these file typesit returns the appropriate content type to the client. The configuration file types contain initialization and settings for a specific application or portion of an application. Another configuration file, called machine.web, contains machine-level initialization and settings. The server ignores requests for web files, because serving them might constitute a security breach. Client requests for these file types cause the server to load, parse, and execute code to return a dynamic response. For Web Forms, the response usually consists of HTML or WML. Web Forms maintain state by round-tripping user interface and other persistent values between the client and the server automatically for each request. A request for a Web Form can use View State, Session State, or Application State to maintain values between requests. Both Web Forms and Web Services requests can take advantage of ASP. Nets integrated security and data access through ADO.NET, and can run code that uses system services to construct the response. So the major difference between a static request and a dynamic request is that a typical Web request references a static file. The server reads the file and responds with the contents of the requested file. ASP.NET uses .NET languages. ASP.NET code exists in multithreaded JIT compiled DLL assemblies, which can be loaded on

demand. Once loaded, the ASP.NET DLLs can service multiple requests from a single in-memory copy. ASP.NET supports all the .NET languages (currently C#, C++, VB.NET, and JScript, but there are well over 20 different languages in development for .NET), so you will eventually be able to write Web applications in your choice of almost any modern programming language. In addition to huge increases in speed and power, ASP.NET provides substantial development improvements, like seamless server-toclient debugging, automatic validation of form data. Fig2. Interoperability

ASP.NET EVENTS .NET events Every time an ASP.NET page is viewed, many tasks are being performed behind the scenes. Tasks are performed at key points ("events") of the page's execution lifecycle. The most common events are: OnInit The first event in our list to be raised is OnInit. When this event is raised, all of the page's server controls are initialized with their property values. Post Back values are not applied to the controls at this time. On Load The next event to be raised is On Load, which is the most important event of them all as all the pages server controls will have their Post Back values now. Post Back Events Next all the Post Back events are raised. These events are only raised when the page view is the result of a Post Back. The order that these events are raised can't be defined or relied upon; the only consistency with the order that Post Back events are raised is that they are all raised between the Unload and OnPreRender events. OnPreRender This event is raised just prior to the page or server control's html output being written into the response stream that's sent to the client web browser. This is last chance you have to make any modifications. By this point, all the server controls on the page have the final data applied.

On Unload This is the last event in our list to be raised and you should destroy any un-managed objects and close any currently open database connection at this point. It is not possible to modify any controls on the page at this point as the response stream has already been sent to the client web browser. As each event of the page is raised it also automatically tells all its child controls to raise their own implementation of the same event. In turn each of those controls will tell its own child controls to do the same and so on down the control tree till all controls have done so. Then execution flow is passed back to the main page class to continue onto the next event and the process is repeated for that event. MAIN FEATURES OF ASP.NET Successor of Active Server Pages (ASP), but completely different architecture Object-oriented Event-based Rich library of Web Controls Separation of layout (HTML) and logic (e.g. C#) Compiled languages instead of interpreted languages GUI can be composed interactively with Visual Studio .NET Better state management NAMESPACES ASP.NET uses a concept called namespaces. Namespaces are hierarchical object models that support various properties and methods. For example,

HTML server controls reside in "System.web.UI.HtmlControls" namespace, web server controls reside in System.web.UI.WebControls" namespace and ADO+ resides in "System. Data" namespace. LANGUAGE INDEPENDENT An ASP.NET page can be created in any language supported by .NET framework. Currently .NET framework supports VB, C#, JScript and Managed C++. ASP.NET SERVER CONTROLS Using ASP.NET Server Controls, browser variation is handled because these controls output the HTML themselves based on the browser requesting the page. TYPES OF CONTROLS ASP.NET has two basic types of controls: HTML server controls and Web server controls.HTML Server Controls are generated around specific HTML elements and the ASP.NET engine changes the attributes of the elements based on server-side code that you provide. Web server controls revolve more around the functional you need on the page. The ASP.NET engine takes the extra steps to decide based upon the container of the requester, what HTML to output.

Fig 3. Web Controls

ADO.NET ADO.NET provides a set of classes which a script can use to interact with databases. Scripts can create instances of ADO.NET data classes and access their properties and methods. A set of classes which work with a specific type of database is known as a .NET Data Provider. ADO.NET comes with two Data Providers, the SQL Server.NET Data Provider (which provides optimised access for Microsoft SQL Server databases) and the OLEDB.NET Data Provider, which works with a range of databases. The main ADO.NET OLEDB data access classes are OLEDBConnection, OLEDBDataAdapter. OLEDBCommand, OLEDBDataReader and

FEATURES OF SQL SERVER 2000 The OLAP Services feature available in SQL Server version 7.0 is now called SQL Server 2000 Analysis Services. The term OLAP Services has been replaced with the term Analysis Services. Analysis Services also includes a new data mining component. The Repository component available in SQL Server version 7.0 is now called Microsoft SQL Server 2000 Meta Data Services. References to the component now use the term Meta Data Services. The term repository is used only in reference to the repository engine within Meta Data Services SQL-SERVER database consist of five type of objects, They are, 1. TABLE 2. QUERY 3. FORM 4. REPORT 5. MACRO TABLE A database is a collection of data about a specific topic.

VIEWS OF TABLE We can work with a table in two types, 1. Design View 2. Datasheet View Design View To build or modify the structure of a table we work in the table design view. We can specify what kind of data will be hold.

Datasheet View To add, edit or analyses the data itself we work in tables datasheet view mode. QUERY A query is a question that has to be asked the data. Access gathers data that answers the question from one or more table. The data that make up the answer is either dynaset (if you edit it) or a snapshot(it cannot be edited).Each time we run query, we get latest information in the dynaset.Access either displays the dynaset or snapshot for us to view or perform an action on it ,such as deleting or updating. FORMS A form is used to view and edit information in the database record by record .A form displays only the information we want to see in the way we want to see it. Forms use the familiar controls such as textboxes and checkboxes. This makes viewing and entering data easy. views of Form We can work with forms in several primarily there are two views, They are, 1. Design View 2. Form View

Design View To build or modify the structure of a form, we work in forms design view. We can add control to the form that are bound to fields in a table or query, includes textboxes, option buttons, graphs and pictures. Form View The form view which display the whole design of the form. REPORT A report is used to vies and print information from the database. The report can ground records into many levels and compute totals and average by checking values from many records at once. Also the report is attractive and distinctive because we have control over the size and appearance of it. MACRO A macro is a set of actions. Each action in macros does something. Such as opening a form or printing a report .We write macros to automate the common tasks the work easy and save the time. SYSTEM ANALYSIS FEASIBILITY STUDY The feasibility of the project is analyzed in this phase and business proposal is put forth with a very general plan for the project and some cost estimates. During system analysis the feasibility study of the proposed system is to be carried out. This is to ensure that the proposed

system is not a burden to the company.

For feasibility analysis, some

understanding of the major requirements for the system is essential. Three key considerations involved in the feasibility analysis are ECONOMICAL FEASIBILITY TECHNICAL FEASIBILITY SOCIAL FEASIBILITY ECONOMICAL FEASIBILITY This study is carried out to check the economic impact that the system will have on the organization. The amount of fund that the company can pour into the research and development of the system is limited. The expenditures must be justified. Thus the developed system as well within the budget and this was achieved because most of the technologies used are freely available. Only the customized products had to be purchased. TECHNICAL FEASIBILITY This study is carried out to check the technical feasibility, that is, the technical requirements of the system. Any system developed must not have a high demand on the available technical resources. This will lead to high demands on the available technical resources. This will lead to high demands being placed on the client. The developed system must have a modest requirement, as only minimal or null changes are required for implementing this system.

SOCIAL FEASIBILITY The aspect of study is to check the level of acceptance of the system by the user. This includes the process of training the user to use the system efficiently. The user must not feel threatened by the system, instead must accept it as a necessity. The level of acceptance by the users solely depends on the methods that are employed to educate the user about the system and to make him familiar with it. His level of confidence must be raised so that he is also able to make some constructive criticism, which is welcomed, as he is the final user of the system. EXISTING SYSTEM The existing system is manual system.Like yahoo or gmail websites we can send only 10MB files .we have to down load the files in the particular websites.we cant invite any friends in this system. we cant easily share our folders.we have to store only limited amount of documents which is private. DRAWBACKS Some of the drawbacks are: 1. The system becomes very slow and not to share the documents easily. 2. We have to store limited documents. 3. Report generation is tedious process. 4. More time consuming.

PROPOSED SYSTEM It is difficult to note down all the problems manually. Instead it is decided to develop a DOCUMENT VERSION CONTROLLER to overcome this drawbacks. A system is required which is being capable of elimination all the problems and become useful to store more than 10MB of files,images, songs,videos.we easily invite the friends and upload their details. BENEFITS 1. We can easily maintain the download details 2. Report generation is easier. 3. We easily create the folders. 4. Monitor the status of the entire at any time and the verification of reports generated by the admin. 5. Less time consuming. PROJECT DESCRIPTION The project entitled as DOCUMENT VERSION REGULATOR developed using ASP.NET using C# and back end as SQL SERVER 2000.This module contains only admin module, The admin enter into the website the above content are displayed as follows, Invite to friends Edit profiles Create folder Download Upload View folder

Invite to friends This module is used to invite friends to any other websites. In the admin logon with login and password and click add friends button. The friends e-mail id is displayed in the screen. In that we add, update and delete the friends details. Edit profiles In this module we enter the friends personal profile and we have to upload the photos in the screen and save in the database. This will help to the user to easily change and update their details through online to view by other users. Create Folder In this module we create the new folder public or private. If the folder mode is public any user can access the details of the folder and used as an own details. If the folder mode is private only the authorized user can access the folder details. These folder contains details about images, video and text details of the authorized users only. Down load In this module we can search the images, songs, videos and files and download all the items and store it in the database. If the folder mode is public any user can download the details of the folder and used as an own details.If the folder mode is private only the authorized user can download the folder details. These download folder contains details about images, video and text details of the authorized users only.

Upload In this module we upload the files which are already stored in the system and download the files and stored in the database. If the folder mode is public any user can upload the details to any user. If the folder mode is private only the authorized user can upload the folder details. View folder In this module the admin can view all the folders which created by the public and private users. SYSTEM DESIGN INPUT DESIGN Input design is the process of converting user-originated inputs to a computer-based 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 web forms with various methods. For example, in the Admin form, the empty username and password is not allowed. The username if exists in the database, the input is considered to be invalid and is not accepted. Likewise, during the Download process, the download images, videos, documents, songs will be noted. 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. In the project,the ouput is to create the new folders,invite friendsand download the files in the website. DATABASE DESIGN The database design is a must for any application developed especially more for the data store projects. Since the chatting method involves storing the message in the table and produced to the sender and receiver, proper handling of the table is a must. In the project, login table is designed to be unique in accepting the username and the length of the username and password should be greater than zero. In this database design the admin details and the common website details are stored in the database. The different users view the data in different format according to the privileges given. The complete listing of the tables and their fields are provided in the annexure under the title Table Structure.

DATA FLOW DIAGRAM

Admin

Tbl_login

Invite to friends

loginid

Edit profile

Profile registration Create folder

Create folders

Download File upload upload

View folders

Create folder

DATA TABLE STRUCTURE

Create folder

Email

File upload

Image view

Login

Login id

Profile registration

Image preview

Login

Uploaded

SYSTEM IMPLEMENTATION Implementation is the stage of the project when the theoretical design is turned out into a working system. Thus it can be considered to be the most critical stage in achieving a successful new system and in giving the user, confidence that the new system will work and be effective. The implementation stage involves careful planning, investigation of the existing system and its constraints on implementation, designing of methods to achieve changeover and evaluation of changeover methods. Implementation is the process of converting a new system design into operation. It is the phase that focuses on user training, site preparation

and file conversion for installing a candidate system. The important factor that should be considered here is that the conversion should not disrupt the functioning of the organization.

SCOPE FOR FUTURE ENHANCEMENTS The project has covered almost all the requirements. Further requirements and improvements can easily be done since the coding is mainly structured or modular in nature. Improvements can be appended by changing the existing modules or adding new modules. One important development that can be added to the project in future is file level backup, which is presently done for folder level.

SOURCE CODINGS Search 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; public partial class Home_Search : System.Web.UI.Page { string str; componentcon c = new componentcon();

protected void Button1_Click(object sender, EventArgs e) { c.con.Open(); if (DropDownList1.SelectedIndex == 0) { Response.Write("Please Select the Category of your Search"); } else { if (RadioButtonList1.SelectedIndex == 0) { if (DropDownList1.SelectedIndex == 1) { str = "SELECT * FROM FILEUPLOAD WHERE FILEEXTENSION LIKE '" + "%" + TextBox1.Text + "%" + "' AND EMAILID='" + Session["EMAILID"].ToString() + "'"; } else { str = "SELECT * FROM FILEUPLOAD WHERE FILENAME LIKE '" + "%" + TextBox1.Text + "%" + "' AND EMAILID='" + Session["EMAILID"].ToString() + "'"; } } else { if (DropDownList1.SelectedIndex == 1) {

str = "SELECT * FROM FILEUPLOAD WHERE FILEEXTENSION LIKE '" + "%" + TextBox1.Text + "%" + "' AND CATEGORY NOT LIKE '%private%'"; } else { str = "SELECT * FROM FILEUPLOAD WHERE FILENAME LIKE '" + "%" + TextBox1.Text + "%" + "' AND CATEGORY NOT LIKE '%private%' "; } } } c.con.Close(); c.DList(str, DataList1); if (DataList1.Items.Count == 0) { Label1.Text = "No Search Results Found"; DataList1.Visible = false; } else { DataList1.Visible = true; } } } Sign in 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 BUSINESSLAYER; using System.Data.SqlClient; public partial class Home_SignIn : System.Web.UI.Page { componentcon c = new componentcon(); Buildconnection cc = new Buildconnection(); protected void Page_Load(object sender, EventArgs e) { Session["EMAILID"] = TextBox1.Text; } protected void Button1_Click(object sender, EventArgs e) { if (TextBox2.Text == "") { Label2.Visible = true; } if (TextBox1.Text == "") { Label1.Visible = true; } else if (TextBox2.Text == "") { Label2.Visible = true; } else { c.con.Open(); string str = "SELECT password FROM tbl_login WHERE userid='" + TextBox1.Text + "'";

SqlCommand comm = new SqlCommand(str, c.con); SqlDataReader dr = comm.ExecuteReader(); while (dr.Read()) { if (TextBox2.Text == dr[0].ToString()) { Response.Redirect("../User/MyHome.aspx"); } else { MESSAGE.Text = "User Not Found"; } } c.con.Close(); } } protected void Button2_Click1(object sender, EventArgs e) { Response.Redirect("~/Home/JoinUs.aspx"); } } Video Documents 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;

public partial class Home_viewdocumentfiles : System.Web.UI.Page { componentcon c = new componentcon(); protected void Page_Load(object sender, EventArgs e) { string search; search = Request.QueryString["search"]; c.DList("select * from FILEUPLOAD where fileextension='" + search + "'", DataList1); } } View file songs 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; public partial class Home_viewfilesongs : System.Web.UI.Page { componentcon c = new componentcon(); protected void Page_Load(object sender, EventArgs e) { string search; search = Request.QueryString["search"]; c.DList("select * from FILEUPLOAD where fileextension='" + search + "'", DataList1); }

} View image files 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; public partial class Home_viewimagesfile : System.Web.UI.Page { componentcon c = new componentcon(); protected void Page_Load(object sender, EventArgs e) { string search; search = Request.QueryString["search"]; c.DList("select * from FILEUPLOAD where fileextension='" + search + "'", DataList1); } } View video files 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; public partial class Home_viewfiles : System.Web.UI.Page { componentcon c = new componentcon(); protected void Page_Load(object sender, EventArgs e) { string search; search=Request.QueryString["search"]; c.DList("select * from FILEUPLOAD where fileextension='" + search + "'", DataList1); } } Folder 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.Drawing; using System.Drawing.Imaging; using System.Drawing.Drawing2D; using System.IO; using System.Data.SqlClient; public partial class User_Folder : System.Web.UI.Page { componentcon c = new componentcon();

protected void Button3_Click(object sender, EventArgs e) { try { string name; string derscription; string choice; name = FOLDERNAME.Text; derscription =FOLDERDESCRIPTION.Text; choice = FOLDERCHOICE.SelectedItem.Text; c.InsertDeleteUpdate("insert into CREATEFOLDER values('" + name + "','" + derscription + "','" + choice + "')"); MESSAGE.Text = "You Successfully Created the Folder"; FOLDERNAME.Text = ""; FOLDERDESCRIPTION.Text = ""; FOLDERCHOICE.Text = ""; } catch (Exception ex) { MESSAGE.Text = ex.Message; } } }

Friends 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 User_Friends : System.Web.UI.Page { componentcon c = new componentcon(); SqlDataReader dr; protected void Button1_Click(object sender, EventArgs e) { string query; query = "select yahooid,gmailid,rediffid from loginid where userid='" + txtemailid.Text + "'"; c.listbox(query,lblist); } protected void btnclear_Click(object sender, EventArgs e) { txtemailid.Text = ""; lblist.Items.Clear(); } protected void Button1_Click1(object sender, EventArgs e) { string query; query = "update loginid set getid='" + lblist.SelectedItem.Text + "' where userid='" + txtemailid.Text + "'"; c.InsertDeleteUpdate(query); } protected void Button2_Click(object sender, EventArgs e) { string query;

query = "update loginid set getid='" + lblist.SelectedItem.Text + "' where userid='" + txtemailid.Text + "'"; c.InsertDeleteUpdate(query); } protected void btnremove_Click(object sender, EventArgs e) { lblist.Items.Remove(lblist.SelectedItem); }} My home 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; public partial class User_MyHome : System.Web.UI.Page { protected void Button1_Click(object sender, EventArgs e) { Response.Redirect("../User/Upload.aspx"); } protected void Button3_Click(object sender, EventArgs e) { Response.Redirect("Folder.aspx"); } protected void Button5_Click(object sender, EventArgs e) { Response.Redirect("../user/Friends.aspx"); } protected void Button2_Click(object sender, EventArgs e) { Response.Redirect("../User/SearchDocuments.aspx"); } protected void Button4_Click(object sender, EventArgs e)

{ Response.Redirect("../user/Myprofile.aspx"); } protected void Button7_Click(object sender, EventArgs e) { Response.Redirect("../user/Viewfolder.aspx"); } } My profile 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; public partial class User_Myprofile1 : System.Web.UI.Page { componentcon c = new componentcon(); protected void Page_Load(object sender, EventArgs e) { TextBox9.Text = Session["EMAILID"].ToString(); } protected void Button1_Click1(object sender, EventArgs e) { string displyname; string gender; string fname; string lname; string dob;

int age; string occuption; string country; string state; string city; string zipcode; string yself; string emailid; string password; TextBox9.Text = Session["EMAILID"].ToString(); displyname = Session["EMAILID"].ToString(); TextBox1.Text = displyname; gender = DropDownList4.SelectedItem.Text; fname = TextBox2.Text; lname = TextBox3.Text; dob = DropDownList1.SelectedItem.Text + "/" + DropDownList2.SelectedItem.Text + "/" + DropDownList3.SelectedItem.Text; age = Convert.ToInt32(TextBox6.Text); occuption = TextBox7.Text; country = DropDownList5.SelectedItem.Text; state = DropDownList6.SelectedItem.Text; city = TextBox5.Text; zipcode = TextBox8.Text; yself = TextBox11.Text; emailid = TextBox9.Text; password = TextBox10.Text; string strfilenameonserver; string strbaselocation; strfilenameonserver = System.IO.Path.GetFileName(uplTheFile.PostedFile.FileName); strbaselocation = "C:\\\\uuuu\\\\"; string filename; filename = System.IO.Path.GetFileName(uplTheFile.PostedFile.FileName); if ((uplTheFile.PostedFile.FileName != ""))

{ uplTheFile.PostedFile.SaveAs(strbaselocation + strfilenameonserver); Session["bpath"] = strfilenameonserver; } else { Label1.Text = ("Error saving <b>" + strbaselocation + strfilenameonserver); } c.InsertDeleteUpdate("insert into PROFILEREGISTRATION values('" + displyname + "','" + gender + "','" + fname + "','" + lname + "','" + dob + "'," + age + ",'" + occuption + "','" + country + "','" + state + "','" + city + "','" + zipcode + "','" + yself + "','" + filename + "','" + emailid + "','" + password + "')"); TextBox1.Text = ""; TextBox2.Text = ""; TextBox3.Text = ""; TextBox5.Text = ""; TextBox6.Text = ""; TextBox7.Text = ""; TextBox8.Text = ""; TextBox9.Text = ""; TextBox10.Text = ""; TextBox11.Text = ""; DropDownList1.Text = ""; DropDownList2.Text = ""; DropDownList3.Text = ""; DropDownList4.Text = ""; DropDownList5.Text = ""; DropDownList6.Text = ""; Label1.Text = "Success Fully Updated";

} }

Search documents 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;

public partial class User_SearchDocuments : System.Web.UI.Page { string str; componentcon c = new componentcon(); protected void Button1_Click(object sender, EventArgs e) { c.con.Open(); if (DropDownList1.SelectedIndex == 0) { Response.Write("Please Select the Category of your Search"); } else { if (RadioButtonList1.SelectedIndex == 0) { if (DropDownList1.SelectedIndex == 1) { str = "SELECT * FROM FILEUPLOAD WHERE FILEEXTENSION LIKE '" + "%" + TextBox1.Text + "%" + "' AND EMAILID='" + Session["EMAILID"].ToString() + "'"; } else {

str = "SELECT * FROM FILEUPLOAD WHERE FILENAME LIKE '" + "%" + TextBox1.Text + "%" + "' AND EMAILID='" + Session["EMAILID"].ToString() + "'"; } } else { if (DropDownList1.SelectedIndex == 1) { str = "SELECT * FROM FILEUPLOAD WHERE FILEEXTENSION LIKE '" + "%" + TextBox1.Text + "%" + "' AND CATEGORY NOT LIKE '%private%'"; } else { str = "SELECT * FROM FILEUPLOAD WHERE FILENAME LIKE '" + "%" + TextBox1.Text + "%" + "' AND CATEGORY NOT LIKE '%private %' "; } } } c.con.Close(); c.DList(str, DataList1); if (DataList1.Items.Count == 0) { Label1.Text = "No Search Results Found"; DataList1.Visible = false; } else { DataList1.Visible = true; } } }

upload 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; public partial class User_Upload : System.Web.UI.Page { componentcon c = new componentcon(); protected void Button1_Click(object sender, EventArgs e) { string filename; string name; string description; string strbaselocation; string choice; string emailid; string filepath; string fileextension; fileextension = System.IO.Path.GetExtension(File1.PostedFile.FileName); filepath = System.IO.Path.GetFullPath(File1.PostedFile.FileName); emailid = Session["EMAILID"].ToString(); choice = RadioButtonList1.SelectedItem.Text; //strbaselocation = "C:\\\\uuuu\\\\"; strbaselocation = Server.MapPath("~\\uploadimages\\"); filename = System.IO.Path.GetFileName(File1.PostedFile.FileName); name = TextBox1.Text; description = TextBox2.Text; if ((File1.PostedFile.FileName) != "") { File1.PostedFile.SaveAs(strbaselocation + filename);

} else { Label1.Text=("Error Saving<b>" + strbaselocation + filename); } string str; str="insert into FILEUPLOAD values('" + emailid + "','" + choice + "','"+filepath+"','" +filename + "','" + fileextension + "','"+name+"','"+description+"')"; c.InsertDeleteUpdate(str); Label1.Text = "Success Fully Send"; TextBox1.Text = ""; TextBox2.Text = "";

} }

SCREEN LAYOUTS
HOME

SIGNIN

HOME

FRIENDS

MYPROFILE

FOLDER

DOCUMENTS

VIEW VIDEO FILES

VIEW IMAGE FILES

VIEW SONGS FILE

VIEW DOCUMENT FILES

UPLOAD

VIEW FOLDER

JOINUS

ABOUTUS

CONTACTUS

CONCLUSION It is concluded that the application works well and satisfy the end users. The application is tested very well and errors are properly debugged. The application is simultaneously accessed from more than one system. Simultaneous login from more than one place is tested. Further enhancements can be made to the application, so that the application functions very attractive and useful manner than the present one. The speed of the transactions become more enough now.

BIBLIOGRAPHY Microsoft Visual Basic.NET Programmers Cook Book: -MATTHEW MACDONALD (Tata McGraw Hill Edition) Microsoft Visual Basic.NET Programmers CookBook: -MATTHEW MACDONALD (Tata McGrawHill Edition) Grey Buczek, .NET developers guide 2002, Prentice-Hall India. Benolt Marchal, VB.NET by example 2003 TataMcGraw- Hill. System Analysis & Design Alenis Leon. An Integral approach to software engineering Pankaj Jalole.