You are on page 1of 65

1.

SYNOPSIS

Metadata removal tool or Metadata scrubber is a type of privacy software


built to protect the privacy of its users by removing potentially privacy-compromising
metadata from files before they are shared with others (e.g. by sending them as e-mail
attachments or by posting them on the Web).

Metadata can be found in many types of files such as documents, spreadsheets,


presentations, images, and audio files. They can include information such as details on
the file authors, file creation and modification dates, document revision history, and
comments.

Since metadata is sometimes not clearly visible in authoring applications


(depending on the application and its settings), there is a risk that the user will be
unaware of its existence or will forget about it and, if the file is shared, private or
confidential information will inadvertently be exposed. The purpose of metadata
removal tools is to minimize the risk of such data leakage.

1
2. ORGANISATION PROFILE

Thamizh Technologies is a professionally managed organization providing


total HR Solutions, Recruitments, Outsourcing and Training to various companies. We
provide services to various types of students which include Engineering, IT,
Management department etc.

 GROUP
We have an enviable history of providing high quality services in the fields of
R&D, Design and Development, Training and HR Consulting in Sivaganga. Our
organization has already established its reputation in offering High quality education in
the areas of Engineering, Arts, Science, and Management Courses.

We have a well-documented quality system, which helps us to monitor measure


and analyze our performance and also to improve our service and delivery standards.
We have a dedicated team of people for monitoring the quality norms.

SERVICES
We dedicate our trainees in Software Development, Human Resource
Consulting, Academic Assistance and Training.

2
3. PROJECT PROFILE

Mail
The internet has grown enormously in the last few decades and very
year sees new and easier ways of accessing the information on it.
However, there are sets of core features that are considered essential tools
on the Internet. One of them is mail.

It is most used feature on the Internet and all service providers give
you a mail account as soon as you sign up. Mail is becoming very popular
because, unlike in regular mail, there is no delay. Postage is not required.
Printing mail address on business cards is becoming as common as
printing the telephone number.

Email address:
An e mail address is very similar to your postal address. Look e-mail
Address given below.
1. User Name: This is the first part of the e-mail address. This is name
chosen by the user to identify that address.
2. Mailbox location: This is the second part of the e-mail address and I
separated from the user name by a “@” symbol and pronounced as
“at”. It indicates the location of you mailbox which is the name of
your ISP, the country you are in and so on.

3
Features
1. Maintain an address book so that you don’t I have to remember add
type cryptic e-mail address every time sends a mail.
2. Inbox: All incoming messages are stored that project.
3. Outbox: All outgoing messages are stored here temporarily before
being sent to the mail server.
4. Sent Items: After a message has been sent to the mail server, it is
removed from the Outbox and a copy is kept in this folder.
5. Deleted Items: all messages deleted from any of the other folders
are stored in the project.
6. Drafts: This project automatically saves all new messages in this
folder while you are composing them.
7. Sending mails: The Create a New Mail Message type the mail
address of the person you want to send in the To field.
8. Receiving mails: To read the mails you have received in the setting
profiles on Check your mails.

Metadata Scrubber
Metadata removal tool or Metadata scrubber is a type of privacy software
built to protect the privacy of its users by removing potentially privacy-
compromising metadata from files before they are shared with others (e.g. by
sending them as e-mail attachments or by posting them on the Web).

4
4. SYSTEM ANALYSIS

4.1 EXISTING SYSTEM


Existing System available in this case are less sensitive; that means they won’t
take care of the failure conditions of any attempts other than login, security modules.
The system to be developed is must be taken much care in implementing the logging
module, otherwise the storage area and the memory consumed for that case will exceed
the normal limit. It may require additional settings to be done to maintain them for
analysis.

4.2 DRAWBACKS OF EXISTING SYSTEM


Metadata can be found in many types of files such as documents, spreadsheets,
presentations, images, and audio files. They can include information such as details on
the file authors, file creation and modification dates, document revision history, and
comments. This leads the hackers to sniffing the highly confidential information.

5
4.3 PROPOSED SYSTEM
In the proposed system, maintaining different category wise security using the
types like roles, responsibilities, and the links with the above two to assign user roles.

4.4 NEED FOR PROPOSED SYSTEM


 There is no chance for know about the Meta data (Information about
information) by the un authorized user.
 Reporting and with the case maintenance with the severity level is easily
give the identity of the event traced and the response to be taken against
the spam mail.
 Analysis will give as further implementation of the system more
secured, and the design of the future system can be modified as per the
results of the analysis of the system proposed.
 The Metadata are identified by the user and the permission for allow
into the user’s mail are given by him to identify the category level with
configured identity explains the development design involved behind the
application.

System proposed in entirely new to the world with the web technology and
application wise security enhancement. Since in all the cases all the systems will take
care of the positive results from the users and they normally won’t care of the issues
regarding the failures, which only can prove the applications reliability and user
interface, and mainly the accessibility control. Our application will surely met that
criteria and it can be included to any module to support the same.

6
5. SYSTEM REQUIREMENTS

5.1. HARDWARE SPECIFICATION


 Processor : Intel PIV.
 RAM : 512 MB.
 Hard Disk : 40GB.
 Display : SVGA.
 Keyboard : 108 Keys.
 Mouse : Optical.
 Digital Storage : CD or DVD

5.2. SOFTWARE SPECIFICATION


 Operating System : Windows XP.
 Frond End : ASP.NET 2005.
 Back End : MS-Access.
 Web Tool : HTML.
 Scripting Tool : VBScript.

7
FRONT END : ASP.NET
ASP.Net, the next generation of visual basic is designed to be the easiest and most
productive tool for creating .NET applications, including Windows applications, Web
Services and Web applications. Active Server Page.NET is a major component of
Microsoft Visual Studio .NET suite. The .NET version of Active Server Page is a new
improved version with more features and additions. After these new additions, VB
qualify to become a full object-oriented language such as C++. ASP.NET is the
following version of VB 6.0. Microsoft .NET is a new programming and operating
framework introduced by Microsoft. All .NET supported languages access a
common .NET library to develop applications and share common tools to execute
applications. Programming with visual basic using .net is called VB.Net.

While providing the traditional ease-of-use of Visual Basic development, Visual


Basic .NET also allows optional use of new language features. Inheritance, method
overloading, structured exception handling, and free threading all make Visual Basic a
powerful object-oriented programming language. Visual Basic .NET fully integrates
with the .NET Framework and the Common Language Runtime, which together
provide language interoperability, simplified deployment, enhanced security, and
improved versioning support.

