Professional Documents
Culture Documents
2. INTRODUCTION - 4
3. TECHNICAL ASPECTS -6
4. CONCLUSION-12
ABSTRACT
Central Leather Research Institute (CLRI) is one of the leading research institutes
in the world in the field of Leather technology. It is one among the 39 laboratories
of Council of Scientific and Industrial Research (CSIR). We are working for the
CHORD division of CLRI. CHORD stands for Centre for Human & Organizational
Resources and Development. It is one of the core departments of CLRI. It takes
care of the entire academic program of CLRI. It also supervises the Research and
Development activities going on in the CLRI campus. The aim of our project that
we do in CLRI is to create a website. The task of the website is to co-ordinate the
activities of the Implementing agencies. How it can coordinate and whom it will
coordinate will be explained very clearly in the subsequent parts of the report.
The tools that we are using to create this application are:
1. ASP.NET 3.5
2. MICROSOFT VISUAL STUDIO 2008
3. MICROSOFT VISUAL C# (pronounced as C sharp)
4. Microsoft SQL Server 2008
INTRODUCTION
1. IMPLEMENTING AGENCY
2. EXPERT
3. ADMINISTRATOR
So this explains the task of our website as well as the job of ours.
So far the work and the job of the website have been mentioned and from now
on the technical aspects of the website will be coming into the picture.
TECHNICAL ASPECTS
As we have mentioned earlier the website will be created using the languages
ASP.NET and C#. Since the website contains the dynamic part like storing the
details of the trainees and storing the feedback of experts it cannot be simply done
by HYPER TEXT MARK UP LANGUAGE. So we have to choose some other
resources for the job to be done. It could be done by PHP and some other
languages but the internet server of the government do not support all those
languages so we have to choose ASP.NET as our background. ASP.NET alone
can’t do the job it must be tied up with other language like C# and C++. We have
chosen C# because it is recommended by the MICROSOFT group. Before going
into the details of ASP.NET we have to know something regarding that and its
background. Microsoft .NET is Microsoft's new Internet strategy.
MICROSOFT.NET was originally called NGWS. It stands for Next Generation
Windows Services. Before the official announcement of .NET, the term NGWS
was used for Microsoft's plans for producing an "Internet-based platform of Next
Generation Windows Services". Steve Ballmer quote January 2000:
STEVE BALLMER is the current CEO of MICROSOFT and at the time he has
given this statement he is the 2nd position following BILL GATES the chairman of
MICROSOFT. So the statement shows the importance of .NET and its applications
to MICROSOFT one of the industry giants in software fields.
The Microsoft .NET strategy was presented by Microsoft officials to the rest of the
world in June 2000:
.NET Framework
The .NET Framework is the infrastructure for the new Microsoft .NET Platform.
The .NET Framework contains common class libraries - like ADO.NET, ASP.NET
and Windows Forms - to provide advanced standard services that can be integrated
into a variety of computer systems.
The .NET Framework is language neutral. Currently it supports C++, C#, Visual
Basic, Java Script (The Microsoft version of JavaScript) and COBOL. Third-party
languages - like Eiffel, Perl, Python, Smalltalk, and others - will also be available
for building future .NET Framework applications.
Before going into the details of ASP.NET we have to know what is ASP.
What is ASP?
ASP Compatibility
When a browser requests an HTML file, the server returns the file
When a browser requests an ASP file, IIS passes the request to the ASP
engine. The ASP engine reads the ASP file, line by line, and executes the
scripts in the file. Finally, the ASP file is returned to the browser as plain
HTML
But ASP.NET is not the same as ASP. It is neither the upgraded version of
ASP. It is completely a new technology and it is built from basic. In order to
differentiate between ASP and ASP.NET ASP is now a days called as
CLASSIC ASP.
ASP.NET is the next generation ASP, but it's not an upgraded version of ASP.
You can read more about the differences between ASP and ASP.NET in the next
chapter of this tutorial.
What is ASP.NET?
"
When a browser requests an HTML file, the server returns the file
When a browser requests an ASP.NET file, IIS passes the request to the
ASP.NET engine on the server
The ASP.NET engine reads the file, line by line, and executes the scripts in
the file
Finally, the ASP.NET file is returned to the browser as plain HTML
What is ASP+?
ASP+ is just an early name used by Microsoft when they developed ASP.NET.
ASP.NET 2.0
ASP.NET 2.0 improves upon ASP.NET by adding support for several new
features.
You can read more about the differences between ASP.NET 2.0 and ASP.NET in
the next chapter of this tutorial.
ASP.NET 3.0
ASP.NET 3.0 is not a new version of ASP.NET. It's just the name for a new
ASP.NET 2.0 framework library with support for Windows Presentation
Foundation, Windows Communication Foundation, Windows Workflow
Foundation; and Windows Card Space.
What ASP.NET 3.5 offers is a way to store, retrieve, and process the information.
Other than storing cookies on the Visitor’s computer, you can’t do too much with
HTML when it comes to controlling the state of your data.
Your browser’s main job is requesting pages from the server and displaying what
the server has processed. Using HTTP as a transfer protocol, your browser parses
(interprets) the HTML code it gets from the server, but otherwise does little
processing. Because your HTTP client (browser) leaves most of the processing
work to the server, it is considered a thin client. There’s nothing wrong with a thin
client, and it can process JavaScript. With plug-ins, which virtually all browsers
have built in, a thin client can also process certain kinds of files such as SWF
(compiled Adobe Flash files), Java Applets, ActiveX Controls, as well as other
files requiring that the browser have compatible plug-ins. For the most part,
though, the thin client model is one where the server does the processing, and your
Browser’s job is to display the contents it gets from the server.
In addition to being a thin client, your HTTP client browser is stateless. As soon as
a web page reaches your computer, the connection between your browser and the
server is broken. The browser does not remember the last page—it does not hold
state. As soon as the next page arrives, it does not remember the last page. You
may be thinking that your cache holds lots of previous pages and that your
browser’s history feature remembers previous pages. That’s not what retaining
state means. You cannot use the data and information in your cache or the
browser’s history as states to use with the current page in memory. What is in
active memory is the web page that the server has sent; the state of the previous
page is not there. As soon as you load a page, the previous page is kicked out, and
the new page is placed there. Just as the information you place in a text input box
is sent to silicon oblivion when you click the Submit button, knowledge of the
previous page (its state) is gone when the new page arrives. A well-organized web
site may appear to maintain state as the links on pages
Connect to a set of related pages, but that is an illusion that the web designer has
crafted by good planning.
All these dynamic parts and jobs can’t be simply done by HTML.
As far as our progress in this project is concerned we have completed first few
pages of the website such as registration and login things.
Now we are working on connecting the database to the site.
Talking about the tools that we use in these projects MICROSOFT VISUAL
STUDIO is of at most importance. It is a building environment in which the code
is automatically generated upon the drag and drop. A part of the demo has been
shown to the Instructor and the students.
CONCLUSION:
By using all the tools and languages we have succeeded to some extent and we
hope that in the near future we will be completing the project.