Re: Difference between asp & asp.net
 

thank you for the link this info was very helpfull!!!

Re: Difference between asp & asp.net
 

I am a Class ASP coder myself, but am learning .NET. In my stand point, asp was easier to get simple tasks done, but the more complicated ones .NET does in a flash. Just like PHP, ASP Classic had to use loops through queries, use if statements, and then display the database information through many, MANY lines of code. I know for a simple three 2-3 column database view through ASP Classic, it would take about 60 lines of code to retreieve information, setup the loops and display the information. In .NET, you can do this in 20, if that. Just grab the info and throw it into a control, like gridview, datalist, etc. It automatically puts it out for you, then you can design it yourself. I am not a PHP programmer, but have developed a few sites with PHP. I must say, this language is easier to learn and easier to compile than PHP.

Anyway, the link will give you better information than I can, but as I am trying to convert over to ASP.NET (as my days of clients requesting ASP sites have just about COMPLETELY ended..) the two languages are almost nothing alike. The only comparable attributes of these languages, are the sub languages that you learn, VBScript and VB.NET. ASPClassic does not require you to know VBScript to get the job done, at all. But ASP.NET requires you to know one of four languages listed earlier (C+, VB or VB.NET, C#, or J#). VB.NET was easier for me to understand as it follows the same rules (mostly) as ASP does.

Comparing the Languages:
PHP follows some basic rules as ASP
ASP.NET follows its own rules
Sub languages are the keys to ASP.NET, without them, you cannot compile a simple page with controls.
ASP.NET is run on the server, not on the clients machine.
ASP.NET uses include files (like .ascx) that doesn't even let a client machine view such a file, let alone trying to hack one.
ASP.NET reforms some html coding, like TextBox, Links, Form Components, etc. They aren't required, but absolutely recommended as they can be compiled onto the server.
ASP.NET lets you keep viewstates without having to write code. It also runs on the server so you can do samepage validation easily.
ASP.NET also has validation controls that can compare ranges, values, etc.

Hopefully I helped a bit... :)