. NET FRAMEWORK
The .NET Framework is an environment for building, deploying, and running
Web Services and other applications. It is the infrastructure for the overall .NET
Platform. The framework consists of three main parts: the Common Language
Runtime, the class libraries, and ASP.NET.

The Common Language Runtime and class libraries, including Windows Forms,
ADO.NET, and ASP.NET, combine together to provide services and solutions that can
be easily integrated within and across a variety of systems. The .NET Framework
provides a fully managed, protected, and feature-rich application execution
environment, simplified development and deployment, and seamless integration with a
wide variety of languages.

8
Overview of the .NET Framework
The .NET Framework is a managed, type-safe environment for application
development and execution.
It allocates memory for the storage of data and instructions
 Grants or denies the appropriate permissions to your application
 Initiates and manages application execution
 Manages the reallocation of memory for resources that are no longer needed

The .NET Framework consists of two main components


 The Common Language Runtime and
 The .NET Framework class library.

Common Language Runtime


The common language runtime can be thought of as the environment that
manages code execution. It provides core services such
 Code compilation
 Memory allocation
 Thread management, and
 Garbage collection

.NET Framework class library


The .NET Framework class library provides a collection of useful and reusable
types that are designed to integrate with the common language runtime.
 Types are object-oriented and
 Fully extensible

Languages and the .NET Framework


The .NET Framework is designed for cross-language compatibility.This means
that .NET components can interact with each other no matter what language they were
originally written in.

9
This level of cross-language compatibility is possible because of the common
language run time. When a .NET application is compiled, it is converted from the
language it was written in (Visual Basic .NET, C#, or any other .NET compliant
language) to Microsoft Intermediate Language (MSIL or IL). This is a low-level
language designed to be read and understood by the common language run time.
Because all .NET executables and DLLs exist as intermediate language, they can freely
interoperate.

The Common Language Specification defines the minimum standards that


.NET language compilers must conform to, and thus ensures that any source code
compiled by a .NET compiler can interoperate with the .NET Framework.

The Common Type System ensures type compatibility between .NET


components. Because .NET applications are converted to IL prior to deployment and
execution, all primitive data types are represented as .NET types. Thus, a Visual Basic
Integer and a C# int are both represented in IL code as a System.Int32. Because both
languages use a common and interconvertable type system, it is possible to transfer
data between components and avoid time-consuming conversions or hard-to-find
errors.

The Structure of a .NET Application


The primary unit of a .NET application is the assembly. An assembly is a self-
describing collection of code, resources, and metadata. The assembly manifest contains
information about what is contained within the assembly. The assembly manifest
provides
 Identity information, such as the name and version number of the assembly.
 A list of all types exposed by the assembly.
 A list of other assemblies required by the assembly.
 A list of code access security instructions for the assembly. This includes a
list of permissions required by the assembly and permissions to be denied
the assembly

10
Each assembly has one and only one assembly manifest, and it contains all the
description information for the assembly. The assembly manifest can be contained in its
own separate file, or it can be contained within one of the assembly's modules.

Compilation and Execution of a .NET Application


When you compile a .NET application, it is not compiled to binary machine
code; rather, it is converted to IL, which is a low-level set of instructions understood by
the common language run time. This is the form that your deployed application takes—
one or more assemblies consisting of executable files and DLL files in IL form. At least
one of these assemblies will contain an executable file that has been designated as the
entry point for the application.
When execution of your program begins,
1. The first assembly is loaded into memory. At this point, the common
language run time examines the assembly manifest and determines the
requirements to run the program. It examines security permissions requested
by the assembly and compares them to the system's security policy. If the
system's security policy does not allow the requested permissions, the
application will not be run.
2. If the application passes the system's security policy, the common language
run time executes the code.

3. It creates a process for the application to run in and begins application


execution.

4. When execution starts, the first bit of code that needs to be executed is
loaded into memory and compiled into native binary code from IL by the
common language run time's Just-In-Time (JIT) compiler.

Once compiled, the code is executed and stored in memory as native code, so
each portion of code is compiled only once during the execution of an application.
Whenever program execution branches to code that has not yet been executed, the JIT
compiler compiles it ahead of execution and stores it in memory as binary code. This

11
way, application performance is maximized because only the parts of a program that
are executed are compiled.

Some of the services provided by the Execution Support are


 Automatic Memory Management
 Security
 Interoperability with Unmanaged Code
 Cross – Language Debugging Support
 Enhanced Deployment and Versioning Support

12
Components of CLR

Move to Visual Basic.NET


There are significant changes to the language:
 A new optional Error handling structure
 Namespaces
 True Inheritance
 Free threading, and many others.

.NET also provides many other features, such as garbage collection for freeing
up resources, true inheritance for the first time, debugging that works across languages
and against running applications, and the ability to create Windows services and
console applications.

Common Type System


The Common Type System specifies the types supported by the CLR. The types
specified by the CLR include
 Classes— the definition of what will become an object; includes properties,
methods, and events
 Interfaces— the definition of the functionality a class can implement, but does
not contain any implementation code

13
 Value Types—User-defined data types that are passed by value
 Delegates—Similar to function pointers in C++, delegates are often used for
event handling and call-backs

The type system sets out the rules that language compilers must follow to
produce code that is cross-language compatible. By following the type system, vendors
can produce code that is guaranteed to work with code from other languages and other
compilers because all languages are consistent in their use of types.

Integrated Development Environment


Visual Studio .NET provides a single integrated development environment (IDE)
that helps developers build solutions faster using key productivity features accessible
by any .NET language. The IDE is a completely customizable cockpit that enables the
highest performance for developers.  It provides unified access to the designers, editors,
and tools of Visual Studio from any .NET language.

In this system, the concept of ADO.NET will have different requirements for
working with data. In some cases, the user might simply want to display data on a form.
In other cases, the user might need to device a way to share information with another
company. The user might never need to know some of the details of data handling —
for example, user might never need to directly edit an XML file containing data — but
it is very useful to understand the data architecture in ADO.NET.

In traditional client/server applications, components establish a connection to a


database and keep it open while the application is running. Open database connections
take up valuable system resources. In most cases, databases can maintain only a small
number of concurrent connections. The overhead of maintaining these connections
detracts from overall application performance.

Similarly, applications that require an open database connections are extremely


