What is difference between ASP and ASP.NET ?

ASP.NET:

(a) ASP.Net web forms have a code behind file which contains all event handling code.

(b) ASP.Net web forms inherit the class written in code behind.

(c) ASP.Net web forms use full fledged programming language

(d) ASP.Net web applications are configurable (web.config)

(e) ASP.Net webforms can use custom controls through the @ register directive

(f) ASP.Net web forms have ADO.Net which supports XML integration and integration of data from two or more data sources

(g) ASP.NET can run on non-Microsoft Platforms. Cassini is a sample Web server produced by Microsoft which, among other projects, has been used to host ASP.NET with Apache. 

(h) We can use any fully compliant .NET language with ASP.NET, including C# and VB.NET.

(i) ASP.NET pages are always compiled into .NET classes housed within assemblies. This class includes all of the server-side code and the static HTML, so once a page is accessed for the first time (or any page within a particular directory is accessed), subsequent rendering of that page is serviced by executing compiled code. The .aspx file is parsed into a single code file and compiled, it is not possible to use multiple server-side languages within a single .aspx file.

ASP:

(a) ASP does not have such facility to separate programming logic from design.

(b) ASP does not have the concept of inheritance.

(c) ASP pages use scripting language.

(d) ASP applications are not.

(e) It is not available with ASP.

(f) while ASP has ADO which is a simple COM object with limited facilities.

(g) Classical ASP had no mechanism of running itself on non- Microsoft technology platforms like the 'The Apache Web Server'.

(h) In ASP only two languages were available for scripting VBScript and Jscript/Javascript. 

(i) In ASP, ASP engine executes server-side code, which is always through an interpreter (JScript or VBScript). When a traditional ASP page is requested, the text of that page is parsed linearly. All content that is not server-side script is rendered as is back to the response. All server-side script in the page is first run through the appropriate interpreter (JScript or VBScript), the output of which is then rendered back to the response. This architecture affects the efficiency of page rendering in several ways. First, interpreting the server-side script on the fly.Response time is increased, intermingling server-side evaluation blocks with static HTML is less efficient than evaluating a single server-side script block many ASP developers resort to large blocks of server-side script, replacing static HTML elements with Response.Write() invocations instead.