0% found this document useful (0 votes)
19 views6 pages

Understanding Classic ASP Basics

Classic ASP refers to Microsoft's previous server-side scripting technology known as Active Server Pages. ASP.NET is not an upgraded version of ASP but rather an entirely new technology that is not backward compatible with classic ASP. ASP.NET is a server-side scripting technology that enables scripts embedded in web pages to be executed by an internet server. It provides better language support, controls, and other features compared to classic ASP.

Uploaded by

sivajothimadurai
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
19 views6 pages

Understanding Classic ASP Basics

Classic ASP refers to Microsoft's previous server-side scripting technology known as Active Server Pages. ASP.NET is not an upgraded version of ASP but rather an entirely new technology that is not backward compatible with classic ASP. ASP.NET is a server-side scripting technology that enables scripts embedded in web pages to be executed by an internet server. It provides better language support, controls, and other features compared to classic ASP.

Uploaded by

sivajothimadurai
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd

What is Classic ASP?

Microsoft's previous server side scripting technology ASP (Active Server Pages) is now often
called classic ASP.

ASP 3.0 was the last version of classic ASP.

To learn more about classic ASP, you can study our ASP tutorial.

[Link] is NOT ASP


[Link] is the next generation ASP, but it's not an upgraded version of ASP.

[Link] is an entirely new technology for server-side scripting. It was written from the ground
up and is not backward compatible with classic ASP.

You can read more about the differences between ASP and [Link] in the next chapter of this
tutorial.

[Link] is the major part of the Microsoft's .NET Framework.

What is [Link]?
[Link] is a server side scripting technology that enables scripts (embedded in web pages) to
be executed by an Internet server.

 [Link] is a Microsoft Technology


 ASP stands for Active Server Pages
 [Link] is a program that runs inside IIS
 IIS (Internet Information Services) is Microsoft's Internet server
 IIS comes as a free component with Windows servers
 IIS is also a part of Windows 2000 and XP Professional

What is an [Link] File?


 An [Link] file is just the same as an HTML file
 An [Link] file can contain HTML, XML, and scripts
 Scripts in an [Link] file are executed on the server
 An [Link] file has the file extension ".aspx"
How Does [Link] Work?
 When a browser requests an HTML file, the server returns the file
 When a browser requests an [Link] file, IIS passes the request to the [Link] engine
on the server
 The [Link] engine reads the file, line by line, and executes the scripts in the file
 Finally, the [Link] file is returned to the browser as plain HTML

What is ASP+?
ASP+ is the same as [Link].

ASP+ is just an early name used by Microsoft when they developed [Link].

The Microsoft .NET Framework


The .NET Framework is the infrastructure for the Microsoft .NET platform. 

The .NET Framework is an environment for building, deploying, and running Web applications
and Web Services.

Microsoft's first server technology ASP (Active Server Pages), was a powerful and flexible
"programming language". But it was too code oriented. It was not an application framework and
not an enterprise development tool.

The Microsoft .NET Framework was developed to solve this problem.

.NET Frameworks keywords:

 Easier and quicker programming


 Reduced amount of code
 Declarative programming model
 Richer server control hierarchy with events
 Larger class library
 Better support for development tools

The .NET Framework consists of 3 main parts:

Programming languages:
 C# (Pronounced C sharp)
 Visual Basic (VB .NET)
 J# (Pronounced J sharp)

Server technologies and client technologies:

 ASP .NET (Active Server Pages)


 Windows Forms (Windows desktop solutions)
 Compact Framework (PDA / Mobile solutions)

Development environments:

 Visual Studio .NET (VS .NET)


 Visual Web Developer

This tutorial is about [Link].

[Link] 2.0
[Link] 2.0 improves upon [Link] by adding support for several new features.

You can read more about the differences between [Link] 2.0 and [Link] in the next
chapter of this tutorial.

[Link] 3.0
[Link] 3.0 is not a new version of [Link]. It's just the name for a new [Link] 2.0
framework library with support for Windows Presentation Foundation, Windows
Communication Foundation, Windows Workflow Foundation; and Windows CardSpace.

[Link] 3.0 is not covered in this tutorial.

[Link] has better language support, a large set of new controls, XML-based components, and
better user authentication.

[Link] provides increased performance by running compiled code.


[Link] code is not fully backward compatible with ASP.

New in [Link]
 Better language support
 Programmable controls
 Event-driven programming
 XML-based components
 User authentication, with accounts and roles
 Higher scalability
 Increased performance - Compiled code
 Easier configuration and deployment
 Not fully ASP compatible

Language Support
[Link] uses [Link].

[Link] supports full Visual Basic, not VBScript.

[Link] supports C# (C sharp) and C++.

[Link] supports JScript.

[Link] Controls
[Link] contains a large set of HTML controls. Almost all HTML elements on a page can be
defined as [Link] control objects that can be controlled by scripts.

[Link] also contains a new set of object-oriented input controls, like programmable list-boxes
and validation controls.

A new data grid control supports sorting, data paging, and everything you can expect from a
dataset control.

Event Aware Controls


All [Link] objects on a Web page can expose events that can be processed by [Link]
code.

Load, Click and Change events handled by code makes coding much simpler and much better
organized.

[Link] Components
[Link] components are heavily based on XML. Like the new AD Rotator, that uses XML to
store advertisement information and configuration.