difficult to scale up. An application that does not scale up well might perform
acceptably with four users but will likely not to do so with hundreds.

14
A model based on always-connected data can make it difficult and impractical
to exchange data across application and organizational boundaries using a connected
architecture. If two components need to share the same data, both have to be connected,
and a way must be devised for the components to pass data back and forth.

For all these reasons, data access with ADO.NET is designed around an
architecture that uses connections sparingly. Applications are connected to the database
only long enough to fetch or update the data. Because the database is not holding on to
connections that are largely idle, it can service many more users of languages.

ADO.NET
ActiveX ® Data Objects.NET (ADO.NET), formerly known as ADO+, is a new
set of classes that expose the data access services of the .NET Framework. ADO.NET
is a natural evolution of ADO and is built around N-Tier application development.
ADO.NET has been created with XML at its core.

The ADO.NET object model is composed of two central components: the


connected layer, which consists of the classes that comprise the .NET Data Provider,
and the disconnected layer, which is rooted in the Dataset. 

.NET Data Providers includes the following components: the Connection


object, the Command object, the Data Reader, and the Data Adapter. The first two
should be familiar to existing ADO programmers; they are used to open a connection to
a data source and execute a command against it. The Data Reader loosely corresponds
to a forward-only, read-only

ADO.NET is essentially a collection of classes that expose methods and


attributes used to manage communications between an application and a data store. An

15
integral part of the .NET Framework, ADO.NET simplifies integration of data sharing
in distributed ASP.NET applications.ADO.NET is an expansion of ADO with some of
the key concepts retained. ADO.NET has greatly extended to provide access to
structured data from diverse sources, which are all accommodated in a consistent,
standardized programming model. ADO.NET can be used in any consumer application
that needs to connect to, and communicate with, data sources such as Microsoft SQL
Server, as well as data sources exposed via OLE DB and XML.
The ADO.NET object model is made up
 Data View
 Data Set
 Data Provider
Data View
The Data View speaks to the Dataset and is a special class designed for objects
to bind to and can provide customized views of the Data Set. It provides methods and
properties that enable objects such as a Data Grid to bind to a Dataset and contains
properties such as Allow Edit and Count that allow the object to work with the data in
meaningful ways. A Data View is only used in conjunction with a Dataset and never
with a Data Reader.

Data Set
The Dataset is the core component of the disconnected architecture of
ADO.NET that caches data locally on the client. The Dataset is explicitly designed for
data access independent of any data source. As a result it can be used with multiple and
differing data sources, XML data, or used to manage data local to the application. The
Dataset contains a collection of one or more DataTable objects made up of rows and
columns of data, as well as primary key, foreign key, constraint and relation
information about the data in the DataTable objects.

16
Data Provider

The Data Provider connects to the database on behalf of ADO.NET. It


encapsulates all connections to a database. The Data Provider containing some objects
in it:
 Connection
 Command
 DataAdaptor
 DataReader

Connections
Connections are part of a Data Provider and the Connection object provides
connectivity to a data source. Connections can be opened in two ways:
1. Explicitly by calling the Open method on the connection;
2. Implicitly when using a DataAdapter.

The following examples demonstrate how to create and open connections to


SQL Server (SqlClient) and OLEDB (OleDb) databases.

Closing the Connection


We must always close the Connection when we are finished using it. This can
be done using either the Close or Dispose methods of the Connection object.
Connections are not implicitly released when the Connection object falls out of scope
or is reclaimed by garbage collection.

Commands
The Command object enables access to database commands to return data,
modify data, run stored procedures, and send or retrieve parameter information.
Commands contain information that is submitted to a database as a query, and, like
connections, are represented by the provider-specific classes SqlCommand and OleDb

17
Command. Functionally, once the Connections are established and the Commands are
executed the results are in the form of streams. These resultant streams can be accessed
either by DataReader object, or passed into a DataSet object via a DataAdapter.

The SqlCommand class provides four different methods to execute a command.


They are: ExecuteReader, ExecuteNonQuery, ExecuteScalar and ExecuteXmlReader.

Data Adapters
The DataAdapter provides a set of methods and properties to retrieve and save
data between a DataSet and its source data store. It does the actual work of putting
returned data from a database into a DataSet. It also manages reconciling how data
should be updated against a database. Connections and Commands whose properties
are set early on in code are often passed into DataAdapters for use when their action
methods are invoked. The DataAdapter object encapsulates a set of data commands and
a database connection, which are used to fill the DataSet and update the data source.
Data Readers
When dealing with large read only data, e.g. reading 5,000 rows of data, the
.NET framework includes the DataReader object, which is a read-only, forward-only
stream returned from the database record set. It is a highly optimized, no buffering, and
fire hose-style interface for getting the results of a query executed against the data
source. The Data Adapter provides the bridge between the .NET Data Providers and the
Dataset. The Dataset is a local buffer of tables or a collection of disconnected record
sets.

Database Interactions Are Performed Using Data Commands


To perform operations in a database, you execute SQL statements or stored
procedures (which include SQL statements). You use SQL statements or stored
procedures to read and write rows and perform aggregate functions, such as adding or
averaging. You also use SQL statements or stored procedures to create or modify tables
or columns, to perform transactions, and so on.

18
In ADO.NET you use data commands to package a SQL statement or
stored procedure.

When you want to get the records, do the following:


 Open a connection.
 Call an execute method of the command, which in turn:
 Executes the SQL statement or stored procedure referenced by the command.
 Then closes the connection.
 The connection stays open only long enough to execute the statement or stored
procedure.

Improved Reliability
The .NET Framework takes the core achievements originally made in Windows
2000 and brings them to new levels. With advanced ways of monitoring the health of
running applications, as well as isolating applications from each other, applications
built using the .NET Framework stay up-and-running longer than ever before.
Increased Performance
Thanks in part to advanced compilation and caching techniques, server
applications have never been faster than with the .NET Framework and its ASP.NET
technology. Customers who have moved from ASP to ASP.NET are seeing significant
increases in speed on the order of 300- to 500-percent improvements.

Developer Productivity
Developers of all backgrounds are finding that they can rapidly get up to speed
on the .NET Framework. The intuitiveness of the programming model, the amount of
code already provided in the class libraries and the amount of work that the .NET
Framework handles behind the scenes in areas such as memory management have
enabled .NET Framework developers to reap huge productivity gains.

