icelava
22-11-2003, 14:35
Originally posted by Hostings
But anyone here mind differentiating the difference between ASP and ASP.NET?
If you are unfamiliar with .NET Framework, and .NET in general, it's gonna take awhile for you to sink the idea and concept in. I know it did for me the first time I printed > 200 pages of .NET Framework whitepaper and related documents. In fact, one of the major failings of Microsoft was its exceedingly obscure marketing and definition of .NET.
I am one who hates to duplicate materials already prepared by others (and in some effect stealing their credit). I will attempt to provide a concise summary while linking you to the _heavy_ stuff for your own consumption.
The ASP.NET Page framework serves to make the web page interface behave as though it was a normal Windows GUI app. If you have programmed Windows apps before, then you will know the event-driven model that lets you place hooks into events that occur from user's input to the interface controls. (eg. Click on button "Save"). These hooks are event handlers, which you write code to define what happens after an event is raised.
In essence, the HTML page is abstracted away from your interface logic. This is done by means of Web Controls, meaning you place tags like <asp:Button id="SaveButton" runat="Server"/> or <asp:TextBox id="EmailTextBox" runat="Server"/> and your code references them as Button or TextBox controls NOT the raw <input> tag that you would in classic ASP.
It also introduces the concept of Code-behind, whereby your code is living in another file away from the HTML-layout .aspx page. No more fragile "spaghetti code" littered all over your page, your designer and programmer don't have to argue anymore.
And because ASP.NET is simply a subset of the .NET Framework, which is entirely object-oriented, developing n-layered architectures of components across a uniform programming environment makes it so much easier than using traditional COM/+ components.
Given this abstraction from HTML, you can written interface controller logic that works for both ASP.NET Web Forms and Windows Forms (the traditional GUI apps), promoting alot of code re-use.
The propaganda site (http://www.microsoft.com/net/)
What is .NET? (http://www.microsoft.com/net/basics/)
Why ASP.NET? (http://asp.net/whitepaper/whyaspnet.aspx?tabindex=0&tabid=1)
What Is the Microsoft .NET Framework? (http://www.microsoft.com/net/basics/framework.asp)
What .NET Means for IT Professionals (http://www.microsoft.com/net/business/it_pros.asp)
Microsoft .NET for IT Professionals (http://www.microsoft.com/technet/treeview/default.asp?url=/technet/itsolutions/net/evaluate/itpronet.asp?frame=true)
But anyone here mind differentiating the difference between ASP and ASP.NET?
If you are unfamiliar with .NET Framework, and .NET in general, it's gonna take awhile for you to sink the idea and concept in. I know it did for me the first time I printed > 200 pages of .NET Framework whitepaper and related documents. In fact, one of the major failings of Microsoft was its exceedingly obscure marketing and definition of .NET.
I am one who hates to duplicate materials already prepared by others (and in some effect stealing their credit). I will attempt to provide a concise summary while linking you to the _heavy_ stuff for your own consumption.
The ASP.NET Page framework serves to make the web page interface behave as though it was a normal Windows GUI app. If you have programmed Windows apps before, then you will know the event-driven model that lets you place hooks into events that occur from user's input to the interface controls. (eg. Click on button "Save"). These hooks are event handlers, which you write code to define what happens after an event is raised.
In essence, the HTML page is abstracted away from your interface logic. This is done by means of Web Controls, meaning you place tags like <asp:Button id="SaveButton" runat="Server"/> or <asp:TextBox id="EmailTextBox" runat="Server"/> and your code references them as Button or TextBox controls NOT the raw <input> tag that you would in classic ASP.
It also introduces the concept of Code-behind, whereby your code is living in another file away from the HTML-layout .aspx page. No more fragile "spaghetti code" littered all over your page, your designer and programmer don't have to argue anymore.
And because ASP.NET is simply a subset of the .NET Framework, which is entirely object-oriented, developing n-layered architectures of components across a uniform programming environment makes it so much easier than using traditional COM/+ components.
Given this abstraction from HTML, you can written interface controller logic that works for both ASP.NET Web Forms and Windows Forms (the traditional GUI apps), promoting alot of code re-use.
The propaganda site (http://www.microsoft.com/net/)
What is .NET? (http://www.microsoft.com/net/basics/)
Why ASP.NET? (http://asp.net/whitepaper/whyaspnet.aspx?tabindex=0&tabid=1)
What Is the Microsoft .NET Framework? (http://www.microsoft.com/net/basics/framework.asp)
What .NET Means for IT Professionals (http://www.microsoft.com/net/business/it_pros.asp)
Microsoft .NET for IT Professionals (http://www.microsoft.com/technet/treeview/default.asp?url=/technet/itsolutions/net/evaluate/itpronet.asp?frame=true)