Geek Answers Handbook

How ASP.Net MVC differs from classic ASP (and not ASP.Net - the original ASP)

I am trying to get a high-level understanding of ASP.Net MVC, and I learned that it is very similar to the original ASP script. On the same day, we organized our model / business logic code into VBScript classes or into VB COM components.

Of course, now we have the extra power of the C # and .net classes. Besides the high-level oo and other features in C # and .Net, what are the other significant differences between the original ASP and ASP.Net MVC?

+5
source share
4 answers

There are three main differences: URL mapping, separation of logic from presentation, and strong typing.

URL mapping

ASP HTML- HTML- . HTML , URL- . ASP.NET, .

ASP.NET MVC "" URL- Controller ( /Controllers ), . () , ( /Views ), ASP , ,

SEO- URL- .

ASP , HTML, , , html, ..

ASP.NET MVC - (, ) ( , LINQ-to-SQL LINQ-to-Entity-Framework), (, State/Province ), ( HTML, ), .

, , . , , , , , , , .

ASP.NET . . , . , , " " ( ). , , :

if (MyArray.Length > 0)


if (MyArray.Length)

, , , .

, - ASP. -, . - (, ) , .

+12

ASP.NET MVC : , , URL- ; . ( ViewData).

, MVC . HTML , , Web Forms, Spark, NHaml .., , (, Web Forms) .. ASP Classic .

+2

ASP VBScript, . - .

0

. . , , , , .

ASP Classic , asp net mvc.

# vb script, , , .

ASP, " asp mvc, , - .

.

Asp Net Mvc integrates seamlessly with technologies such as EntityFramework to allow further code splitting and organization.

0
source

More articles:


All Articles