Security
The code access security technology in the .NET Framework was designed for
today's Internet environments. The .NET Framework can collect evidence about the

19
origin and author of an application. The .NET Framework run-time environment can
then combine that evidence with administrator-set or default security policies to make
fine-grained decisions about whether to run that application or enable it to access a
particular resource. It can even "negotiate" with the application, for example, denying it
the permission to write to a protected directory and enabling the application to choose
whether it will run, given that it has been denied that permission.

Integration with existing systems


The COM intro technology in the .NET Framework generates a wrapper around
your existing COM components and Windows—based applications (such as Microsoft
Office), enabling us to program against them as though they were originally written
using the .NET Framework. Applications built using the .NET Framework can connect
with existing systems and packaged applications—regardless of their underlying
platform.

Mobility Support
The .NET Framework provides one unified programming model for developing
smart client and Web applications for both PCs and mobile devices such as personal
digital assistants (PDAs) and mobile phones.

Native XML Web Service Support


The .NET Framework was designed from the ground up to support XML Web
services, a model for cross-platform, distributed computing based on standard protocols
such as XML, SOAP, and HTTP. Web services can be used to integrate applications
running on different platforms, or to offer software as a service. With the .NET
Framework, an application can be transformed into a Web service with just one simple
line of code.

20
BACKEND: MS-ACCESS
A database program for windows, available separately or included in the
Microsoft office suite. Access is programmable using visual basic for
applications(VBA). Access can read Paradox, dBase and Btrieve files, and using
ODBC, Microsoft SQL Server, SYBASE SQL Server and Oracle data.

Microsoft Access (current full name Microsoft Office Access) is a relational


database management system from Microsoft, packaged with Microsoft Office
Professional which combines the relational Microsoft Jet Database Engine with a
graphical user interface.

Microsoft Access can use data stored in Access/Jet, Microsoft SQL Server,
Oracle, or any ODBC-complaint data container. Skilled software developers and data
architects use it to develop application software. Relatively unskilled programmers and
non-programmer “power users” can use it to build simple applications. It supports

21
some object-oriented (OO) techniques but falls short of being a fully Object-Oriented
development tool.

Microsoft Access was also the name of a communications program from


Microsoft, meant to compete with ProComm and other programs. This Microsoft
Access proved a failure and was dropped. Years later Microsoft reused the name for its
database software.

FEATURES
One of the benefits of Access from a programmers perspective is its relative
compatibility with SQL – queries may be viewed and edited as SQL statements, and
SQL statements can be used directly in Macros and VBA Modules to manipulate
Access tables. Users may mix and use both VBA and “Macros” for programming
forms and logic and offers object-oriented possibilities.

MSDE (Microsoft SQL Server Desktop Engine) 2000, a mini-version of MS


SQL Server 2000, is included with the developer edition of Office XP and may be used
with Access as an alternative to the Jet Database Engine.

Unlike a complete RDBMS, the Jet Engine lacks database triggers and stored
procedures. Starting in MS Access 2000(Jet 4.0), there is a syntax that allows creating
queries with parameters, in a way that looks like creating stored procedures, but these
procedures are limited to one statement per procedure. Microsoft Access does allow
forms to contain code that is trigged as changes are made to the underlying table (as
long as the modifications are done only with that form), and it is common to use pass-
through queries and other techniques in Access to run stored procedures in RDBMS
that support these.

In ADP files (supported in MS Access 2000 and later), the database-related


features are entirely different, because this type of file connects to a MSDE or
Microsoft SQL Server, instead of using the Jet Engine. Thus, it supports the creation of
nearly all objects in the underlying server (tables with constraints and triggers, views,

22
stored procedures and UDF-s). However, only forms, reports, macros and modules are
stored in the ADP file (the other objects are stored in the back-end database).

ACCESSIBILITY FEATURES IN MICROSOFT ACCESS


If you have disabilities, you can do the following to take advantage of
accessibility features in Access:
 View and print list of all available shortcut keys.
 Use the keyboard to define relationship, add or copy text
boxes or other controls on forms and reports, and rearrange
columns in Datasheet view.
 Create a toolbar that consists only the buttons and menus you use
most often for the current databases. You can also increase the size
of the buttons and group related buttons together.

OPERATING SYSTEM : WINDOWS XP


Microsoft Windows XP is software program that makes IBM PC systems easy
to use, it does this by simplifying the computers. User Interface is a buzzword that
refers to the way we give commands to the computer and the way in which we interact
with it.

With windows the user can run programs, enter and move data around and
performs DOS tasks by simply using the mouse to point objects on the screen.
Windows owes its name to the fact it runs each program or each document in its own
separate window. Further, the user can have any number of Windows on the screen at
time, each containing its own program. It is possible to switch between windows easily.

Another advanced feature in windows is that it has clipboard facility. It lets the
user to copy data of different document types, make it easy to cut and paste information
from one application to another.

Features of Windows XP

23
Microsoft windows XP is more compatible and more powerful than any
workstation that you have used before.
- Easier to use
- Easier to manage
- More compatible
- More powerful
- Distributed processing

Easier to Use
Windows XP makes it easier to:
- Work with files
- Find information
- Personalize your computer environment
- Work on the web Work remotely

More compatible
Windows XP offers Increased Compatibility with different types of networks
and with the wide array of legacy hardware and software.

Windows XP also provides


- Improved Driver support
- Increased support for new generation hardware and multimedia
technologies
- Integration of new Symbols

More Powerful
Windows XP provides
- Industrial Strength reliability
- The highest level of security
- Powerful performance

Distributed processing

24
Windows XP allows the connectivity with variety of host environment through
its support of multiple transport protocol an client server facilities.

6. SYSTEM DESIGN

The design of the system is essentially a blue print or a plan for a solution for
the system. At the first level the focus is made which modules are needed for the
system and how modules should be interconnected. This is called system design.

In the second level, the internal design of the modules and how the specification
of the module can be satisfied is decide upon. Thus design level is called detailed
design. Since the detailed design delineates the major characteristics of the system and
also its efficiency. A Design methodology is a systematic approach to create a design
by application of a set of techniques and guidelines.

6.1. STRUCTURE DESIGN

25
6.2. DATA DICTIONARY

Compose Mail

Field Name Data Type Description Field Size


fname Memo First Name 1000
lname Memo Last Name 1000
uname Memo User Name 1000
paswd Memo PassWord 1000
dob Date/time Date Of birth
Gender Text Gender 50
mph Number Mobile Number Long integer
secque Memo Secret Question 1000
ans Memo Answer 1000

