ASP.NET is comprised of two major areas: ASP.NET
Web pages and ASP.NET Web services.
ASP.NET Web pages are akin to classic ASP pages
– Web surfers visit them through a browser and are returned valid HTML.
ASP.NET Web services provide for inter-Web
server communications.This allows
an ASP.NET Web page (or a stand-alone application) to access a remote
program to obtain information.(More
on this topic in tomorrow’s talk on Web services.)
ASP.NET Web pages and Web services are compiled
programs.So when a user visits one
of your ASP.NET Web pages, an actual “program” is being executed – the
ASP.NET Web page.
These Web pages and Web services are compiled
on-demand, meaning that when a Web page or Web service is first visited, it
is compiled.From then on, a cached
version (using disk-based caching) of the intermediate code is referenced.
Only runs on Windows 2000 and Windows XP Pro
(requires that IIS 5.0+ be installed).
The .NET Framework is freely available to
download from http://www.asp.net/
Once the .NET Framework has been installed you
can create ASP.NET pages simply by creating a file (using your favorite
editor (Notepad / Visual Studio, etc.) with a .aspx extension in a Web
directory (I.e., C:\InetPub\wwwroot\).
ASP.NET and Classic ASP can run side-by-side on
a Web server.That is, you can have
ASP.NET Web pages and classic ASP pages running on your Web site.
One of .NET’s goals is to provide side-by-side
functionality, meaning you should be able to run ASP.NET v2.0 and v1.0 on
the same Web server at the same time (whenever ASP.NET v2.0 comes out, that
ASP.NET Web Pages can be created to look just
like classic ASP pages.Show SimpleASP.NET.demo.aspx.
Note that when we run this demo, there is a
slight delay.The .NET Framework is
actually running an instance of the VB.NET compiler!This delay only occurs when the page is
loaded for the first time after it is created or a change to the source
code has occurred.
Also note that ASP.NET Web pages output regular
HTML, just like classic ASP pages.