User Authentication
[Link] supports form-based user authentication, cookie management, and automatic
redirecting of unauthorized logins.

User Accounts and Roles


[Link] allows user accounts and roles, to give each user (with a given role) access to different
server code and executables.

High Scalability
Much has been done with [Link] to provide greater scalability.

Server-to-server communication has been greatly enhanced, making it possible to scale an


application over several servers. One example of this is the ability to run XML parsers, XSL
transformations and even resource hungry session objects on other servers.

Compiled Code
The first request for an [Link] page on the server will compile the [Link] code and keep a
cached copy in memory. The result of this is greatly increased performance.
Easy Configuration
Configuration of [Link] is done with plain text files.

Configuration files can be uploaded or changed while the application is running. No need to
restart the server. No more metabase or registry puzzle.

Easy Deployment
No more server-restart to deploy or replace compiled code. [Link] simply redirects all new
requests to the new code.

Compatibility
[Link] is not fully compatible with earlier versions of ASP, so most of the old ASP code will
need some changes to run under [Link].

To overcome this problem, [Link] uses a new file extension ".aspx". This will make
[Link] applications able to run side by side with standard ASP applications on the same
server.

« Previous Next Chapter »

Common questions

Powered by AI

In Classic ASP, when a browser requests a file, the server processes the ASP file line by line, executing the script and returning HTML to the browser. On the other hand, ASP.NET handles files differently. When a browser requests an ASP.NET file, the Internet Information Services (IIS) passes the request to the ASP.NET engine, which reads the file, executes the scripts, and returns plain HTML to the browser. ASP.NET improves performance through compiled code, meaning the code is compiled once and cached for faster subsequent access .

Migrating from Classic ASP to ASP.NET poses several challenges due to the lack of full backward compatibility, requiring changes in code to make older ASP applications work under ASP.NET. Developers need to convert VBScript to supported languages such as C# or Visual Basic and adapt to the new architecture and compiled code model. To mitigate these challenges, developers can take a phased approach, utilizing tools for code conversion and training to familiarize themselves with ASP.NET's framework and architecture, reducing downtime and transition issues .

Event-driven programming in ASP.NET offers several key benefits, enhancing the way developers interact with web page elements. It allows all objects on a web page to expose events (like Load, Click, and Change) that can be handled in the code, making the coding process more straightforward and organized. This approach improves responsiveness and interactivity, as events are processed dynamically, leading to faster execution and response times. It also aids in separating the business logic from the user interface, simplifying maintenance and scalability .

ASP.NET significantly improves application deployment over Classic ASP by eliminating the need to restart servers when publishing or replacing compiled code. ASP.NET can redirect new requests to updated code without interruption, facilitating smoother and quicker deployment processes. This ability to handle configuration changes through simple uploads of text configuration files, without requiring server restarts, also contributes to easier and more efficient deployments compared to Classic ASP .

ASP.NET achieves higher scalability through several key improvements over Classic ASP. For example, ASP.NET supports better server-to-server communication, which allows applications to scale over multiple servers. This is accomplished by running XML parsers, XSL transformations, and resource-intensive session objects on different servers. Furthermore, ASP.NET's compiled code model improves performance and reduces the computational load during subsequent requests, enhancing scalability. These architectural changes enable ASP.NET applications to handle larger loads efficiently compared to Classic ASP .

XML plays a crucial role in both the functionality and configuration of ASP.NET applications. Functionally, ASP.NET components are heavily based on XML, such as the AD Rotator, which uses XML to store advertisement information and configurations. For configuration, ASP.NET employs plain text configuration files written in XML. These files can be modified and uploaded without the need for server restarts. This flexibility simplifies the management of application settings and enhances the deployment process .

ASP.NET features significant improvements in language support and control elements compared to Classic ASP. ASP.NET supports full Visual Basic, C#, and C++, allowing for robust programming compared to Classic ASP, which primarily supports VBScript. ASP.NET defines almost all HTML elements on a page as control objects, enabling them to be manipulated more dynamically with scripts. Furthermore, ASP.NET introduces object-oriented input controls, such as programmable list-boxes and validation controls, and includes a new data grid control that supports sorting and paging. These enhancements result in more sophisticated and manageable web applications .

ASP.NET enhances application security through its form-based user authentication system, which allows the management of user credentials and roles. It supports cookie management and automatic redirection of unauthorized users if they attempt access. This ensures that only authenticated users with specific roles can access certain areas of the application. In contrast, Classic ASP lacks such built-in mechanisms, often requiring developers to manually implement these security features in their code, making ASP.NET a more secure and easier option for managing user access control .

ASP.NET supports form-based user authentication by allowing developers to define forms for user login and manage user credentials securely. It manages user roles by enabling role-based access control, whereby each user is assigned a role, granting specific permissions to access server resources and execute code. These built-in features simplify managing user access rights and enhance application security, contrasting with Classic ASP where such functionalities require manual and less secure implementations .

The .NET Framework comprises three main components: programming languages (C#, Visual Basic, J#), server and client technologies (ASP.NET, Windows Forms, Compact Framework), and development environments (Visual Studio .NET, Visual Web Developer). These components collectively enhance ASP.NET's functionality by providing a robust infrastructure for building, deploying, and running web applications. Programming languages allow for versatile coding, server technologies provide efficient backend processing, and development environments offer user-friendly tools for building and managing ASP.NET applications .

You might also like