Sending Mail

26
Field Name Data Type Description Field Size
ToAd Text To Address 50
CarCopy Text Carbon Copy 50
BCarCopy Text Blind Carbon Copy 50
Sub Text Subject 50
Attach Text Attachments 50
Con Text Contents 50
UName Text User Name 50
DaTi Date/Time Date & Time

Save Draft

Field Name Data Type Description Field Size


ToAd Text To Address 50
CarCopy Text Carbon Copy 50
BCarCopy Text Blind Carbon Copy 50
Sub Text Subject 50
Attach Text Attachments 50
Con Text Contents 50
UName Text User Name 50
DaTi Date/Time Date & Time

Inbox

Field Name Data Type Description Field Name


ToAd Text To Address 50
Sub Text Subject 50
Con Text Content 50
DaTi Text Date & Time
Img Text Image

27
6.3. DATA FLOW DIAGRAM
Data Flow Diagram (DFD) is a directed graph in which the nodes specify
processing activities and the arcs specify data items transmitted between processing
nodes.

Data Flow Diagrams are excellent mechanisms for communicating with


customers during analysis. Data Flow Diagram are quit valuable for establishing
naming conventions and names of system components such as subsystems, files and
data link.

DFD is used to represent the functional relationship of input, process and output
values presented by system. DFD shows how information moves through the system
and how it is modified by series of transformation that are applied as data moves from
input to output. DFD may be used to represent a system at any level of abstraction.

A level 0 DFD also called context diagram represents entire system as a single
module with input to output data indicated by incoming and outgoing allows
respectively. Additional processes and information flow paths are represent as a level 0
DFD is partitioned to reveal more detail represent the system with major modules, data
flows and data stores, the other levels will show each module in the top level DFD in a
more detailed fashion.

SQUARE:
The Square symbol denotes the source or destination of system data.

28
 ARROW:
The arrow marks identifies the flow of information it is like a PIPELINE
CIRCLE:
The circle or bubble or an oval symbol is used to specify the incoming data flow
or the outgoing data flow.
OPEN RECTANGLE:
An open rectangle is a data store or temporary repository of data.

Level 0:

User
Searc
Outbox h

Mail
Inbox Server Feedback

Thras Addres
s
h

29
Outbox Module

Addnew

Metadat
outbox a Remove
Data
base
Search

30
Inbox Module

Search
inbox Metadat Data
a base
Remove

31
Thrash Module

Retrieve
Thrash
User
Data
base
Remove

Address Module

Addnew

Retrieve

Address Trap Data


Remove
base

Modify

32
7. SYSTEM IMPLEMENTATION

Implementation is the stage, which is crucial in the life cycle of the new system
designed. The main stage in the implementation is planning, training, system testing.
Implementation is converting a new or revised system into an operational one.
Conversion is the main aspect of implementation. It is the process of changing from
the old system to the new one. After system is implemented, user conducts a review of
the system. It is used to gather information for the maintenance of the system. The
basic review method is a data collection method of questionnaire, interview etc.

The proposed system is implemented by direct method in which a new a system


will be designed and implemented. The implementation plan consists of:

 Testing the developed system with sample data.

 Detection and correction of errors.

 Making necessary changes in the system.

 Checking the report with that of the existing system

 Training on new software.

 Installation of new software utilities

33
8. SYSTEM TESTING

The system as a whole was deployed in the ASP.NET 2005 and was tested. The
system was found to be working perfect and an end user has been asked to enter the
data, and further the connected systems has been tested with the sample.

8.1. UNIT TESTING


Unit testing different modules are tested against the specifications produced
during the design of the modules. Unit testing is essential for Verification of the code
produced during the coding phase and hence the goal is to test the internal logic of the
modules. Using the details design description as a guide, important paths are tested to
uncover errors with in the boundary of the Modules. This testing was carried out during
the programming stage itself.

In this type of testing step, each module was bound to be working satisfactorily
as regards to be expected output from module .Unit testing is performed and to be
working in “Metadata Scrubber”.

8.2. INTEGRATION TESTING


System has been partitioned into sub Modules .The integration of them must be
subjected to a strong checking, so that data gets prevented from loss across the
interface. Thus Integration Testing system is subjected to integration.

34
8.3. SYSTEM TESTING
System Testing involves two kinds of activities: Integration Testing and
Acceptance Testing. Strategies for integrating software components into a functioning
product include the bottom-up strategy, the top-down strategy and the sandwich
strategy. Acceptance Testing involves planning and execution of the functional tests,
performance tests and the stress tests to verify that the implemented system satisfies its
requirements.
System testing does not test the module wise, but the integration of each module
in the systems. System testing helps to find in discrepancies between the original
objectives of the system.

8.4. ACCEPTANCE TESTING


Acceptance testing is done with live data provided by the administrator to
ensure that the software works satisfactorily. Acceptance testing focuses on the external
behavior of the system. Giving inputs from actual data tested the system and the results
were found to be satisfactory. The reference document for system testing
implementation using the various design concepts, a detailed design of the process,
inputs and outputs are done as mentioned in above sections. This leads to the further
stages of implementation using Active Server Page. The software is implementing
incorporating all mentioned features successfully and the outcome is found satisfactory.
Successfully, collecting sample data and testing it in the organization implement this
system.

35
9. CONCLUSION

The system has been developed for the present requirement and it works
satisfactorily under all circumstances that may arise in the real environment. It caters to
need of organizations effectively.

By using this meta data scrubber, all the information about a file or a mail
attachment are removed within a fraction of time. This makes the hackers not to access
the other files in a secured place.

Since metadata is sometimes not clearly visible in authoring applications


(depending on the application and its settings), there is a risk that the user will be
unaware of its existence or will forget about it and, if the file is shared, private or
confidential information will inadvertently be exposed. The purpose of metadata
removal tools is to minimize the risk of such data leakage.

36
APPENDIX – A
SCREEN SHOTS

37
38
39
40
41
42
43
44
45
46
47
APPENDIX – B
SOURCE CODE

Compose.aspx
Imports System.Data.SqlClient
Public Class adcompose
Inherits System.Web.UI.Page
Dim cn As SqlConnection
Protected WithEvents Image1 As System.Web.UI.WebControls.Image
Protected WithEvents Image2 As System.Web.UI.WebControls.Image
Dim adap As SqlDataAdapter

#Region " Web Form Designer Generated Code "


<System.Diagnostics.DebuggerStepThrough()> Private Sub InitializeComponent()
End Sub

Protected WithEvents TextBox1 As System.Web.UI.WebControls.TextBox


Protected WithEvents Button8 As System.Web.UI.WebControls.Button
Protected WithEvents Label1 As System.Web.UI.WebControls.Label
Protected WithEvents Button2 As System.Web.UI.WebControls.Button
Protected WithEvents Button1 As System.Web.UI.WebControls.Button
Protected WithEvents TextBox3 As System.Web.UI.WebControls.TextBox
Protected WithEvents DropDownList1 As
System.Web.UI.WebControls.DropDownList

48
Private Sub Page_Init(ByVal sender As System.Object, ByVal e As
System.EventArgs) Handles MyBase.Init
InitializeComponent()
End Sub
Private Sub Page_Load(ByVal sender As System.Object, ByVal e As
System.EventArgs) Handles MyBase.Load
strpath = Server.MapPath(".") & "\CITS.mdb"
strconnect = "Provider=Microsoft.Jet.oledb.4.0;Data Source=" & strpath
fillvalues()
End Sub

Private Sub Button2_Click(ByVal sender As System.Object, ByVal e As


System.EventArgs) Handles Button2.Click
TextBox1.Text = ""
TextBox3.Text = ""
Label1.Text = ""
End Sub
Private Sub Button1_Click(ByVal sender As System.Object, ByVal e As
System.EventArgs) Handles Button1.Click
Dim ids As Integer
Try
cn = New SqlConnection(constr)
Dim stselect As String
stselect = "select inboxid from uinbox order by inboxid"
adap = New SqlDataAdapter(stselect, cn)
Dim dtable As New DataTable
Dim drow As DataRow
adap.Fill(dtable)
For Each drow In dtable.Rows
ids = drow(0)
Next
ids = ids + 1

49
Catch ex As Exception
Response.Write(ex.ToString)
End Try
Try
cn = New SqlConnection(constr)
Dim stselect As String
Dim d As Date = Now.Date
stselect = "insert into uinbox values (" & ids & ",'" & d & "','" & TextBox1.Text
& "','" & TextBox3.Text & "','" & DropDownList1.SelectedItem.ToString & "')"
Dim cmd As SqlCommand
cn.Open()
cmd = New SqlCommand(stselect, cn)
cmd.ExecuteNonQuery()
cn.Close()
Label1.Text = "Successfully Inserted"
Catch ex As Exception
Response.Write(ex.ToString)
End Try
End Sub

Private Sub Button8_Click(ByVal sender As System.Object, ByVal e As


System.EventArgs) Handles Button8.Click
Response.Redirect("WelAdmin.aspx")
End Sub

Adinbox.aspx
Imports System.Data.SqlClient
Public Class adinbox
Inherits System.Web.UI.Page
Dim cn As SqlConnection
Protected WithEvents Button8 As System.Web.UI.WebControls.Button

50
Protected WithEvents Image1 As System.Web.UI.WebControls.Image
Protected WithEvents Image2 As System.Web.UI.WebControls.Image
Dim adap As SqlDataAdapter

#Region " Web Form Designer Generated Code "


<System.Diagnostics.DebuggerStepThrough()> Private Sub InitializeComponent()
End Sub

Private designerPlaceholderDeclaration As System.Object


Private Sub Page_Init(ByVal sender As System.Object, ByVal e As
System.EventArgs) Handles MyBase.Init
InitializeComponent()
End Sub
#End Region

Private Sub Page_Load(ByVal sender As System.Object, ByVal e As


System.EventArgs) Handles MyBase.Load
'Put user code to initialize the page here
strpath = Server.MapPath(".") & "\CITS.mdb"
strconnect = "Provider=Microsoft.Jet.oledb.4.0;Data Source=" & strpath
fillvalues()
Private Sub fillvalues()
Try
cn = New SqlConnection(constr)
Dim stselect As String
stselect = "select * from admininbox"
adap = New SqlDataAdapter(stselect, cn)
Dim dtable As New DataTable
Dim drow As DataRow
adap.Fill(dtable)
Response.Write("<br><br><br><br><br><center><table border=1><tr><th>
From <th> Date <th>Subject")

51
For Each drow In dtable.Rows
Response.Write("<tr><td> " & drow(1) & "<td>" & drow(2) & "<td><a
href=adminview.aspx?mesid=" & drow(0) & ">" & drow(3) & "</a>")
Next
Response.Write("</table>")
Catch ex As Exception
Response.Write(ex.ToString)
End Try
End Sub

Private Sub Button8_Click(ByVal sender As System.Object, ByVal e As


System.EventArgs) Handles Button8.Click
Response.Redirect("weladmin.aspx")
End Sub

Private Sub ImageButton1_Click(ByVal sender As System.Object, ByVal e As


System.Web.UI.ImageClickEventArgs)

Clientform.aspx
Imports System.Data.SqlClient
Public Class clientform
Inherits System.Web.UI.Page
Dim cn As New SqlConnection
Protected WithEvents Button8 As System.Web.UI.WebControls.Button
Protected WithEvents Label1 As System.Web.UI.WebControls.Label
Protected WithEvents DropDownList1 As
System.Web.UI.WebControls.DropDownList
Protected WithEvents DropDownList2 As
System.Web.UI.WebControls.DropDownList
Protected WithEvents DropDownList3 As
System.Web.UI.WebControls.DropDownList

52
Protected WithEvents Button3 As System.Web.UI.WebControls.Button
Protected WithEvents Button2 As System.Web.UI.WebControls.Button
Protected WithEvents Button1 As System.Web.UI.WebControls.Button
Protected WithEvents TextBox1 As System.Web.UI.WebControls.TextBox
Protected WithEvents TextBox2 As System.Web.UI.WebControls.TextBox
Protected WithEvents TextBox3 As System.Web.UI.WebControls.TextBox
Protected WithEvents TextBox4 As System.Web.UI.WebControls.TextBox
Protected WithEvents Label3 As System.Web.UI.WebControls.Label
Dim adap As SqlDataAdapter
Protected WithEvents TextBox5 As System.Web.UI.WebControls.TextBox
Protected WithEvents Image1 As System.Web.UI.WebControls.Image
Protected WithEvents Image2 As System.Web.UI.WebControls.Image
Dim adap1 As SqlDataAdapter

#Region " Web Form Designer Generated Code "


<System.Diagnostics.DebuggerStepThrough()> Private Sub InitializeComponent()
End Sub

Private designerPlaceholderDeclaration As System.Object


Private Sub Page_Init(ByVal sender As System.Object, ByVal e As
System.EventArgs) Handles MyBase.Init
InitializeComponent()
End Sub
#End Region

Private Sub Page_Load(ByVal sender As System.Object, ByVal e As


System.EventArgs) Handles MyBase.Load
Dim intLoopIndex As Integer
For intLoopIndex = 0 To 2
Next
strpath = Server.MapPath(".") & "\CITS.mdb"
strconnect = "Provider=Microsoft.Jet.oledb.4.0;Data Source=" & strpath

53
fillvalues()
fill1values()
End Sub

Private Sub Button2_Click(ByVal sender As System.Object, ByVal e As


System.EventArgs) Handles Button2.Click
TextBox1.Text = ""
TextBox2.Text = ""
TextBox3.Text = ""
TextBox4.Text = ""
TextBox5.Text = ""
Label3.Text = ""
End Sub

Private Sub fill1values()


If Page.IsPostBack = True Then
Else
DropDownList2.Items.Clear()
Try
cn = New SqlConnection(constr)
Dim stselect1 As String
stselect1 = "select availprojecttitle from Cregis"
adap1 = New SqlDataAdapter(stselect1, cn)
Dim dtable As New DataTable
Dim drow As DataRow
adap1.Fill(dtable)
For Each drow In dtable.Rows
DropDownList2.Items.Add(drow(0))
Next
Catch ex As Exception
Response.Write(ex.ToString)
End Try

54
End If
End Sub

Private Sub Button8_Click(ByVal sender As Object, ByVal e As System.EventArgs)


Handles Button8.Click
Response.Redirect("clientdetail.aspx")
End Sub

Private Sub Button1_Click(ByVal sender As Object, ByVal e As System.EventArgs)


Handles Button1.Click
Response.Redirect("weladmin.aspx")
Try
cn = New SqlConnection(constr)
Dim stselect As String
stselect = "insert into clientregis values ('" &
DropDownList1.SelectedItem.ToString & "','" & TextBox1.Text & "','" &
TextBox2.Text & "','" & Val(TextBox3.Text) & "'," & TextBox4.Text &
Dim cmd As SqlCommand
cn.Open()
cmd = New SqlCommand(stselect, cn)
cmd.ExecuteNonQuery()
cn.Close()
Label1.Text = "Successfully Inserted"
Catch ex As Exception
Response.Write(ex.ToString)
End Try
End Sub

Private Sub Button3_Click(ByVal sender As System.Object, ByVal e As


System.EventArgs) Handles Button3.Click
Response.Redirect("Homenew.aspx")
End Sub

55
Private Sub DropDownList2_SelectedIndexChanged(ByVal sender As System.Object,
ByVal e As System.EventArgs) Handles DropDownList2.SelectedIndexChanged
If DropDownList2.SelectedItem.Text = "Networkmonitoring" And
DropDownList2.SelectedIndex = 0 Then
Label3.Text = ""
Label3.Text = "This is Network Project"
ElseIf DropDownList2.SelectedItem.Text = " Punch Card Reader " And
DropDownList2.SelectedIndex = 1 Then
Label3.Text = ""
Label3.Text = "Reduces user's work by providing authentication to user's "
ElseIf DropDownList2.SelectedItem.Text = "Congestion control" And
DropDownList2.SelectedIndex = 2 Then
Label3.Text = ""
Label3.Text = “Provides solution to easier Traffic Routing”
End If
End Sub

strconnect = "Provider=Microsoft.Jet.oledb.4.0;Data Source=" & strpath


fillvalues()
End Sub

Private Sub Button2_Click(ByVal sender As System.Object, ByVal e As


System.EventArgs) Handles Button2.Click
TextBox1.Text = ""
TextBox3.Text = ""
Label1.Text = ""
End Sub
Private Sub Button1_Click(ByVal sender As System.Object, ByVal e As
System.EventArgs) Handles Button1.Click
Dim ids As Integer
Try
cn = New SqlConnection(constr)

56
Dim stselect As String
stselect = "select inboxid from uinbox order by inboxid"
adap = New SqlDataAdapter(stselect, cn)
Dim dtable As New DataTable
Dim drow As DataRow
adap.Fill(dtable)
For Each drow In dtable.Rows
ids = drow(0)
Next
ids = ids + 1
Catch ex As Exception
Response.Write(ex.ToString)
End Try
Try
cn = New SqlConnection(constr)
Dim stselect As String
Dim d As Date = Now.Date
stselect = "insert into uinbox values (" & ids & ",'" & d & "','" & TextBox1.Text
& "','" & TextBox3.Text & "','" & DropDownList1.SelectedItem.ToString & "')"
Dim cmd As SqlCommand
cn.Open()
cmd = New SqlCommand(stselect, cn)
cmd.ExecuteNonQuery()
cn.Close()
Label1.Text = "Successfully Inserted"
Catch ex As Exception
Response.Write(ex.ToString)
End Try
End Sub

Private Sub Button8_Click(ByVal sender As System.Object, ByVal e As


System.EventArgs) Handles Button8.Click

57
Response.Redirect("WelAdmin.aspx")
End Sub

Adinbox.aspx
Imports System.Data.SqlClient
Public Class adinbox
Inherits System.Web.UI.Page
Dim cn As SqlConnection
Protected WithEvents Button8 As System.Web.UI.WebControls.Button
Protected WithEvents Image1 As System.Web.UI.WebControls.Image
Protected WithEvents Image2 As System.Web.UI.WebControls.Image
Dim adap As SqlDataAdapter

#Region " Web Form Designer Generated Code "


<System.Diagnostics.DebuggerStepThrough()> Private Sub InitializeComponent()
End Sub

Private designerPlaceholderDeclaration As System.Object


Private Sub Page_Init(ByVal sender As System.Object, ByVal e As
System.EventArgs) Handles MyBase.Init
InitializeComponent()
End Sub
#End Region

Private Sub Page_Load(ByVal sender As System.Object, ByVal e As


System.EventArgs) Handles MyBase.Load
'Put user code to initialize the page here
strpath = Server.MapPath(".") & "\CITS.mdb"
strconnect = "Provider=Microsoft.Jet.oledb.4.0;Data Source=" & strpath
fillvalues()
Private Sub fillvalues()

58
Try
cn = New SqlConnection(constr)
Dim stselect As String
stselect = "select * from admininbox"
adap = New SqlDataAdapter(stselect, cn)
Dim dtable As New DataTable
Dim drow As DataRow
adap.Fill(dtable)
Response.Write("<br><br><br><br><br><center><table border=1><tr><th>
From <th> Date <th>Subject")
For Each drow In dtable.Rows
Response.Write("<tr><td> " & drow(1) & "<td>" & drow(2) & "<td><a
href=adminview.aspx?mesid=" & drow(0) & ">" & drow(3) & "</a>")
Next
Response.Write("</table>")
Catch ex As Exception
Response.Write(ex.ToString)
End Try
End Sub

Private Sub Button8_Click(ByVal sender As System.Object, ByVal e As


System.EventArgs) Handles Button8.Click
Response.Redirect("weladmin.aspx")
End Sub

Private Sub ImageButton1_Click(ByVal sender As System.Object, ByVal e As


System.Web.UI.ImageClickEventArgs)

Clientform.aspx
Imports System.Data.SqlClient
Public Class clientform

59
Inherits System.Web.UI.Page
Dim cn As New SqlConnection
Protected WithEvents Button8 As System.Web.UI.WebControls.Button
Protected WithEvents Label1 As System.Web.UI.WebControls.Label
Protected WithEvents DropDownList1 As
System.Web.UI.WebControls.DropDownList
Protected WithEvents DropDownList2 As
System.Web.UI.WebControls.DropDownList
Protected WithEvents DropDownList3 As
System.Web.UI.WebControls.DropDownList
Protected WithEvents Button3 As System.Web.UI.WebControls.Button
Protected WithEvents Button2 As System.Web.UI.WebControls.Button
Protected WithEvents Button1 As System.Web.UI.WebControls.Button
Protected WithEvents TextBox1 As System.Web.UI.WebControls.TextBox
Protected WithEvents TextBox2 As System.Web.UI.WebControls.TextBox
Protected WithEvents TextBox3 As System.Web.UI.WebControls.TextBox
Protected WithEvents TextBox4 As System.Web.UI.WebControls.TextBox
Protected WithEvents Label3 As System.Web.UI.WebControls.Label
Dim adap As SqlDataAdapter
Protected WithEvents TextBox5 As System.Web.UI.WebControls.TextBox
Protected WithEvents Image1 As System.Web.UI.WebControls.Image
Protected WithEvents Image2 As System.Web.UI.WebControls.Image
Dim adap1 As SqlDataAdapter

#Region " Web Form Designer Generated Code "


<System.Diagnostics.DebuggerStepThrough()> Private Sub InitializeComponent()
End Sub

Private designerPlaceholderDeclaration As System.Object


Private Sub Page_Init(ByVal sender As System.Object, ByVal e As
System.EventArgs) Handles MyBase.Init
InitializeComponent()

60
End Sub
#End Region

Private Sub Page_Load(ByVal sender As System.Object, ByVal e As


System.EventArgs) Handles MyBase.Load
Dim intLoopIndex As Integer
For intLoopIndex = 0 To 2
Next
strpath = Server.MapPath(".") & "\CITS.mdb"
strconnect = "Provider=Microsoft.Jet.oledb.4.0;Data Source=" & strpath
fillvalues()
fill1values()
End Sub

Private Sub Button2_Click(ByVal sender As System.Object, ByVal e As


System.EventArgs) Handles Button2.Click
TextBox1.Text = ""
TextBox2.Text = ""
TextBox3.Text = ""
TextBox4.Text = ""
TextBox5.Text = ""
Label3.Text = ""
End Sub

Private Sub fill1values()


If Page.IsPostBack = True Then
Else
DropDownList2.Items.Clear()
Try
cn = New SqlConnection(constr)
Dim stselect1 As String
stselect1 = "select availprojecttitle from Cregis"

61
adap1 = New SqlDataAdapter(stselect1, cn)
Dim dtable As New DataTable
Dim drow As DataRow
adap1.Fill(dtable)
For Each drow In dtable.Rows
DropDownList2.Items.Add(drow(0))
Next
Catch ex As Exception
Response.Write(ex.ToString)
End Try
End If
End Sub

Private Sub Button8_Click(ByVal sender As Object, ByVal e As System.EventArgs)


Handles Button8.Click
Response.Redirect("clientdetail.aspx")
End Sub

Private Sub Button1_Click(ByVal sender As Object, ByVal e As System.EventArgs)


Handles Button1.Click
Response.Redirect("weladmin.aspx")
Try
cn = New SqlConnection(constr)
Dim stselect As String
stselect = "insert into clientregis values ('" &
DropDownList1.SelectedItem.ToString & "','" & TextBox1.Text & "','" &
TextBox2.Text & "','" & Val(TextBox3.Text) & "'," & TextBox4.Text &
Dim cmd As SqlCommand
cn.Open()
cmd = New SqlCommand(stselect, cn)
cmd.ExecuteNonQuery()
cn.Close()

62
Label1.Text = "Successfully Inserted"
Catch ex As Exception
Response.Write(ex.ToString)
End Try
End Sub

Private Sub Button3_Click(ByVal sender As System.Object, ByVal e As


System.EventArgs) Handles Button3.Click
Response.Redirect("Homenew.aspx")
End Sub
Private Sub DropDownList2_SelectedIndexChanged(ByVal sender As System.Object,
ByVal e As System.EventArgs) Handles DropDownList2.SelectedIndexChanged
If DropDownList2.SelectedItem.Text = "Networkmonitoring" And
DropDownList2.SelectedIndex = 0 Then
Label3.Text = ""
Label3.Text = "This is Network Project"

63
10. BIBLIOGRAPHY

BOOK REFERENCE
o Essential .NET, James S.Miller, Tata McGraw Hill Publications, 2002 Second
Edition.
o ASP.NET Programming, Matt J.Crouch, Neway Publicatons Private Limited,
Third Edition, 2003.
o Programming in the .NET Environment, Damien Watking, Mark Hammond,
Brand Abrams, APress Publications, 2002.

WEBSITE REFERENCE
1. http://code.msdn.microsoft.com/GotDotNet.aspx
2. http://www.devarticles.com/c/b/MSAccess/
3. http://www.aspdotnetheaven.com/

64
65

You might also like